Network dies after apx 1 hour of service

I have a problem with my new windows 2003 ES server. It is a standalone
server, so it is it's own domain controller, and it's running terminal
services. I have also installed Real VNC so that I can access the console
remotely.

There are two network cards. One is on an internal (192.168) network and it
is currently disabled. The other is on a public network. The problem I have
is that after a reboot it works properly for about an hour and then it stops
communicating with the outside world. I was on it remotely through VNC and
the session just died. Terminal services stopped working too.

I can ping the NIC remotely and get a response. But if I log onto the
server from the console, it won't even ping the gateway. It's probably a
routing table update of some kind, but I did a route print and it looked like
it should. I'm totally stumped.

Figured it out. Had two servers with the same IP address. One was an
internal VLAN on our web server that didn't have a DNS entry.

"Doug P" wrote:

> I have a problem with my new windows 2003 ES server. It is a standalone
> server, so it is it's own domain controller, and it's running terminal
> services. I have also installed Real VNC so that I can access the console
> remotely.
>
> There are two network cards. One is on an internal (192.168) network and it
> is currently disabled. The other is on a public network. The problem I have
> is that after a reboot it works properly for about an hour and then it stops
> communicating with the outside world. I was on it remotely through VNC and
> the session just died. Terminal services stopped working too.
>
> I can ping the NIC remotely and get a response. But if I log onto the
> server from the console, it won't even ping the gateway. It's probably a
> routing table update of some kind, but I did a route print and it looked like
> it should. I'm totally stumped.
>