Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

NDS on BDC PLEASE READ!!!!

0 views
Skip to first unread message

Terry6489

unread,
Dec 14, 2000, 11:06:25 AM12/14/00
to
Ok here is my situtation. I have a PDC up and running with NT Server
4.0. It has NDS for NT. (I didn't install the NDS I am kind walking
into this situtation and suppose to untangle everything.) Well I have
a second server identical hardware that I will be useing as a BDC. So
far I have encountered two problems that I have never seen before.

1. When doing a fresh install on the BDC of NT Server 4.0 I get to the
part where it ask me what domain will this particpate in. I choose the
same domain as the PDC is on, it gives me an error, I use administrator
as my username.
"Domain Controller for Network can not be located"
Could this at all be caused by NDS on the PDC not setup properly?

2. When installing NDS on the BDC do I need a differant CD than what
was used for the PDC. Because when I pop the cd in it says its for
only a PDC controller.

Thank you


* Sent from Novell Discussion Forums http://novell.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!

Vikas Mahajan

unread,
Dec 14, 2000, 11:15:40 AM12/14/00
to
Terry,

Do you know which verison of NDS4NT is installed on the PDC? Versions
2.0 and below will require IPX. If you have NetWare 4.x servers in your
tree, then you should also use IPX only.

When setting up the BDC, be sure to configure it as a domain controller
in the same domain as the PDC. NT will try to find the domain using the
NETBIOS name. However, this name is not routable, so it won't find the
name unless you setup the server from the same subnet. I think that
should solve your problem. NDS4NT doesn't get involved with this. Also
make sure your TCP/IP and/or IPX configuration is correct.

Once you successfully make the server a BDC of the domain, apply the
same service pack as on the PDC. Then install NDS4NT on the BDC. The
installation will detect the server is a BDC and simply replace the
samsrv.dll on the BDC so it can talk to NDS. You should use the same
NDS4NT CD as was used on the PDC.

If the NT server is already setup as a member server or standalone
server, it cannot be promoted to a domain controller. You must
re-install NT from Scratch. There are 3rd party utilities available to
make the promotion as well, but they aren't officially supported through
Microsoft.

Good Luck,

--
Vikas Mahajan
Novell Support Connection Volunteer SysOp


0 new messages