Question Locked

New terminal server to WAN/LAN network not accessible.

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
The new server is running Server 2003 Standard and is set up as a terminal server only. There is a working terminal server in the network running Server 2000 that is accessible from our remote locations using Remote Desktop however the Server 2003 cannot be accessed. When trying to log in to the 2003 Server through RD the user gets the generic "Remote Desktop disconnected. This computer can't connect to the remote computer." message. The firewall on the 2003 server is turned off. A Remote Desktop connection to the 2003 server can be made on any computer in the LAN but not the WAN. Also cannot ping any computers on the WAN from the Server 2003 machine. Remote users have been added to the Remote Desktop Users group on the 2003 server and Remote Desktop has been enabled. I am new to Server 2003 so there may security settings I have missed that are not available or have defaults in Server 2000 allowing the access to the 2000 server.

8 replies

by robo_dev

is there a router or firewall between your LAN and WAN?

Run run tracert on the Windows 2000 box to a host on the WAN and then run it on the 2003 box the same way.

I would bet there is a network hop that is being blocked by a router/firewall rule or VLAN configuration....or perhaps a static route is needed in the server.

by jlaughlin

The topology consist of a Comcast Business Gateway router at our home and remote location and a lynksys router between each Comcast router and the LAN for that location. The way I understood the Comcast setup when it was done a while back is that the Comcast router is a passthrough and the linksys handles DHCP, etc...

I ran the tracert on the 2000 server and it hits the local Comcast router, then the remote linksys router, then the remote host. When tracert is run on the 2003 server it hits nothing and times out.

by robo_dev

or there are 'NAT rules' setup in each site router to allow the Windows 2000 server Remote Desktop traffic to go over the internet.

whether it's a site-to-site VPN, or the connection is just performed by firewall rules, there needs to be some router reconfiguration to allow the traffic to reach the new server.

Not the right solution, but if you took the windows 2000 server off-line and gave the Windows 2003 server the same WAN IP address as the old server, it would most likely work.

by jlaughlin

Changing the 2003 IP to the 2000 IP was the first thing I tried and it was unsuccessful. Since I don't have access to all the settings on the Comcast router I guess I'll talk to their support people (arghhhh). Thanks for pointing me in the right direction.

by cg it

Need some more clarification on your topology.

Have to know if the connection is a VPN site to site with endpoints at the routers [non comcast]. If so, does both routers provide relay agent services to provide LAN addresses to hosts accessing the tunnel? If only one side provides relay agent services, then only inbound requests on the side that provides it will be able to remote desktop in to a host on that network. Going the other way, hosts will be on a different subnet thus not able to access resources on that subnet.

If this is not site to site vpn, rather your forwarding RD requests to a specific host, then that's the problem. Forwarding limits to the specified host.

by jlaughlin

There is not a VPN tunnel set up between my routers (Linksys). The linksys routers handle the DHCP for their local networks but I do not know how the WAN is configured. Comcast set up their routers and I was not involved. I will have to get a tech from Comcast to either come out or explain to me the setup and any forwarding that is occurring.

by cg it

If you can remote desktop into one server, then chances are that RD connection is forwarded to the server. If you have another server on that same network, RD isn't going to work for it because RD is forwarded to a specific server/computer.

This discussion is closed to new replies.