Issue joining domain + Outlook/Exchange 2k3 Question

[Thraxen]

When trying to connect a Windows 2000 PC to a Windows Server 2003 domain I have to enter the DNS in the NIC properties manually before it will be able to join the domain. XP PCs do not have this issue, they can connect just fine with the DNS set to automatic. Any ideas what could be causing this and is there a way to fix it?

Now for a different question. I'd like to be able to disable cached exchange mode globally for the domain. I added the Outlook administrative template to the Group Policy of the doman and enabled the option to "Disable cached exchange mode for new profiles". I installed Outlook 2003 on a Win2K PC and the cached exchange mode option was indeed disabled when setting up the user account. But then when installing Outlook on an XP PC the cached exchange mode was available and selected by default. How can I fix this?

Thanks!

 

[RebateMonger]

Regarding the Cached Exchange Mode:

I'd start by running the GPResult tool on the computers configuring correctly and on those not configuring correctly and look for the difference in the Policies they are receiving.

Or, just running RSoP on the XP boxes may help you see where they are getting their Outlook policies.

 

[Thraxen]

OK, I've run into some errors on the XP box trying yor suggestions.

GPResult = The user "blah\blah" does not have RSoP data
RSop = RSoP data is invalid. Likely causes are data corruption, etc... Details: Invalid namespace

If I attempt to run RSoP from the domain controller I get an error stating that I do not have sufficient permission and "Access denied". But I can run RSoP from the DC on any server in the rack, just not the XP box attached to the domain.

 

[RebateMonger]

Well, that's not a good sign. Running RSoP on an XP client should work just fine. Heck, I just ran it as a Limited User (both local and domain) on an XP client in my Domain, and I'm able to see the policies and which GPO they are coming from.

Similarly, I can run GPResult as both a Limited User and as a Domain Administrator and get a full listing of applied Group Policy Objects.

 

[Thraxen]

Any ideas on possible causes and/or solutions?

 

[RebateMonger]

The most common reason for Group Policy errors is DNS problems. Have you checked your DNS Event logs on your servers?

 

[Thraxen]

Hey, you were exactly right. This is a new server rack were are prepping for deployment and we had a typo in the DNS IP address on the DC. We corrected that and now everything is working as expected. Thanks!

[edit] BTW, this obviously fixed the other issue too. I'm not sure how the XP box was able to log on with the wrong DNS, but now both the XP and 2000 box log onto the domain fine with all the TCP/IP configurations set to Automatic.

 

[RebateMonger]

Glad you got it working.

Once in every thousand guesses, I get one right.