Forum Replies Created
-
Posts
-
We strongly recommend to upgrade NoMachine to the newest version.
For the router configuration. In “Enter IP Address” section write yours machine local IP. In “Starting/Ending Port” enter 4000. In “Protocol” choose TCP (or “ALL” if there is such possibility) and confirm changes (probably you need to restart router after all). Now you should be able to connect from external network. In NoMachine player enter Public IP (not local) and choose Port 4000 and Protocol NX.
If I try port forwarding do I need to edit the server.cfg file to allow the ports forwarded in the router to be detected by the server?
You don’t need to edit server.cfg. Configure your router to pass traffic to port 4000 (NX protocol). Instructions on how to connect to NoMachine when the server is behind a NAT router or a firewall you can find there: https://www.nomachine.com/AR11L00827. Read part “IMPORTANT”, there is instruction: “if the router doesn’t accept UPnP or NAT-PMP commands, it will be necessary to configure it manually through its administrative interface.”
Will that enable me to get my public ip address?
On NoMachine’s Welcome Screen page IP list? No – if you had disabled UPnP or your router doesn’t accept UPnP commands. In that case you can get your public IP address from whatismyip[dot]com, for example.
Users connected to the desktop can forward their own microphone to the session. By default microphone is always disabled. Users will have to activate it from the NoMachine menu panel inside the session. Click on the right upper corner of the session window or press Ctrl+Alt+0 to open the menu.Choose ‘Mic in’ icon button and click ‘Enable mic’. Sections 6.1 and 7 (Fig 18 and 19) in the following guide:
https://www.nomachine.com/DT07M00087
Now users are able to use default microphone from the client machine in the session. To swap input device just click on ‘Change settings’ and choose other device in the ‘Microphone input’ section.
To use input device from server machine in the session – users need only to play sound from microphone by using some application like system voice recorder.
Can you check solution from that post? https://www.nomachine.com/forums/topic/entering-login-keychain-password
We weren’t able to reproduce problem. Can you write here what is your graphic cards model and video drivers?
Seems like a firewall issue. Try disabling it temporarily to check. If it helps, enable firewall again and add the following exceptions – nxd, nxserver.bin, nxclient.app.
You can check if these services are with “Allowed” status in “System Preferences/Security & Privacy/Firewall/Firewall options”, if not – restart nxserver (in terminal use command
sudo /etc/NX/nxserver --restartand click “Allow” in pop-ups with mentioned services.sudo rm -rf /Applications/NX*.app
It’s not default NoMachine folder. It should be:
sudo rm -rf /Applications/NoMachine.app. Moving NoMachine folder to trash via GUI should be sufficient to remove NoMachine from system. But if you try to do it from terminal – shutdown nxserver first (sudo /etc/NX/nxserver --shutdown) and check it all nx processes are closed like you did it earlier. After that you can remove folder safety.Take a look at this topic: https://www.nomachine.com/forums/topic/error-138-cant-connect-to-office-computer-from-home
Can you verify whether you have this same problem?Thanks for the report. We were able to reproduce problem. Issue will be fixed as soon as possible. Please follow this trouble report: https://www.nomachine.com/TR05N06815 and use the notify me tool to know when a fix is available.
Please upgrade NoMachine on Mac to 5.1.24 and add extra options in the node configuration file (/Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg) to DisplayServerExtraOptions do not confuse with DisplayAgentExtraOptions).
Then uncomment DisplayServerExtraOptions key and change value to “-oldeventapi 0” or just add following line on the bottom node.cfg file.
DisplayServerExtraOptions “-oldeventapi 0”
Let us know if it helps.
Hi John.
Are you trying to connect via NX protocol? Which nxserver product do you have – is it free? Can you paste here what is in the nxerror.log (it’s in “/Library/Application Support/NoMachine/var/log/” directory)?
We couldn’t reproduce the problem on 5.0.47 server. Do you have any special symbols (non latin characters etc.) in username or password?
This also might be of help to you:
Setting up key-based authentication with NX protocol.
https://www.nomachine.com/AR02L00785(By the way, if possible you should update to the latest NoMachine version.)
Are you sure that you had changed server.cfg on your slackware machine? Which version slackware and which product of NoMachine you have? Is there anything written bellow spinning wheel?
Please upgrade your version to 5.1.24. We haven’t been able to reproduce it on the 5.1.22.
If problem still occurs please run debug (check article linked below), restart nxserver and try to reproduce the problem. If you were able to, please send top output (for example
top -1n -b > top_output.txt) and all logs from server side to forum[at]nomachine[dot]com or attach them here (size is restricted). Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT04M00076.Thanks for the post. We were able to reproduce problem. Issue was reported to developers and it will be fixed as soon as possible. As a workaround you can disable this key: PhysicalDesktopAuthorization in server.cfg.
Change: #PhysicalDesktopAuthorization 1 to PhysicalDesktopAuthorization 0
It’s a known issue – TR12M06315 (Cannot start nxnode on windows if hostname or username contains non-Latin symbols). Please follow this trouble report: https://www.nomachine.com/TR12M06315 and use the notify me tool to know when a fix is available.
We strongly recommend you update to 5.1.24 and check whether the problem disappears. If that didn’t help read suggestion from post, because issue looks similar: https://www.nomachine.com/forums/topic/no-available-sessions-4#post-11045