Saving config files/Auto connect

Forum / NoMachine for Windows / Saving config files/Auto connect

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #55549
    SovereignGFC
    Participant

    What I have

    – NoMachine Windows connecting to NoMachine Mac successfully (used for years)

    When I open NM on Windows, I get:

    – Zero nxs files in Documents\NoMachine
    – No ability to save a configuration

    When I attempt to create a new file for the Mac it wants to go through the internet (why???)

    What I want:
    – Connect to the NM Mac client on Windows boot/desktop
    – Use LAN-only connectivityWhat am I missing?  The documentation I’ve read about “saving/using connections” assumes the existence of NXS files, which I’m not seeing and don’t know how to generate for this “located through local discovery service” version of a connection.

    #55560
    Britgirl
    Keymaster

    Hi,

    Local network connections don’t save a file in Documents\NoMachine, because of the ephemeral nature of automatic server discovery e.g., a machine might be temporarily unavailable or change its local address, and so on. Local server connections are stored in a temporary cache, where the cached connection files keep user preferences, but automatically update the server address and protocol information.

    You have two options:

    i) From the Windows player, create a new connection file manually and set the local LAN server’s IP in the Host field. The “Direct connection over the Internet” description that you see there might be misleading you. Creating a connection this way is not limited to WAN addresses only. Choosing this way to connect is useful only if the server IP doesn’t change.

    ii) From the Windows player, in the Machines panel, edit the connection you want to launch automatically (right click on the connection icon), select Info in the left menu, copy the UUID visible in the Software group on the right, and look for the cached NXS file: %USERPROFILE%\.nx\cache\.nxs. Note however that when the system starts, the client has not yet received the broadcasted server address, so the one stored in the cache could be old and the connection may fail. Consider giving the Mac server a static LAN IP (in such a case, solution 1 would be easier).

    #55561
    SovereignGFC
    Participant

    Thank you for the prompt response.

    The Mac already has a fixed IP address, so I’ve used option 1 and created a connection file.  I found its file in the expected location.

    I’ve copied that file into my Startup folder.

    You can mark this as solved.

     

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Please login .