NSLOOKUP Failure.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have 350 PCs, a mix of Xp and 2000. Our DNS server is a 2003 server. One
several of our PCs, about 10, the NSLOOKUP fails. Has anyone any ideas where
to look?
 
Si1 said:
We have 350 PCs, a mix of Xp and 2000. Our DNS server is a 2003
server. One several of our PCs, about 10, the NSLOOKUP fails. Has
anyone any ideas where to look?
Click to expand...

Can you be a little more specific?
 
OK.

On a majority of PCs they can access all of our servers with no problems. On
the faulty PCs they can only access our PDC, which is also the DNS server.
When they try to access any other servers there is a network error. When you
try to Ping the servers the PCs cannot identify the server name and when you
try NSLOOKUP on the server names you get a "non-existant domain" error..
 
A bit more info. On the problem machines if I type in nslookup 172.16.132.247
the correct server name comes up. So the reverse lookup is working on these
PCs. Is that any help?
 
Si1 said:
OK.

On a majority of PCs they can access all of our servers with no
problems. On the faulty PCs they can only access our PDC, which is
also the DNS server. When they try to access any other servers there
is a network error. When you try to Ping the servers the PCs cannot
identify the server name and when you try NSLOOKUP on the server
names you get a "non-existant domain" error..
Click to expand...

Would this be the host name of these servers?
If it is then I suspect the DNS suffix search list is incorrect.

Post ipconfig /all from a good machine and a bad machine.
 
We have 350 PCs, a mix of Xp and 2000. Our DNS server is a
2003 server. One
several of our PCs, about 10, the NSLOOKUP fails. Has anyone
any ideas where
to look?
Click to expand...

what fails? please describe more
 
Back
Top