Link to home
Start Free TrialLog in
Avatar of Drizzt420
Drizzt420

asked on

DNS Troubles?

I have a member server and 1 domain controller in my entire network. My member server logs into the domain with no problem, views and uses network shares with no problem, recieves DHCP info from this DC with no problem, etc. But if I try to view active directory users and computers from this machine, I get this message: "Naming information cannot be located because No authority could be contacted for authentication..." I actually reformatted the member server and started over, it worked fine for about an hour then went back to giving me this message. I also lost the ability to access the internet via NAT at this time, I cannot even access the net in the DC anymore unless I disable the private interface net card, everything was working fine earlier today - Whats going on?
Avatar of netnightmare
netnightmare

If you do ipconfig /all from the member server does it list the IP of the DNS server? When you lose connectivity can you still ping the DC by IP and NETBIOS? I suspect it isn't getting this properly from the DHCP service. Try statically assigning the IP and DNS server IP addresses and see if this resolves it.

Dave
Avatar of Drizzt420

ASKER

I can ping the domain from the member using name and ip, vice versa is also true. I can delete all the dns entries for member server and do a succesful /registerdns

I DO NOT lose connectivity ever, I simply cannot view the active directory from the member server, which is preventing me from installing Exchange 2000 on this box
Do you have have 2 network interfaces?
what service pack are you running? I used to have this problem a couple of years ago after first upgrading my domain. i, too, thought it was dns related. ipconfig /flushdns would fix the problem for awhile, but it would always return.

i also noticed that when the problem would occur and i would try to ping my domain controller (or anything else for that matter), it would reply with its netbios name rather than the fqdn. i finally solved the problem by disabling the 'dns client' service on my pc, and any other affected boxes. apparently what happens is the client has a dns cache which it checks before querying the dns server. for whatever reason, the client 'forgets' to go out and query the server whenever something isn't in its cache, and then you get all sorts of freaky problems.

so, disabling the dns client service causes the machine to always query the dns server. a little more traffic, sure, which i was more than willing to accept to get rid of such a frustrating problem.

btw, you can disable the service through windows group policy. very convenient if you decide to turn it off on a large number of clients.

hth,
kris.
does the server reference the DC DNS?

try this on the DC DNS:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;300202

I had same problem.  This fixed it.

Alton
ASKER CERTIFIED SOLUTION
Avatar of Laith98
Laith98

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial