Problem attaching new NT4 BDC to already Win2kAD domain

[Mike Smith]

I have a Win2k server that was an AD replicator in our
production environment. I pulled it and start it as the
first server in a test environment I am building. It
retained all the AD information correctly and I have added
new Win2000 servers and clients to the domain without
issue.

When i am going through the initial install of a NT4 BDC
and trying to attatch it to the domain i get "domain
controller for this doamin cannot be contacted.

here's what i've checked:

-my nt4 BDC NIC and cables are good. drivers are good. it
is specified for the gateway and dns of the Win2k server.
user name and password to create a new object on domain is
good.

-Win2k server has dns and dhcp funtioning properly and
other objects have been added to domain that are Win2000
and up. i thought is was because the PDC emulator stated
in the FSMO rules still denotes the original DC in the
production environment, so i changed that role to match
the Win2k server of my test environment.

Any ideas? advice? anything is appreciated,

Thanks!

 

[Mike Smith]

-----Original Message-----
And AD is still in mixed mode? And you're sure your DNS is set up right? No
external (ISP) DNS servers listed in the

server/workstation IP configs, with

 

[Lanwench [MVP - Exchange]]

I think you clicked "send" too fast....

server/workstation IP configs, with

 

[Mike Smith]

Yes, sir. still in mixed mode. There's no entries in
host