Upgrade from 2k3 to 2k8 on a DC causing problems

[Molenski]

Hi there,

We have a secure network and want to upgrade our last 2k3 DC to 2k8R2. As part of this process we powered down our 2k3 DC to allow communications to go ahead with an existing 2k8 DC which was fine all excecpt for one server running 2k3 R2.

As soon as the existing 2k3 DC was powered down, only local logon to the 2k3 R2 server was possible and events were generated in the local event log - Netlogon 5719 this computer was not able to setup a secure session...LSASRV 40960 The security system detected an authentication error for the server --- "There are currently no logon servers available to service the request" and various other events. We have a Server 2k3 (non R2) in the domain which had no authentication problems at all.

nltest /dsgetdc:domainname failed with a 'no such domain error'

Has anyone got any ideas how to progress this or any ideas what the issue could be? As soon as we powered up the DC connectivity between this 2k3 DC and the 2k3 R2 member server was restored and everything was running hunky dory. I thought maybe as a workaround, we could remove the 2k3 R2 server from the domain and then join it with the 2k3 powered down and try and get it on this way. Somewhere in my mind, it seems that this member server has a secure connection with the 2k3 DC and won't switch when it loses this connection i.e. when the 2k3 DC is powered down.

Any ideas would be great.

Thanks in advance,
Molenski

 

[58sniper]

Are other domain controllers also Global Catalogs? And you're not using read-only DCs, right?

Do you have your Tek-Tips.com Swag? I've got mine!

Stop by the new Tek-Tips group at LinkedIn.

 

[Molenski]

This is a secure enviroment so only the two DC's are reachable by the member server and they are both GC's. No RODC's, no.

Thanks for getting back by the way!

 

[58sniper]

And both DCs are in the same AD site, and subnets are properly defined?

Do you have your Tek-Tips.com Swag? I've got mine!

Stop by the new Tek-Tips group at LinkedIn.

 

[Molenski]

Yep, both DC's in the same site and like I say, no other machine having problems. We are going to try removing it and readding to the domain today and see if that makes any difference.