ip/dns problem

  • Thread starter Thread starter dan
  • Start date Start date
D

dan

hi, i have a windows 2000 server that until today was ok. today, the
users complained that they could not print to network ip printers. i
noticed that i could not get on the internet from the server. it
could ping ip addresses on the net, but not ping unc stuff like
www.msn.com . i ran netdiag, but it would hang from the start. i
then ran netdiag /debug, and it would hang on "gathering the list of
domain servers for the domain 'united'".

all the work stations can print to the printers, get on the net, and
log into the domain (i only have one server, so its the dc also).

when i go into dns on the server it looks ok, but there was a diffrent
domain other than "united.lan" it was "." i dont know if that normal
or not, but i deleted it in my quest to fix this problem. ive worked
with allot of dns server probelms before, and are allways able to fix
it, this is my first stumper.

any help from this group would be greatley appreciated

dan
mcse cne
 
In
dan said:
hi, i have a windows 2000 server that until today was ok. today, the
users complained that they could not print to network ip printers. i
noticed that i could not get on the internet from the server. it
could ping ip addresses on the net, but not ping unc stuff like
www.msn.com . i ran netdiag, but it would hang from the start. i
then ran netdiag /debug, and it would hang on "gathering the list of
domain servers for the domain 'united'".

all the work stations can print to the printers, get on the net, and
log into the domain (i only have one server, so its the dc also).

when i go into dns on the server it looks ok, but there was a diffrent
domain other than "united.lan" it was "." i dont know if that normal
or not, but i deleted it in my quest to fix this problem. ive worked
with allot of dns server probelms before, and are allways able to fix
it, this is my first stumper.

any help from this group would be greatley appreciated

dan
mcse cne
Click to expand...

Well, if the "." zone exists, and this DNS server is taking care of Internet
name resolution, that's the first thing that needs to be deleted. Then
configure a forwarder to your ISP's DNS. Make sure all the machines (DCs and
Clients) only use the internal DNS server in their IP properties.

Once you've done that, post back with your results and we'll take it from
there.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
if you have the "." zone AND your clients are using this DNS server for
resolution, then they would NOT have been able to resolve any external
record (e.g. www.msn.com). It's surprising that you say they are able to.
Either the clients have already cached those addresses BEFORE the "." zone
was created on your DNS server (very unlikely) or the clients are using
another DNS server that does not belong to you - probably your ISP's (more
likely). But then, you said the clients could access network resources
(printers and logon), so that is even more confusing.

Since the problem appears to be confined to the Server alone, try the
following
delete the "." zone - this you've already done
from cmd, type the following:
net stop dns
net stop dnscache
net stop netlogon
net start dns
net start dnscache
net start netlogon
ipconfig /registerdns

If you don't see a difference, let's hear it.
--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - COMPLETE SPAM Protection
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon


"Ace Fekay [MVP]"
 
Back
Top