Forum Replies Created
-
Posts
-
Thank you for your response. I’ve been using Teamviewer to work remotely with a friend that has an ActionTec router. I assigned him a “static” IP address using DHCP reservation. Does not that accomplish the same purpose as setting up a static IP on the computer itself? This particular router was assigned to him by is ISP. The router he had before worked flawlessly with NoMachine, requiring no special efforts. If the ActionTec does require the setting of a static IP on the computer itself in order to work with port forwarding regardless of DHCP reservation, please let me know. NoMachine has automatically set up everything else it needs with regards to port forwarding.
In the firewall setting of this particular ActionTec modem/router, there is a long list of ports defined as open to traffic out. The ones dealing with web service are also checked to allow traffic in. The list includes the usual default settings for things such as FTP, SSH, etc. If I wished to open FTP access to the system, I would check the box to allow traffic in. At the bottom of the defined ports is a setting to allow in and out traffic to all other ports which should include 4000. I’ve even temporarily checked the boxes there just to check things out. All that aside, in the port forwarding section the particular needs of NoMachine are defined. The NoMachine software actually sets this automatically when the server is started, but I’ve also set things up there manually. And, yes, the server.cfg file has EnableUPnP set properly, and UPnP is enabled in the router. But, there has to be something in the router that is causing the problem. I just cannot at this point figure out what it is.
Thank you for all your suggestions which should have worked. Normally, NoMachine configures all these things automatically provided UPnP is enabled in the router. NoMachine automatically creates the port forwarding information, but I’ve also manually entered the information as well. I’ve also set things in the server.cfg file, restarted the server and ran the nxserver –upnpmap command. There’s still a mapping problem. I think the person I’m trying to help needs to contact his service provider concerning his problem.
Thank you for your response. It did provide some hope; however, I have tried several times to manually set up port forwarding. And, of course, NoMachine does this automatically upon startup. I’m wondering if I should manually set up both TCP and UDP. I’ve continually gotten the error message about not being able to map the port. In addition, I’ve also edited the NoMachine server.cfg file to make sure certain things are turned on and have found the settings as they should be. This modem/router is provided by an IP service. Could it be that the service has configured the device to make it totally incompatible with running a NoMachine server?
@barnoux: I only have the 64-bit version of 4.0.346_1 DEB file. I am connecting from one Ubuntu installation to another. Your experience using Windows 7 as client might be quite different from my experience. I think, however, NoMachine should maintain some archive copies of previous iterations of its software. I just do not know where they are maintained or if the company would make them available upon request.
I have the same problem when using the latest versions of NoMachine. However, when using the client of NoMachine 4.0.346_1, the resolution of the host is maintained by using “keep original aspect” in the settings on the client side. I tried all types of setting combinations in the client of the two latest versions, but could never get it to perform as well as the version I’ve named here. My host does have the latest version of the software. It’s only the client that needs to use the earlier one.