Server 2003 Issues

[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

[Erik]

What is the default gateway? Can other computers on the network ping to it and access the internet? Is the proper default gateway set on the server?

Check and try to disable Windows Firewall, it gives me nothing but headaches on servers.

TS licensing should have nothing to do with this. You will either see errors in the event logs about not having proper licenses or get refused connections when trying to connect.

[mizzfit]

Hey Eric,

Thanks for the reply. I just fixed it at 2:00AM this morning. Firewall was disabled, but I have been struggling with this for about two weeks now. It turns out there is a program called DoubleTake. It was telling the router the wrong MAC address since it provides fail over in case something happens. Removing the program and rebooting the router has finally resolved my nightmare.

BTW: I could still ping locally because only the router was seeing the wrong MAC.

LOL
Thanks for the assistance.