0

I had a very odd problem today at work.

An employee couldn't connect to the file server (which is also the DC,DNS,etc). It's our main/only server(other than a print server). anyways, he was receiving a valid NIC/dns/gateway ip and could ping the server fine. Though when I tried to connect via \\server1 it timed out. I tried connecting via \\192.168.0.1 and the same thing happened.


I looked at our DNS service on the server and noticed there wasn't a (A) Host record in the FLZ for his login. I added it and after about 5 minutes he could connect fine.

I'm not convinced this was the problem though. If it was a DNS error, shouldn't I have been able to connect via \\192.168.0.1 ??

2
Contributors
1
Reply
2
Views
10 Years
Discussion Span
Last Post by DimaYasny
0

active directory depends very heavily upon the dns service, for logons and routine work. check your server logs and look up the dns errors on the MS site

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.