Have an old Windows NT domain with no BDC. Eventually will disband the
domain (rather than migrate to Windows 2003) however, in the interim, I
would like to set up a BDC. I run the install for Windows NT Server and
choose BDC as the configuration. However, when I get to the point to where
it says: “You must supply the name of the domain that this Backup domain
controller will participate on and an Administrators name and password that
has the rights to add Backup Domain controllers to that domain” the process
fails.
I enter the correct domain, administrator name and password for the domain,
but receive the message that it’s unable to connect to the domain controller.
What may be causing the problem?
TIA
Jiri Tuma - 27 Apr 2006 10:48 GMT
Usually it is because your network configuration is incorrect. Most probably
because your network card requires at least SP3 or 4 to be functional.
Unfortunately there is not easy solution for this. You can either install
server as standalone, apply servicepacks and then use third party tool
Upromote to make it domain controller. But this tool was a bit expensive if
I remember correctly.
Or you can try to install BDC server using older hardware compatible with
Windows NT build (and eventually migrate this installation to new hw, but
DCs usually dont like migration). Some people had luck with adding older
network card just for installation and switching to new card after applying
of servicepack.
> Have an old Windows NT domain with no BDC. Eventually will disband the
> domain (rather than migrate to Windows 2003) however, in the interim, I
[quoted text clipped - 3 lines]
> controller will participate on and an Administrators name and password that
> has the rights to add Backup Domain controllers to that domain" the
process
> fails.
>
> I enter the correct domain, administrator name and password for the domain,
> but receive the message that it's unable to connect to the domain
controller.
> What may be causing the problem?
>
> TIA
Robert Moir - 01 May 2006 12:03 GMT
> Have an old Windows NT domain with no BDC. Eventually will disband
> the domain (rather than migrate to Windows 2003) however, in the
[quoted text clipped - 8 lines]
> domain, but receive the message that it’s unable to connect to the
> domain controller. What may be causing the problem?
One possible solution if Jiri's diagnosis turns out to be true is to install
a more modern OS on the hardware and then install Microsoft's Virtual Server
(or the VMWare version if you prefer). Both of these are free and will allow
you to install your BDC as a virtual machine quite happily.

Signature
--
Rob Moir, Microsoft MVP
Blog Site - http://www.robertmoir.com
Virtual PC 2004 FAQ - http://www.robertmoir.co.uk/win/VirtualPC2004FAQ.html
I'm always surprised at "professionals" who STILL have to be asked "Have you
checked (event viewer / syslog)".