Sign in with
Sign up | Sign in
Your question

Baffling network issue

Last response: in Networking
Share
October 15, 2008 2:30:17 PM

I manage a company's network. They have two locations connected by a VPN. They have 3 windows 2000 servers. Two are domain controllers and one is a terminal server. There is one domain controller at one location (192.168.1.2) and the other two on the other side (DC: 192.168.0.2, TS: 192.168.0.8).

Every once in a while, the terminal server will be inaccessible from the 192.168.1.2 side. I can ping the terminal server from that side but cannot browse its files nor can I connect to it with remote desktop.

We manage the network remotely using a system which employs VNC. When the terminal server is down for the .1.2 side of the network, it shows up as offline in our database. In order to reach it, I need to remote into 192.168.0.2 and then use remote desktop to connect to 192.168.0.8. When I'm in 192.168.0.8, I'm able to ping all points on the network (local, over the VPN and external like yahoo.com). I can't browse to any webpages. It always times out. I can browse files on local systems but nothing over the VPN. Nobody on the .1.2 network can use remote desktop to get to the terminal server. Everyone on the 0.1 side of the network can. Also, I can't access the router's (192.168.0.1) web administration yet I can ping it just fine.

192.168.0.2 and 192.168.0.8 are both plugged into a large switch (along with numerous other computers). We are moving the two servers directly to the router. Will this fix the problem? Or am I just grasping at straws?

More about : baffling network issue

October 16, 2008 1:06:05 PM

Anyone have an idea?
October 24, 2008 9:47:16 AM

Maybe ??

We had a similar issue with our main Terminal Server, two network cards one internal, one external. Every few days the TS would be inaccessable on the External address, Internal fine.
If we rebooted, the problem went a way for a while, also if we changed the external cards IP address for 2 minutes then changed back the problem again resolved itself for a while.

Looking into it, both network cards had default gateways. we did a route print when "all was well" and saw that the external DG was the default, then when the issue occured a route print showed that the DG had switched to the internal.

The solve was to remove the Internal Cards DG. then manually add the gateway (cmd prompt, and I guess for you something along the lines of "route add –p 192.168.0.0 mask 255.255.255.?192.168.0.8".)

Hope this helps.

!