m oconnell

I am attempting to join a rebuilt BDC (NT4.0) to an
existing domain (NT4.0). This new machine fails to join
the domain - I have done all the recommended steps I have
found in MS support site but am still unable to join the
domain.

Any suggestions?

thanks

michael giorgio - mvp

Without knowing the exact error you are getting while
attempting to join the domain it would hard to give you
any advice. I assume the BDC is on the same subent
as the PDC?

john van staaijeren

Last week I tried to set up a BDC on a different network then the PDC.
This was no possible, whatever we tried, the BDC could not contact the
PDC.......

Solution was to put temporarely the BDC in the same subnet as the PDC and
then later move the BDC to his real place in the WAN.

Strange but it solved the problem.
Never could find the real problem why. Looked in the Knowledge base for a
long time, but no success,

Hope this helps,
John van Staaijeren

scott harding - ms mvp

Most likely an issue with the necessary Netbios ports being open through the
WAN or the BDC not being to find the PDC w/o a Lmhosts file which can be
imported from a floppy during installation. This still may be a problem as
the BDC across the WAN will still need to access the PDC in order to keep
replication going. Are you able to open User Manager on the BDC? This should
tell you if the necessary ports are open or hit shares on the PDC from the
BDC.

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

scrockel@***No_SPAM***hotmail.com

mike

The error I'm getting is 'unable to connect to the domain
controller for this domain. Either the Username or
Password entered is incorrect'
I've checked the error log and I see that it records the
same information on the domain controller. I can login
directly to the domain controller with the same ID and
Password with no problem!
The BDC is on a different segment than the PDC.

thanks,
mike

michael giorgio - ms mvp

This rebuilt BDC was previously a member of the
existing domain you are attempting to join? If not
you cannot do this in NT 4.0 because of a unique
SID or security id.