We have a LAN consisting of a Windows 2003 Server and 6 Windows XP Pro Tower PC's. A Netgear ProSafe FVX336G router handles local traffic as well as incoming connections from end users who wish to connect to our network via Remote Desktop Connection. This router sits "behind" our ISP's device. Our ISP has given us a Static IP address which is used by our "outside" employees to gain access.
I have no problem gaining access to our server with this Static IP. Once in the server I can gain access to individual computers on our LAN by using Remote Desktop Connection on the server. Each individual PC has been given it's own listening port and port forwarding has been setup and configured in the Netgear Router.
From the outside world, our Server is reached by RDC as follows:
ISP's Static IP Address: xxx.xxx.xxx.xxx:3389 (reaches Server Desktop)
From the outside world, the 1st PC on the LAN should be reached by RDC as follows:
ISP's Static IP Address: xxx.xxx.xxx.xxx:3390 (does not work)
This would indicate to me that I have a problem with port forwarding in the Netgear. However, whenever I reach the Server's desktop successfully, I am able to use RDC on the Server and reach the PC's on the LAN by keying in our LAN's addressing scheme with the listening port of the PC as in: 192.168.5.101:3390
What makes this all the more confusing is that from the Server I can reach all PC's on the LAN as described in the above paragraph with the exception of one PC. . . and that PC is configured exactly as all other PC's on the LAN.
I'm offering tech support to this small company and am following someone else's setup of this LAN and router. This type of setup is not new to me but these problems are confusing me to no end.