Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote Desktop Setup

Status
Not open for further replies.
Jun 12, 2012
1
I have two servers (2003 and 2008) connected to a AD domain. The servers have fixed IP's within the local domain (192.168.0.xxx) and I have setup unique port numbers for each server to use Remote Desktop (3390 and 3391).

The Public IP is static and I want to be able to point Remote desktop at the public IP using the correct port number for each server.

NETGEAR ProSafe VPN Firewall FVS336G

I have a working setup with the 2003 server and have been connecting fine from any system. I setup a Inbound Firewall rule in the Netgear to redirect HTTP and PING to the 2003 IP. This seems to work.

The 2008 is the problem. I recreated the same rules for the 2008 based on the 2003 and get connection refused. I disabled the Windows Firewall and can remote into the box from within the domain.

173.xxx.xxx.xxx:3390 ---> 192.168.0.101:3390 2003 server OK

173.xxx.xxx.xxx:3391 ---> 192.168.0.100:3391 2008 server Connection Refused

I setup a service in the router for the specific port 3391 and forwarded all traffic directly to the server and still fails.

I need to get this to work ASAP as I am testing out a move from the 2003 server to 2008 and have to recreate the exact functionality before I get paid. The 2008 server is brand new and may not have everything configured correct yet. Any suggestions?

Jon B
 
Well you could change the port on the 2003 server to 3391 to quickly test the firewall rule.

Check to make sure the 2008R2 server can connection to the internet and that's it's DNS and gateway are correct.

Also make sure you are using the latest RDP client externally as remote desktop for your 2008 server may be configured to only allow access from the newer client.
 
just a question is there a good reason that you need the rdp port on 3391 instead of the default 3389?

Anyways have you tried d/l wireshark on your external client and the 2008 server and run a capture on both while trying to connect? This should show if your getting through the firewall or not.

We are also making some assumtions here that your 2008 and 2003 subnet and gateway are the same and that the gateway has a route out for 192.168.0.100 to your external client, like joepc stated about checking the internet connection.


Windows Haiku:

Serious error.
All shortcuts have disappeared.
Screen. Mind. Both are blank.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top