Forum Replies Created
Today I got the the session negotiation failed.
When I first installed it and it was working, I would right click on one PC and copy the file. Then I would go to the other PC and choose to paste the file and nothing happens. I could only use the File Transfer method to move a file from one PC to the other from the Desktop. The Computers are at different site locations. When I use RDP I normally use an external IP address like 206.xx.x.xxx:3391 and it connects to the remote PC and everything works. On the Cisco firewall at the remote location:
I set up and access rule that has its destination set as my actual local IP on the Remote PC 172.xx.xx.xxx. I name the Service TCP-3389 and save that access rule.
I then set up a Nat rule that again uses my actual local internal IP address 172.xx.xx.xxx from the site remote PC. I then set that up with an automatic Translation Rule that points to a translated IP address like 206.xx.x.xxx which is used above to connect to the remote PC with the include port number. Under Advanced setting here I set the Service Protocol to TCP to forward the real port 3389 to port 3391. This is called the source Inside and destination outside. The other part of that has the same info on the Object is called the Outside Source and Inside destination.
The last piece needed to get the RDP to work with the remote on site PC is the created Network Object/Groups.This has the same static local IP address as seen above172.16.44.105 which is the actual local IP address of that remote PC. It also has that same translated IP address as seen above 18.104.22.168. Under advanced in that location it has the inside source and outside destination with TCP real port 3389 to mapped port 3391. With that, the RDP works flawlessly.
When I try and use your software, I installed the software first on the remote off site PC. When I start the software up it only finds the following:NX://172.xx.xx.xxx and a ssh://172.xx.xx.xxx with no port info which is the actual local internal IP address of the Remote PC which again is at a different location then the PC I’m setting this up on trying to connect to it remotely.
I then installed your software on my local workstation and it finds the following: NX://192.168.x.xx which is my actual local IP address. So I go through the settings with your software and it surprisingly connect to the remote off site PC using my local IP 192.168.1.xx using the given 4000 port. This worked until the next day and then I started getting the session negotiation failed today. When it was working yesterday it just couldn’t perform a simple copy from the Local Desktop to the Remote Desktop or vice versa.
Like I mentioned before, when I browse to C:\Users\Tom nx/config on either the local or remote PC I only saw a Player.cfg on both the local and remote PC, no server.cfg to look for clues on the copy and paste issue. This evening I just checked on my Local PC and found a server.cfg on it but I thought this was suppose to be the Player non Server PC. When I checked the remote PC at the other location, I still only found a Player.cfg but I thought that PC was suppose to be the server.
If I use Whats my IP on my local PC, I get an Public ID address like: 73.xxx.xx. xxx which is provided by my ISP Comcast.
On the remote PC I get using Whats my IP the Public address is like: 206.xx.x.xxx from that ISP
I’m not sure what to try next or just give up on using your software.