Networking Forums

Networking Forums > Computer Networking > Windows Networking > Client computers cannot access Win2003 server

Reply
Thread Tools Display Modes

Client computers cannot access Win2003 server

 
 
Dale Sampson
Guest
Posts: n/a

 
      10-03-2006, 07:43 PM
I recently installed Vista on a system & after playing awhile, decided to
try and join the local domain hosted on Win2003, AD integrated, DNS & IIS
installed. I found I was not able to contact the DC (error no DC). I decided
to compare settings with an XP client already on the network only to
discover I had the same problem - as with all the network clients. After
reading through troubleshooting guides & fooling with it for several days, I
still have no handle on what the problem is.
I'm hoping someone can get me pointed in the right direction ... I'm unsure
what may have occured that hosed things up though it worked not too long ago
as I added a new client (which now has same symptoms as dalespc).

Not too surprising, I attempted to access AD data using MMC snap in - but am
unable to contact the DC. Ditto with domain security stuff.

Network hardware: Linksys broadband router for internet access, gateway
192.168.1.1. Some clients are wired to router, some wireless. DC is wired.
DC is named othercomputer, domain is dalesnet.local. Sample client data is
from dalespc. Local ip & scope is 192.168.1.x, 255.255.255.0.
----------------------------------------------------------------------------------------------
Client data: (DC/Server data below client data)
C:\Documents and Settings\dalesplace.DALESNET>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DALESPC
Primary Dns Suffix . . . . . . . : dalesnet.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dalesnet.local

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
Adapt
er(LNE100TX v4)
Physical Address. . . . . . . . . : 00-20-78-1D-7B-48
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.128
192.168.1.1
-------------------------------------------------------------
Ping data: Notice it finds DC but NOT if the domain is specified.
C:\Documents and Settings\dalesplace.DALESNET>ping othercomputer

Pinging othercomputer [192.168.1.128] with 32 bytes of data:

Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.128:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\dalesplace.DALESNET>ping
othercomputer.dalesnet.local
Ping request could not find host othercomputer.dalesnet.local. Please check
the
name and try again.

C:\Documents and Settings\dalesplace.DALESNET>ping dalespc

Pinging DALESPC.dalesnet.local [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\dalesplace.DALESNET>ping dalespc.dalesnet.local

Pinging DALESPC.dalesnet.local [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
-------------------------------------------------------------------------------
NSloolup: can't find the DNS server at all.....
C:\Documents and Settings\dalesplace.DALESNET>nslookup richpc othercomputer
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.128: Timed out
Server: UnKnown
Address: 192.168.1.128

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Documents and Settings\dalesplace.DALESNET>nslookup richpc 192.168.1.128
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.128: Timed out
Server: UnKnown
Address: 192.168.1.128

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
--------------------------------------------------------------------------------------------
NLTEST: can't find the DC using NETBIOS but can via DNS or IP....
C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dcli
st:dalesnet.local
Cannot find DC to get DC list from.Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
The command completed successfully

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dcli
st:dalesnet
Cannot find DC to get DC list from.Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
The command completed successfully

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dsge
tdc:dalesnet.local /dns
DC: \\othercomputer.dalesnet.local
Address: \\192.168.1.128
Dom Guid: d6f8b2ff-f0b3-40ea-8167-39d37c116182
Dom Name: dalesnet.local
Forest Name: dalesnet.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST
CLOSE_SITE
The command completed successfully

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dsge
tdc:dalesnet.local /netbios
DsGetDcName failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dsge
tdc:dalesnet.local /ip
DC: \\othercomputer.dalesnet.local
Address: \\192.168.1.128
Dom Guid: d6f8b2ff-f0b3-40ea-8167-39d37c116182
Dom Name: dalesnet.local
Forest Name: dalesnet.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST
CLOSE_SITE
The command completed successfully

*** here if finds the NETBIOS domain name, but not the DNS domain name ?????

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dcname:dalesnet
PDC for Domain dalesnet is \\OTHERCOMPUTER
The command completed successfully

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dcna
me:dalesnet.local
NetGetDCName failed: Status = 2453 0x995 NERR_DCNotFound
-----------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------
SERVER DATA
Windows IP Configuration

Host Name . . . . . . . . . . . . : othercomputer
Primary Dns Suffix . . . . . . . : dalesnet.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : dalesnet.local

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : dalesnet.local
Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
Adapter(LN
E100TX v4) #2
Physical Address. . . . . . . . . : 00-20-78-1F-DB-D1
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.128
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.128
-----------------------------------------------------------------------------
E:\Documents and Settings\dalesplace.DALESNET.000>nltest
/serverthercomputer /
dsgetdc:dalesnet
DC: \\OTHERCOMPUTER
Address: \\192.168.1.128
Dom Guid: d6f8b2ff-f0b3-40ea-8167-39d37c116182
Dom Name: DALESNET
Forest Name: dalesnet.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_FOREST CLOSE_SITE
The command completed successfully

E:\Documents and Settings\dalesplace.DALESNET.000>nltest
/serverthercomputer /
dsgetdc:dalesnet.local
DC: \\othercomputer.dalesnet.local
Address: \\192.168.1.128
Dom Guid: d6f8b2ff-f0b3-40ea-8167-39d37c116182
Dom Name: dalesnet.local
Forest Name: dalesnet.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST
CLOSE_SITE
The command completed successfully
---------------------------------------------------------------------------
Ping correctly recognized the host as belonging to the domain
Pinging DALESPC.dalesnet.local [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

E:\Documents and Settings\dalesplace.DALESNET.000>ping othercomputer

Pinging othercomputer.dalesnet.local [192.168.1.128] with 32 bytes of data:

Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.128:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
---------------------------------------------------------
DCDIAG DATA: http://www.dalesplace.net/dcdiag2.txt
this shows root hints errors - even though I replaced them from \dns\sample\
as per KB Q249868
NetDiag DATA: http://www.dalesplace.net/NetDiag.log



 
Reply With Quote
 
 
 
 
Robert L [MVP - Networking]
Guest
Posts: n/a

 
      10-04-2006, 02:04 AM
Have you changed any thing recently, for example othercomputer's IP? This search result may help,

Nslookup Troubleshooting Nslookup.exe. 1. *** Can't find server name for address wxyz : Timed out. Cause: the DNS server cannot be reached or the service is not ...
www.chicagotech.net/nslookup.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Dale Sampson" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
I recently installed Vista on a system & after playing awhile, decided to
try and join the local domain hosted on Win2003, AD integrated, DNS & IIS
installed. I found I was not able to contact the DC (error no DC). I decided
to compare settings with an XP client already on the network only to
discover I had the same problem - as with all the network clients. After
reading through troubleshooting guides & fooling with it for several days, I
still have no handle on what the problem is.
I'm hoping someone can get me pointed in the right direction ... I'm unsure
what may have occured that hosed things up though it worked not too long ago
as I added a new client (which now has same symptoms as dalespc).

Not too surprising, I attempted to access AD data using MMC snap in - but am
unable to contact the DC. Ditto with domain security stuff.

Network hardware: Linksys broadband router for internet access, gateway
192.168.1.1. Some clients are wired to router, some wireless. DC is wired.
DC is named othercomputer, domain is dalesnet.local. Sample client data is
from dalespc. Local ip & scope is 192.168.1.x, 255.255.255.0.
----------------------------------------------------------------------------------------------
Client data: (DC/Server data below client data)
C:\Documents and Settings\dalesplace.DALESNET>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DALESPC
Primary Dns Suffix . . . . . . . : dalesnet.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dalesnet.local

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
Adapt
er(LNE100TX v4)
Physical Address. . . . . . . . . : 00-20-78-1D-7B-48
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.128
192.168.1.1
-------------------------------------------------------------
Ping data: Notice it finds DC but NOT if the domain is specified.
C:\Documents and Settings\dalesplace.DALESNET>ping othercomputer

Pinging othercomputer [192.168.1.128] with 32 bytes of data:

Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.128:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\dalesplace.DALESNET>ping
othercomputer.dalesnet.local
Ping request could not find host othercomputer.dalesnet.local. Please check
the
name and try again.

C:\Documents and Settings\dalesplace.DALESNET>ping dalespc

Pinging DALESPC.dalesnet.local [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\dalesplace.DALESNET>ping dalespc.dalesnet.local

Pinging DALESPC.dalesnet.local [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
-------------------------------------------------------------------------------
NSloolup: can't find the DNS server at all.....
C:\Documents and Settings\dalesplace.DALESNET>nslookup richpc othercomputer
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.128: Timed out
Server: UnKnown
Address: 192.168.1.128

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Documents and Settings\dalesplace.DALESNET>nslookup richpc 192.168.1.128
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.128: Timed out
Server: UnKnown
Address: 192.168.1.128

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
--------------------------------------------------------------------------------------------
NLTEST: can't find the DC using NETBIOS but can via DNS or IP....
C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dcli
st:dalesnet.local
Cannot find DC to get DC list from.Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
The command completed successfully

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dcli
st:dalesnet
Cannot find DC to get DC list from.Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
The command completed successfully

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dsge
tdc:dalesnet.local /dns
DC: \\othercomputer.dalesnet.local
Address: \\192.168.1.128
Dom Guid: d6f8b2ff-f0b3-40ea-8167-39d37c116182
Dom Name: dalesnet.local
Forest Name: dalesnet.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST
CLOSE_SITE
The command completed successfully

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dsge
tdc:dalesnet.local /netbios
DsGetDcName failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dsge
tdc:dalesnet.local /ip
DC: \\othercomputer.dalesnet.local
Address: \\192.168.1.128
Dom Guid: d6f8b2ff-f0b3-40ea-8167-39d37c116182
Dom Name: dalesnet.local
Forest Name: dalesnet.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST
CLOSE_SITE
The command completed successfully

*** here if finds the NETBIOS domain name, but not the DNS domain name ?????

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dcname:dalesnet
PDC for Domain dalesnet is \\OTHERCOMPUTER
The command completed successfully

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dcna
me:dalesnet.local
NetGetDCName failed: Status = 2453 0x995 NERR_DCNotFound
-----------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------
SERVER DATA
Windows IP Configuration

Host Name . . . . . . . . . . . . : othercomputer
Primary Dns Suffix . . . . . . . : dalesnet.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : dalesnet.local

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : dalesnet.local
Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
Adapter(LN
E100TX v4) #2
Physical Address. . . . . . . . . : 00-20-78-1F-DB-D1
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.128
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.128
-----------------------------------------------------------------------------
E:\Documents and Settings\dalesplace.DALESNET.000>nltest
/serverthercomputer /
dsgetdc:dalesnet
DC: \\OTHERCOMPUTER
Address: \\192.168.1.128
Dom Guid: d6f8b2ff-f0b3-40ea-8167-39d37c116182
Dom Name: DALESNET
Forest Name: dalesnet.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_FOREST CLOSE_SITE
The command completed successfully

E:\Documents and Settings\dalesplace.DALESNET.000>nltest
/serverthercomputer /
dsgetdc:dalesnet.local
DC: \\othercomputer.dalesnet.local
Address: \\192.168.1.128
Dom Guid: d6f8b2ff-f0b3-40ea-8167-39d37c116182
Dom Name: dalesnet.local
Forest Name: dalesnet.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST
CLOSE_SITE
The command completed successfully
---------------------------------------------------------------------------
Ping correctly recognized the host as belonging to the domain
Pinging DALESPC.dalesnet.local [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

E:\Documents and Settings\dalesplace.DALESNET.000>ping othercomputer

Pinging othercomputer.dalesnet.local [192.168.1.128] with 32 bytes of data:

Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.128:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
---------------------------------------------------------
DCDIAG DATA: http://www.dalesplace.net/dcdiag2.txt
this shows root hints errors - even though I replaced them from \dns\sample\
as per KB Q249868
NetDiag DATA: http://www.dalesplace.net/NetDiag.log



 
Reply With Quote
 
Dale Sampson
Guest
Posts: n/a

 
      10-04-2006, 03:42 PM
Bob,

Same IP since install of win2003. From the client systems, NSLOOKUP doesn't see the DNS even using the server's IP.
PING -a cannot resolve the server name. NLTEST using NetBIOS can't resolve the DC but using DNS it can. Network Browser DOES see all the computers in the domain including the DC. But if I try to connect to DC using an MMC snapin such as AD it can't find the DC. I even tried adding an lmhost record for the DC (192.168.1.128 Othercomputer #PRE #DOM:dalesnet.local) yet ping othercomputer.dalesnet.local returns error: Ping request could not find host othercomputer.dalesnet.local. Please check
the name and try again. Interestingly enough, no network packets are even sent for this ping (monitor using ethereal) - ping doesn't even try to send an ICMP.

I really am at a loss.

Oh, the 'new' addition to the network is the router/gateway. I did change form a Linksys wired (BEFSR41) to a wired/wireless linksys WRT54GS - I can't see that this should matter though.

Any suggestions ideas would be appreciated ...

--
Dale Sampson
http://www.dalesplace.net
"Robert L [MVP - Networking]" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Have you changed any thing recently, for example othercomputer's IP? This search result may help,

Nslookup Troubleshooting Nslookup.exe. 1. *** Can't find server name for address wxyz : Timed out. Cause: the DNS server cannot be reached or the service is not ...
www.chicagotech.net/nslookup.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Dale Sampson" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
I recently installed Vista on a system & after playing awhile, decided to
try and join the local domain hosted on Win2003, AD integrated, DNS & IIS
installed. I found I was not able to contact the DC (error no DC). I decided
to compare settings with an XP client already on the network only to
discover I had the same problem - as with all the network clients. After
reading through troubleshooting guides & fooling with it for several days, I
still have no handle on what the problem is.
I'm hoping someone can get me pointed in the right direction ... I'm unsure
what may have occured that hosed things up though it worked not too long ago
as I added a new client (which now has same symptoms as dalespc).

Not too surprising, I attempted to access AD data using MMC snap in - but am
unable to contact the DC. Ditto with domain security stuff.

Network hardware: Linksys broadband router for internet access, gateway
192.168.1.1. Some clients are wired to router, some wireless. DC is wired.
DC is named othercomputer, domain is dalesnet.local. Sample client data is
from dalespc. Local ip & scope is 192.168.1.x, 255.255.255.0.
----------------------------------------------------------------------------------------------
Client data: (DC/Server data below client data)
C:\Documents and Settings\dalesplace.DALESNET>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DALESPC
Primary Dns Suffix . . . . . . . : dalesnet.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dalesnet.local

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
Adapt
er(LNE100TX v4)
Physical Address. . . . . . . . . : 00-20-78-1D-7B-48
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.128
192.168.1.1
-------------------------------------------------------------
Ping data: Notice it finds DC but NOT if the domain is specified.
C:\Documents and Settings\dalesplace.DALESNET>ping othercomputer

Pinging othercomputer [192.168.1.128] with 32 bytes of data:

Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.128:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\dalesplace.DALESNET>ping
othercomputer.dalesnet.local
Ping request could not find host othercomputer.dalesnet.local. Please check
the
name and try again.

C:\Documents and Settings\dalesplace.DALESNET>ping dalespc

Pinging DALESPC.dalesnet.local [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\dalesplace.DALESNET>ping dalespc.dalesnet.local

Pinging DALESPC.dalesnet.local [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
-------------------------------------------------------------------------------
NSloolup: can't find the DNS server at all.....
C:\Documents and Settings\dalesplace.DALESNET>nslookup richpc othercomputer
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.128: Timed out
Server: UnKnown
Address: 192.168.1.128

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Documents and Settings\dalesplace.DALESNET>nslookup richpc 192.168.1.128
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.128: Timed out
Server: UnKnown
Address: 192.168.1.128

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
--------------------------------------------------------------------------------------------
NLTEST: can't find the DC using NETBIOS but can via DNS or IP....
C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dcli
st:dalesnet.local
Cannot find DC to get DC list from.Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
The command completed successfully

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dcli
st:dalesnet
Cannot find DC to get DC list from.Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
The command completed successfully

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dsge
tdc:dalesnet.local /dns
DC: \\othercomputer.dalesnet.local
Address: \\192.168.1.128
Dom Guid: d6f8b2ff-f0b3-40ea-8167-39d37c116182
Dom Name: dalesnet.local
Forest Name: dalesnet.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST
CLOSE_SITE
The command completed successfully

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dsge
tdc:dalesnet.local /netbios
DsGetDcName failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dsge
tdc:dalesnet.local /ip
DC: \\othercomputer.dalesnet.local
Address: \\192.168.1.128
Dom Guid: d6f8b2ff-f0b3-40ea-8167-39d37c116182
Dom Name: dalesnet.local
Forest Name: dalesnet.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST
CLOSE_SITE
The command completed successfully

*** here if finds the NETBIOS domain name, but not the DNS domain name ?????

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dcname:dalesnet
PDC for Domain dalesnet is \\OTHERCOMPUTER
The command completed successfully

C:\Documents and Settings\dalesplace.DALESNET>nltest /serverthercomputer
/dcna
me:dalesnet.local
NetGetDCName failed: Status = 2453 0x995 NERR_DCNotFound
-----------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------
SERVER DATA
Windows IP Configuration

Host Name . . . . . . . . . . . . : othercomputer
Primary Dns Suffix . . . . . . . : dalesnet.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : dalesnet.local

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : dalesnet.local
Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
Adapter(LN
E100TX v4) #2
Physical Address. . . . . . . . . : 00-20-78-1F-DB-D1
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.128
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.128
-----------------------------------------------------------------------------
E:\Documents and Settings\dalesplace.DALESNET.000>nltest
/serverthercomputer /
dsgetdc:dalesnet
DC: \\OTHERCOMPUTER
Address: \\192.168.1.128
Dom Guid: d6f8b2ff-f0b3-40ea-8167-39d37c116182
Dom Name: DALESNET
Forest Name: dalesnet.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_FOREST CLOSE_SITE
The command completed successfully

E:\Documents and Settings\dalesplace.DALESNET.000>nltest
/serverthercomputer /
dsgetdc:dalesnet.local
DC: \\othercomputer.dalesnet.local
Address: \\192.168.1.128
Dom Guid: d6f8b2ff-f0b3-40ea-8167-39d37c116182
Dom Name: dalesnet.local
Forest Name: dalesnet.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST
CLOSE_SITE
The command completed successfully
---------------------------------------------------------------------------
Ping correctly recognized the host as belonging to the domain
Pinging DALESPC.dalesnet.local [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

E:\Documents and Settings\dalesplace.DALESNET.000>ping othercomputer

Pinging othercomputer.dalesnet.local [192.168.1.128] with 32 bytes of data:

Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128
Reply from 192.168.1.128: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.128:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
---------------------------------------------------------
DCDIAG DATA: http://www.dalesplace.net/dcdiag2.txt
this shows root hints errors - even though I replaced them from \dns\sample\
as per KB Q249868
NetDiag DATA: http://www.dalesplace.net/NetDiag.log



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Client computers cannot access internet through host pc Shawn Windows Networking 2 05-20-2007 11:23 PM
Non-windows client cannot browse Win2003 server Arnaud Lesauvage Windows Networking 4 08-25-2006 08:38 AM
error 778 when connecting to Win2003 VPN server with Windows XP client Jason Windows Networking 1 05-23-2006 03:25 AM
HELP! Error /w Wireless Client Connecting to Win2003 Server /w IAS, CA Christopher C. Welber Windows Networking 0 11-12-2005 08:30 PM
HELP! Error /w Wireless Client Connecting to Win2003 Server /w IAS, CA Christopher C. Welber Wireless Networks 0 11-12-2005 08:30 PM



1 2 3 4 5 6 7 8 9 10 11