Server 2003

[mizzfit]

Hello Everybody,

Recently my DC will no longer ping the default gateway, or allow external remote connections. The tricky part here is that I don't remember causing this but yet it happened. Key notes to point out:

1. I can't ping the default gateway
2. I can't browse through IE or Firefox
3. I can ping any other host on the subnet
4. I can remote desktop from internal computers on the network
5. The setup is that it has a port forward to the default 3389 port from the router, but obviously since I can't ping the router the reqests are not getting through.

I think I have exceeded my Terminal Services license, would this cause the above problems? What is the difference betwen a terminal service Vs. a remote desktop connection? If this is the problem why can't I ping the router or browse the internet from locally on the host.

Please help!

Thanks in advance,
Ryan

[DragonNOA1]

If your Terminal Service grace period has expired or you are out of TS licenses, then clients that connect to your TS server will be denied access. Remote Desktop is the XP/Vista name for Terminal Services.

Do you have Terminal Services enabled on a DC? Without going into too much detail, if you have clients that connect to a DC to run programs that is a big No-No but if you use it just for Administrators to connect than that is fine.

Can all (emphasis on ALL) other computers get out to the Internet fine that are on that subnet? Any weird DNS issues in the domain lately? Double-check that the DNS servers are listed correctly in the TCP/IP properties as well as the default gateway? Is this computer also a DNS server?

If you do an IPCONFIG /ALL on the DC and a computer on the same subnet that can get to the Internet, are the entries pretty much the same?

If so then what has been installed lately in the domain? New proxy server? New NAC appliance? New domain or host-based firewall?

It really sounds like the default gateway was deleted but if you could do some more testing to help narrow it down and let us know what you find. Thanks.

[mizzfit]

Hello,

Thanks for the reply, it ended up being there was a failover program on the PC. When it rebooted the secondary server took control and the router had kept the secondary servers MAC address and thus when the PC pinged the router it was being sent to the secondary server.

Resolution was to reboot the router.

[DragonNOA1]

When in doubt, reboot! Glad you got everything working again.