Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I recently transferred my domain controller over to another Windows 2003 server. The old one was retired and disconnected from the network.

I have since found that I can no longer log into my laptop when disconnected from the network. This was never an issue before. I checked the local group policy and Windows Settings\Security Settings\Local Policies\Security Options\Interactive Logon: Number of previous logons to cache... is set to 10. If I restart and remove the ethernet cable before logging in, I get the error stating the log on server could not be found. Once I plug it back in, I can log on.

Everything in the domain seems to work perfectly fine, but for some reason this setting is just not working anymore. Is there another setting somewhere that could be disabling this?

Thanks in advance for any replies.

share|improve this question
    
When you migrated to the new server, did you remember to migrate all the roles? –  user3463 Aug 25 '12 at 21:26
    
Yes. The roles were migrated without issue and the server was able to be decommissioned without causing any hiccups. This is the only issue I have encountered in the whole month of the original server being offline. Not sure if there is something still cached on the local client machine or not though. No clue how to check that. –  TyCobb Aug 25 '12 at 21:33
1  
I'd spend this time removing and re-adding the machine to the domain. It's Windows 7, so you can back up the profile and restore it when it's back online again. –  user3463 Aug 25 '12 at 21:34

1 Answer 1

up vote 0 down vote accepted

Randolph West's comment from original question.

I'd spend this time removing and re-adding the machine to the domain. It's Windows 7, so you can back up the profile and restore it when it's back online again. - Randolph West

That did it! Not a real fan of that being the solution, but it was. Was more hoping the solution would be an obscure setting somewhere. Thanks a lot!

Also it allowed me to see that I had some DNS issues with the dual NICs on the server since I wasn't able to initially join back to the domain.

share|improve this answer
    
I assume that the DNS problem was the real problem. –  Robert Aug 31 '12 at 18:10

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.