Server 2003 DC offline for 12 months

[user@domain.invalid]

Hello

We have a client that is setting up a branch in India, due to site
difficulties the Server 2003 DC has been offline for about 12 months.
Just recently the server has been powered up. I have performed a machine
password reset as outlined in Article ID: 325850.
http://support.microsoft.com/kb/325850.

The primary DC in Australia is running fine.

I can browse the remote DC using it's IP address, I.E \\192.168.100.1\
but cannot via its hostname, I.E \\FS1\. I checked nbtstat -n but the
remote server does not appear in the nbtstat list.

I believe that the first hurdle is getting Netbios name resolution
working. Then following this article
http://technet.microsoft.com/en-us/library...630(WS.10).aspx to
remove lingering objects. Is there anything else that needs to be done?

Can you please assist me in resolving the netbios name resolution issue?

 

[Meinolf Weber [MVP-DS]]

Hello user@domain.invalid,

your problems belong to the exceeded tombstone lifetime of the DC, that must
be solved first either with demoting and removing from the AD database, DNS,
AD sites and services according to:
http://support.microsoft.com/default.aspx/kb/555846/en-us

Or check with this articles what has happened and how to be able to maybe
resolve the issues:
http://blogs.dirteam.com/blogs/jorge/archi.../11/24/153.aspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello
>
> We have a client that is setting up a branch in India, due to site
> difficulties the Server 2003 DC has been offline for about 12 months.
> Just recently the server has been powered up. I have performed a
> machine password reset as outlined in Article ID: 325850.
> http://support.microsoft.com/kb/325850.
>
> The primary DC in Australia is running fine.
>
> I can browse the remote DC using it's IP address, I.E \192.168.100.1
> but cannot via its hostname, I.E \FS1. I checked nbtstat -n but the
> remote server does not appear in the nbtstat list.
>
> I believe that the first hurdle is getting Netbios name resolution
> working. Then following this article
> http://technet.microsoft.com/en-us/library...630(WS.10).aspx to
> remove lingering objects. Is there anything else that needs to be
> done?
>
> Can you please assist me in resolving the netbios name resolution
> issue?
>