Babadoop

April 29, 2008

Windows 2003 DNS search order error

Filed under: Uncategorized — babadoop @ 11:26 pm

I keep running into an issue in our environment where by changing the DNS search order I can get a machine to login to the domain. However, other machines are on the same domain and have no problem logging into the domain.

For example, I have machine1 with the following DNS search order:
DNS1
DNS2

At times, I won’t be able to login; it says the domain is not available. So I login as the local administrator, change the search order to:
DNS2
DNS1

Then I log out, and then log back in as my domain user. No problem. Except this is a stupid solution and even then it doesn’t always work.

I’ve looked at our DNS server and the Active Directory configuration, but I don’t see anything wrong…

On top of this issue, there are times where I can log in as my domain user, yet when I go into the User Groups I can not see the domain object, but instead only see the local computer objects. So at times I can’t add other users to the proper groups because its as if it can’t see the Active Directory….even though I’m logged into the domain with my domain user!

This is becoming a big issue since the Clustering service needs access to the domain account I created for it.

anybody got any ideas? (please refrain from the usual anti-Windows suggestions…you know who you are)

Update: EDL 4100 and NetWorker 7.4 sp2

Filed under: Uncategorized — babadoop @ 3:34 am

So previously I mentioned that I chose a generic Medium Changer. I have since learned that this is not necessary; it was only the drives that needed to be generic.

Blog at WordPress.com.