New Domain Controller Problem

[glennda]

I am having trouble with a newly promoted DC, i am getting an 1054 error, "Windows cannot obtain the domain controller name for your computer network" (an unexpected network error occurred), i have run dc diag and i get no errors, i have run net diag aswell which is also giving no errors, from google i can see that there was a problem with sp1 that can cause similar problems but the problem was solved with SP2 which has been installed. I have also seen one other forum post that said it could have been a dodgy network lead - but its a virtual server so that has ruled that out.

 

But Im abit stumped. the only thing i can think of is either demote it and see if the error still occurs - but before i promoted it from a member to dc there is no userenv errors.

 

Any one come across this before and know a fix? or something to try

 

Toby

[Michael]

What Server OS are you running? 2003 SP2 /2003 SP2 R2 or 2008 SP2 /2008 SP2 R2? Adding the server to the network as a member server should be fine, but 2003 SP2 and 2003 SP2 R2 have different schema versions for example. They need to match.

[glennda]

What Server OS are you running? 2003 SP2 /2003 SP2 R2 or 2008 SP2 /2008 SP2 R2? Adding the server to the network as a member server should be fine, but 2003 SP2 and 2003 SP2 R2 have different schema versions for example. They need to match.

 

Sorry i realised that as soon as i had posted that i missed the os!

 

we are using 2 x 2k3 dc's (the new one being this) and one old 2k3 r2 which i am replacing with the new one. they are all sp2 and all have the latest updates.

 

Edit: neither of the old dc's have the error

[glennda]

Is this an computer with an AMD processor?

 

If so you need the AMD Opteron Core driver and it will fix the problem instantly.

 

I had this error on my Proliant ML-115's.

 

Nope its a virtual machine which has a Qemu Virtual CPU (using KVM on Ubuntu as host). The thing is the clients don't seem to be having a problem - its just the server is not liking something

 

Toby

[Michael]

we are using 2 x 2k3 dc's (the new one being this) and one old 2k3 r2 which i am replacing with the new one. they are all sp2 and all have the latest updates.

 

Sorry you've just confused me more. Could you confirm what you're using? 2 x 2003 DCs, then I don't understand the rest.

[glennda]

In total at the moment there at 3 dc's. the new one with the problem being a server 2003 sp2 standard edition one.

 

the other 2 consist of a 2k3 standard, and a 2k3 r2. One of which I eventually plan to demote/remove.

 

Make sense?

[zag]

So the DC your trying to add is older than your schema?

[glennda]

I have both types of dc - which i didn't actually realise until Michael asked which OS it was as i didn't build either of them the one with all the roles is the 2k3 normal server - which was made a dc after the 2k3 r2 server was - so i am told by the NM.

 

Im guessing its probly best to demote it again - remove then create a new vm which is 2k3 r2 then promote it back to being a domain controller??

 

or can i just upgrade the server to 2k3 r2 with demoting it etc??

 

Toby

[Michael]

In total at the moment there at 3 dc's. the new one with the problem being a server 2003 sp2 standard edition one.

 

the other 2 consist of a 2k3 standard, and a 2k3 r2. One of which I eventually plan to demote/remove.

 

Make sense?

 

Perfect sense, thanks If you already have a 2003 R2 SP2 the schema must be 31 or greater, as technically you could upgrade the schema to 44 (2008 Server) without running 2008 Server.

 

the one with all the roles is the 2k3 normal server - which was made a dc after the 2k3 r2 server was

 

This makes sense also. The primary DC or role holder essentially dictates the schema version, so when another DC is added it adopts the schema version which more than likely is 31.

If you were to upgrade to 2008 Server, you'd update the schema on your primary DC or role holder only to 44 and this would replicate to your other 2003 DC Servers. You could then in theory add a 2008 Server later on.

 

Back to your problem, it's beginning to smell like DNS. Configure the new server with a static IP and make sure the primary DNS points to your existing primary DC. You then try pinging the IP to see if it works OK.

Once successful and promoted to a DC, you need to change the primary DNS so each of your servers points to itself first then each other.

Edited March 25, 2010 by Michael

[Michael]

Edit, apologies double post.

[glennda]

Back to your problem, it's beginning to smell like DNS. Configure the new server with a static IP and make sure the primary DNS points to your existing primary DC. You then try pinging the IP to see if it works OK.

Once successful and promoted to a DC, you need to change the primary DNS so each of your servers points to itself first then each other.

 

they are set like that - that's is what confused me - they can both see each other and talk to each other fine there is no file replication errors apart from about 3/4 mins after i promoted it - which was saying that it hadn't quite replicated everything across from the old dc's - its set to see each itself via 127.0.0.1 rather then its 192.168.xx.xx which was how i was taught it should be done.

 

The group policy error is ever 5-10 mins i can't remember which, but its constantly happening. The error did not occur before it was promoted it had been a dns/dhcp server before for 24 hours before i actually got round to promoting the server - so it has to be something to do with it being promoted to a domain controller but im not sure what! but there seems no problems with clients but this machine itself not seeing a domain controller!

[Michael]

its set to see each itself via 127.0.0.1 rather then its 192.168.xx.xx which was how i was taught it should be done.

 

It shouldn't make any difference, but change the primary DNS on each DC to its real static IP address instead of 127.0.0.1. Then force replication manually and check the event logs.

[glennda]

Sorted this problem in the end - was a bug with server 2003 and multi-processors

 

This article states the fix kb938448 Shame the search results for the event id error don't bring this straight up.

 

Thanks anyways