DC was renamed - now problems

[WalleyeGuy]

Hello All,
Hopefully you all can help.

Our company has taken over another company. The other company was a smaller company with Active Directory running on a single DC. Right now, I cannot take that server down so... I do have a trust going on that is working just fine.

However, in order for us to proceed with IT plans, I have to get another DC running on this system in question.

It appears that at one time they had changed the name of this Domain Controller (W2K3 R2 - Forest and Domain W2K3 Native). When I run a netdiag -v I come up with the below:

Proto Local Address Foreign Address State
OTHER STUFF ABOVE
TCP server-dc01:ldap US-SERVER-DC01:1059 ESTABLISHED
TCP server-dc01:ldap US-SERVER-DC01:1372 ESTABLISHED
TCP server-dc01:ldap US-SERVER-DC01:2155 TIME_WAIT
TCP server-dc01:ldap US-SERVER-DC01:2156 ESTABLISHED
TCP server-dc01:ldap US-SERVER-DC01:2157 TIME_WAIT
OTHER STUFF BELOW

server-dc01 is the current name and US-SERVER-DC01 is the old name. I can't figure where to remove that old server reference from. Been through their DNS and WINS, I don't see anything, nothing in any lmosts or hosts files (they were running an NT4 domain too).

Oh I have my work cut out for me...with this one I think

Hopefully someone here can/will help out as I always find great stuff in the forums here. Thanks ahead of time.

 

[gavm99]

What server names show in AD sites and services?

Gavin Moorhouse

http://www.lucidcomputersolutions.co.uk

 

[WalleyeGuy]

Shows correctly as server-dc01

 

[58sniper]

See if this helps

Rename a domain controller

http://technet2.microsoft.com/windo...f0d2-47d5-b0ea-989081ce62be1033.mspx?mfr=true

netdom is used to tie a new name to a DC for renaming, then used again to remove the old name.

Pat Richard MVP

 

[WalleyeGuy]

I've already done all of that. I even tried to /remove:us-server-dc01 and it comes up with 'no elements found'