I'm not sure exactly how "far" this is into the upgrade when you see this
(ie, after the point where you select if it is to be a dc or server, etc)
but normally a reboot will just pick things back up. If you add an lmhosts
file with the 1B domain entry etc using the article below, and also possibly
a host file entry for you pdc as well, those will be loaded in cache which
it will look for first and may get it going. Not sure what options it's
giving you when you get that error msg (cancel upgrade, etc) but if you can
abort the upgrade and make the change so much the better. There are a
couple of registry things that can be done here, but sort of hate to do that
via email like this, and would make it a server, not dc, after upgrade.
180094 How to Write an LMHOSTS File for Domain Validation and Other Name
http://support.microsoft.com/?id=180094
Be sure that the 1b etc are showing in cache when you run the nbtstat cmd to
be sure they are loaded in cache properly. If you see the others but not
1b, the most common problem is not having Exactly 20 spaces between the " "
and if you don't see anything, usually its because of a txt file extension
on the lmhosts file so view extensions etc.
Another option would be if you're handing out dns address via dhcp where you
could hand out the new (correct) dns address that way.
Have had limited success editing the dns IP address in registry, but
something that you may consider. Located in
hklm/system/ccs/services/tcpip/parameters/dnsregisteredagapters/xxxxxxxx and
you'll see value for dnsserveraddress and registeredaddresses. These are in
hex.
--
David Brandt
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
