DC unable to communicate beyond gateway

OK I have a Win2003 Domain controller that cannot get to
the internet or anything beyond the default gateway. I
have chased everything I can think of and It not a DNS
problem since it cannot connect by IP either. However I
have listed all the DNS and other network info below.

This is the PDC DC (DC1) running AD integrated DNS. There
is also a second DC (DC2) with AD integrated DNS as well.
DNS and TCPIP are configured the same on both servers.
DC2 can brose out to the internet. DC1 cannot - it soes
not seem to be able to get any traffic to the internet at
all.. DC1 can ping its default gateway. The NIC IP
configs on DC1 point to DC2 first, then itself.
Both servers are configured to point to each other first,
then themselves. I have tried with and without having an
external DNS server listed in the DC1 servers IP configs
DNS search order.
Both DNS servers have forwarders set to our ISP's DNS
servers.
I have tried removing the forwarders from DC1. No good.

I have run Netdiag on DC1 and the only problem reported is
the standard business of:

Global Results:
You don't have a single interface with the
<00>'Workstation Service', <03>'Messenger
Service',<20>'WINS' names defined.
My understanding is that this is not uncommon.

Route Print looks OK

Internal name resolution against the DNS on DC1 works fine.
NSlookup for DC1 on DC1 works correctly.

Neither server is a root server - no "." Zone listed.
Both servers have standard MS provided root hints.
I am starting to think maybe the IP stack is corrupt
somewhere, but I am not excited about manually removing
the entire IP on a DC.
Any ideas?

Thanks in advance.
Ric

So DC1 can ping anything on the local network including DC2 and the default
gateway- correct? DC2 can ping anything including Internet IP addresses -
correct?
I don't think this is a case of a corrupt IP stack. Have you tried tracert
or pathping to an Internet address to find out how far the packets make it?

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.


"Ric R" <(E-Mail Removed)> wrote in message
news:e37b01c3f0f4$8d9c40e0$(E-Mail Removed)...
> OK I have a Win2003 Domain controller that cannot get to
> the internet or anything beyond the default gateway. I
> have chased everything I can think of and It not a DNS
> problem since it cannot connect by IP either. However I
> have listed all the DNS and other network info below.
>
> This is the PDC DC (DC1) running AD integrated DNS. There
> is also a second DC (DC2) with AD integrated DNS as well.
> DNS and TCPIP are configured the same on both servers.
> DC2 can brose out to the internet. DC1 cannot - it soes
> not seem to be able to get any traffic to the internet at
> all.. DC1 can ping its default gateway. The NIC IP
> configs on DC1 point to DC2 first, then itself.
> Both servers are configured to point to each other first,
> then themselves. I have tried with and without having an
> external DNS server listed in the DC1 servers IP configs
> DNS search order.
> Both DNS servers have forwarders set to our ISP's DNS
> servers.
> I have tried removing the forwarders from DC1. No good.
>
> I have run Netdiag on DC1 and the only problem reported is
> the standard business of:
>
> Global Results:
> You don't have a single interface with the
> <00>'Workstation Service', <03>'Messenger
> Service',<20>'WINS' names defined.
> My understanding is that this is not uncommon.
>
> Route Print looks OK
>
> Internal name resolution against the DNS on DC1 works fine.
> NSlookup for DC1 on DC1 works correctly.
>
> Neither server is a root server - no "." Zone listed.
> Both servers have standard MS provided root hints.
> I am starting to think maybe the IP stack is corrupt
> somewhere, but I am not excited about manually removing
> the entire IP on a DC.
> Any ideas?
>
> Thanks in advance.
> Ric
>

Since Ping only really test ICMP and not TCP or UDP you probably should try
to Telnet to the Default Gateway. Assuming it is a normal router it should
accept the connection. Do not worry about logging into it, that doesn't
matter. If the Router have a Web Inteerface then connect to it with a
Browser.

This will be a more realistic test than Ping.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Ric R" <(E-Mail Removed)> wrote in message
news:e37b01c3f0f4$8d9c40e0$(E-Mail Removed)...
> OK I have a Win2003 Domain controller that cannot get to
> the internet or anything beyond the default gateway. I
> have chased everything I can think of and It not a DNS
> problem since it cannot connect by IP either. However I
> have listed all the DNS and other network info below.
>
> This is the PDC DC (DC1) running AD integrated DNS. There
> is also a second DC (DC2) with AD integrated DNS as well.
> DNS and TCPIP are configured the same on both servers.
> DC2 can brose out to the internet. DC1 cannot - it soes
> not seem to be able to get any traffic to the internet at
> all.. DC1 can ping its default gateway. The NIC IP
> configs on DC1 point to DC2 first, then itself.
> Both servers are configured to point to each other first,
> then themselves. I have tried with and without having an
> external DNS server listed in the DC1 servers IP configs
> DNS search order.
> Both DNS servers have forwarders set to our ISP's DNS
> servers.
> I have tried removing the forwarders from DC1. No good.
>
> I have run Netdiag on DC1 and the only problem reported is
> the standard business of:
>
> Global Results:
> You don't have a single interface with the
> <00>'Workstation Service', <03>'Messenger
> Service',<20>'WINS' names defined.
> My understanding is that this is not uncommon.
>
> Route Print looks OK
>
> Internal name resolution against the DNS on DC1 works fine.
> NSlookup for DC1 on DC1 works correctly.
>
> Neither server is a root server - no "." Zone listed.
> Both servers have standard MS provided root hints.
> I am starting to think maybe the IP stack is corrupt
> somewhere, but I am not excited about manually removing
> the entire IP on a DC.
> Any ideas?
>
> Thanks in advance.
> Ric
>