asked on

Terminal Services Disconnecting - not able to reconnect unless you reboot the server

I need to run something by you. We have a couple of servers that are accessible through Terminal Services that we run a scheduling app on. From time to time the server is unavailable from the internet, by this I mean that if you are behind our firewalls you are able to still access the server via the same external IP address and the server answers but you cant get to it from the outside. In order to fix the problem we have to reboot the server and then the server is available from the outside again. When the server becomes unavailable there are no entries anywhere in the event viewer referring to any problems. I am convinced since I found out that you can open the TS session from behind our firewall that the problem is with the CISCO or the Time Warner Security services that we have. The other in house IT guy is sure the problem is with Windows. Any ideas?

Steve Knight

Sounds like a route problem. Can it PING anything on the internet then. Have you got a default gateway defined on both an internet facing and internal NIC perhaps? If so Windows does a feature called dead gateway detection which means it may shut down a default gateway and use an alternate one (and not switch back) if it drops a connection for some reason.

If it is in this situation it might just be a case of removing the default gateway from the internal NIC and configuring some static routes to any other internal subnets if needed.

Off very shortly now but will look back tomorrow if you can throw any more details in here.

Steve

bbmorey

ASKER

Yes our systems do have 2 gateways but according to the registry key DeadGWDetectDefault it is set to 0 which I believe means that it is disabled. One thing to remember that the system is still accessible from our WAN when the system is not available from outside the WAN. Thank you for your input!

bbmorey

ASKER

i removed the gateway from the internal lan.

Steve Knight

accessible from our WAN when the system is not available from outside the WAN.

Sorry I must have misread the other way around... was overnight here before (on GMT). Post here when you are back and we can see if there any other issues with it .

bbmorey

ASKER

Any more thoughts? I am still looking for something concrete.

Steve Knight

Can we look at the current situation again then, it is dropping off the LAN side but WAN continues working, bit confused there sorry. Have you looked at the routing table from the server when this is happening

route print

and also do a tracert to whatever IP you can't get to to check the route it is taking.

bbmorey

ASKER

sure we can. Our outside clients from a remote IP lose connectivity to the server. At the time when they lose connectivity we are still able to access the server from the WAN or LAN ip address from inside of our organization(behind the firewall).

I will get the client to do the tracert and see what happens next time, good idea.

ASKER CERTIFIED SOLUTION

Steve Knight

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial