Resolved New server won't let me log on

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Guys, I have a weird problem for you. Last week I installed a new server 2008 R2 system. It all went well, did all the updates and then joined it to the domain. I come in today, start it up and it wont let me log on. There's no option to change accounts (as if it isn't in the domain) and the local admin password doesn't let me in either. Looking on the DC I see in DHCP it has an address assigned with the FQDN but DNS has nothing and there is no computer account for it either.

Any ideas? If I can't get in in the next hour or so it looks like I might have to scrap the whole system and start again. I have to start installing exchange 2007 today and I think that will take a while.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

have you checked the dns server?

 

You could try booting with Offline NT Password & Registry Editor.
That should enable you to reset the local admin account.

 

Try manually configuring the TCP/IP settings. Servers should never have dynamic IP addresses.

Oh wait.. penny dropped you cant log on.

 

For what? The DNS is working fine, just no entry for the new server in there.

Thanks mate. Tried it but it didn't work.


One thing just came to mind as I'm playing around. Does the local admin account get disabled as part of the process of joining a server 2008 system to the domain?


I'm thinking now that there was a problem when joining to the domain and something was corrupted in the process.

 

No it doesn't get changed... unless you have a group policy in place to change the name of the local admin account.

Next step, check the GPO to make sure that the account name hasn't been changed via that.

 

I was just wondering wether it (new server) should have been manually entered into it.

 

Nope, no GPO to do that. Was thinking about doing that eventually.

Anyway, it's a bit hard to have a GPO running on a computer that doesn't exist in the domain.

I bit the bullet, have done a new install and joined the domain. The computer account has shown up in AD Users and Computers so I hope it's okay now.

Would have liked to have solved this but I don't have the time to mess around anymore.

 

Is a strange one, could have been a replication issues in regards to the computer account not showing.

 

I don't think it is mate.

 

Thats only DC's isnt it!?

 

No it doesn't, it would make working on a server very difficult if you found that you didn't have network access and the local user account was disabled, renamed sure, disabled... asking for a SERIOUS amount of trouble.

 

This was certainly the case on Windows 2000

 

The error message was that the username or password is wrong, you know, the one you get when someone accidentally hits caps lock and doesn't realise it.


Seems to be okay now.