Network/Server overview: Small subnet consisting of a dozen 2K professionals PC's, a couple of 98 PC's, one file server/domain controller and one member server (both running Windows 2000 server).
Domain controller has its IP in the prefered DNS server settings. The DC is listed in both the forward and reverse lookup zones. Please provide some assistance in this frustrating dilemma.
Tests I have run.
> nslookup 123.34.567.89
server: badgers.mydomain.xyz.abc.mil
address: 123.34.567.89
name: badgers.mydomain.xyz.abc.mil
address: 123.34.567.89
> nslookup mydomain
Server: badgers.mydomain.xyz.abc.mil
Address: 123.34.567.89
DNS request timed out.
timeout was 2 seconds.
*** Request to badgers.mydomain.xyz.abc.mil timed-out
> ls mydomain
[badgers.mydomain.xyz.abc.mil]
*** Can't list domain mydomain: Non-existent domain
> ping badgers
Pinging badgers.mydomain.xyz.abc.mil [123.34.567.89] with 32 bytes of data:
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Ping statistics for 123.34.567.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
>ping badgers.mydomain.xyz.abc.mil
Pinging badgers.mydomain.xyz.abc.mil [123.34.567.89] with 32 bytes of data:
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Ping statistics for 123.34.567.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Domain controller has its IP in the prefered DNS server settings. The DC is listed in both the forward and reverse lookup zones. Please provide some assistance in this frustrating dilemma.
Tests I have run.
> nslookup 123.34.567.89
server: badgers.mydomain.xyz.abc.mil
address: 123.34.567.89
name: badgers.mydomain.xyz.abc.mil
address: 123.34.567.89
> nslookup mydomain
Server: badgers.mydomain.xyz.abc.mil
Address: 123.34.567.89
DNS request timed out.
timeout was 2 seconds.
*** Request to badgers.mydomain.xyz.abc.mil timed-out
> ls mydomain
[badgers.mydomain.xyz.abc.mil]
*** Can't list domain mydomain: Non-existent domain
> ping badgers
Pinging badgers.mydomain.xyz.abc.mil [123.34.567.89] with 32 bytes of data:
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Ping statistics for 123.34.567.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
>ping badgers.mydomain.xyz.abc.mil
Pinging badgers.mydomain.xyz.abc.mil [123.34.567.89] with 32 bytes of data:
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Reply from 123.34.567.89: bytes=32 time<10ms TTL=128
Ping statistics for 123.34.567.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms