Windows cannot obtain the domain controller name...

[site4sure]

HELP!

This is the error I am getting in the application log on the client computer

Windows cannot obtain the domain controller name for your computer network. I have joined the domain already, I assume I have the DNS setup right, I can ping it, I can ping the FQDN, I can browse AD, etc etc. The problem we are having is the GPO is not getting passed down. I downloaded the tool from Microsoft to control the GPO's better etc and enforce them. No luck. Rebooted the client comp several times and nothing. Please help. We also have VPN, between the offices and everythings works great there. Thanks

 

[ecunupe]

If you have a vpn between your offices. I would enable userenv logging.

http://support.microsoft.com/default.aspx?scid=kb;en-us;221833.

I would first check DNS by pinging and performing an nslookup. I would then try the article.

 

[site4sure]

Hi,

I actually figured it out. Found an article online that talked about the pinging etc. I made two registry tweaks and it works for the time being. I have to figure out how to make our firewall on the receiving end accept ICMP requests larger than 2K.

 

[ecunupe]

Was the issue group policy minimum transfer rate. I have seen this issue before. Thanks.

 

[site4sure]

Hi,

Yeah it was. I did a registry hack for it. I did another post though on how to fix our firewall. How might I make a custom rule to allow like a 3K ICMP packet?

 

[ecunupe]

Are your clients XP or Win2k? If I remember with Win2k the clients will apply the new policy. The issue is with WinXP. We get caught in a chicken or the egg scenario. If we put the group poliy min transfer rate reg keys in place we can apply group policy. I know that we need icmp to be 1500 bytes. As far at the rule I am not sure.

 

[site4sure]

Hi,

We are all on Win2k. I did both the reg hacks in this article.. and it seems to work, just a pain to do for each user.

http://archives.neohapsis.com/archives/ntbugtraq/2003-q4/0043.html