No connection to Server

I'm having problems with one of our DC's (We have two) - it has no
connectivity. I'm unable to ping it by name or IP and unable to ping any
names or IPs from it and suspect it's a DNS issue. I've been through the
event logs and seen a 4319 NetBT error and 5781 NetLogon errors which I've
read related to Servers with 2 Nics - the Server does have 2 Nics but one of
those is disabled.

Below is the NetDiag Output, I have rebooted the server, checked DNS is
running and checked for W2K3Server1 entries in DNS - can anyone advise on
next steps?


Computer Name: W2K3Server1
DNS Host Name: W2K3Server1.SOFTDEV.INTERNAL

Netcard queries test . . . . . . . : Passed
[WARNING] The net card 'RAS Async Adapter' may not be working because it
has not received any packets.
[WARNING] The net card 'Intel(R) PRO/1000 EB Network Connection with I/O
Acceleration' may not be working because it has not received any packets.

Per interface results:

Adapter : Default LAN Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : W2K3Server1.local
IP Address . . . . . . . . : 192.168.79.253
Subnet Mask. . . . . . . . : 255.255.255.0
IP Address . . . . . . . . : 192.168.78.28
Subnet Mask. . . . . . . . : 255.255.252.0
IP Address . . . . . . . . : 192.168.76.28
Subnet Mask. . . . . . . . : 255.255.252.0
Default Gateway. . . . . . : 192.168.76.1
Dns Servers. . . . . . . . : 192.168.76.29
192.168.76.28

IpConfig results . . . . . : Failed

[WARNING] Your default gateway is not on the same subnet as your
IP address.

AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Failed
No gateway reachable for this adapter.

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.
No remote names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.

Global results:

Domain membership test . . . . . . : Passed

NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{B15F969C-12F2-40D9-9E4F-4B9F829321FA}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed

IP loopback ping test. . . . . . . : Passed

Default gateway test . . . . . . . : Failed
[FATAL] NO GATEWAYS ARE REACHABLE.
You have no connectivity to other network segments.
If you configured the IP protocol manually then
you need to add at least one valid gateway.

NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Service', <03> 'Messenger Service', <20> 'WINS' names defined.

Winsock test . . . . . . . . . . . : Passed

DNS test . . . . . . . . . . . . . : Passed
[WARNING] The DNS entries for this DC cannot be verified right now on
DNS server 192.168.76.29, ERROR_TIMEOUT.
PASS - All the DNS entries for DC are registered on DNS server
'192.168.76.28' and other DCs also have some of the names registered.

Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{B15F969C-12F2-40D9-9E4F-4B9F829321FA}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{B15F969C-12F2-40D9-9E4F-4B9F829321FA}
The browser is bound to 1 NetBt transport.

DC discovery test. . . . . . . . . : Passed

DC list test . . . . . . . . . . . : Passed

Trust relationship test. . . . . . : Skipped

Kerberos test. . . . . . . . . . . : Passed

LDAP test. . . . . . . . . . . . . : Passed
[WARNING] Failed to query SPN registration on DC
'W2K3Server2.SOFTDEV.INTERNAL'.

Bindings test. . . . . . . . . . . : Passed

WAN configuration test . . . . . . : Skipped
No active remote access connections.

Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information

The command completed successfully

"william" <(E-Mail Removed)> wrote in message
news:fi1un4$tam$(E-Mail Removed)...
> I'm having problems with one of our DC's (We have two) - it has no
> connectivity. I'm unable to ping it by name or IP and unable to ping any
> names or IPs from it and suspect it's a DNS issue.

No it isn't DNS.
If it was DNS you would still be able to ping by IP#.

Possible causes may include:
1. Bad cable
2. Bad Switch port
3. Bad Nic
4. Mis-configured TCP/IP settings
5. Corrupted Nic Driver
6. Corrupted TCP/IP Stack

> Host Name. . . . . . . . . : W2K3Server1.local
> IP Address . . . . . . . . : 192.168.79.253
> Subnet Mask. . . . . . . . : 255.255.255.0
> IP Address . . . . . . . . : 192.168.78.28
> Subnet Mask. . . . . . . . : 255.255.252.0
> IP Address . . . . . . . . : 192.168.76.28
> Subnet Mask. . . . . . . . : 255.255.252.0
> Default Gateway. . . . . . : 192.168.76.1
> Dns Servers. . . . . . . . : 192.168.76.29
> 192.168.76.28
> IpConfig results . . . . . : Failed
> [WARNING] Your default gateway is not on the same subnet as
> your IP address.

There is a name for this that I use....it's called a mess. You *really*
need to reconsider whatever it is that makes you think you have to configure
the nic this way. The nic is identified by the Primary IP#. This number
will be the first one applied to the Nic and it is the one you see when you
go into the *normal* TCP/IP setting without going to the Advanced button.
The Default Gateway must be the same subnet as this Primary IP#.

This might be the root of your problem,...and it might not,...but it
certainly would be an aggravation to the problem. There is rarely a
justifyable reason for a NIC to have more than one IP#,...particularly when
the IP#s aren't even in the same subnet. There is almost always a better
and more cleaner way to handle it that involves having only one IP# on the
Nic.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------