add new BDC problem

[cjkenworthy]

I have installed NT4 onto a basic server, and added SP6. I then trying to join an existing NT4 domain. When I setup networking, it recognises the NIC (standard Intel card, with NT4s own drivers), and installs all of the required services etc... then reboots. Every thing looks fine.

When I arrive back into windows, I am told 'at least one service failed' - referring to the computer browser, server, and the network card itself (and all network related services). I know for a FACT that the NIC works, as it does in win2k, and I can even use Intel's own testing software to verify it. It also tells me that there is not enough server storage space available (only after I install networking, but there is over 15gb of space!) (all in the event log)

I am simply trying to join the domain, as a backup domain controller - it can't even find the domain controller.

(all obvious things i have checked, i.e. network socket not dead etc..., have tried without sp6a, definately connected to teh correct switch etc.)

I recall this happened also with another server i tried to add to the domain, in the end i gave up and installed win2k)

I really need help on this one ASAP - any pointers? I can get exactly what its says in the event log.

 

[Stiddy]

Just a quick tip, usless you have some kind of third party software such as "Uprmote" you can not add a BDC to the NT4 doamin without completely reinstalling. You can though add the server as a member server or some call it an application server.

Secondly, how is the machine resolving hostnames? Here is a way that you can check. From the command you should be able to resolve the Primary domain controllers hostname like such:

nslookup ThePDCsHostname


If the above command does not resolve the hostname of the PDC, then the machine will never join the domain. You then have a DNS problem. See what you got and post back.

HTH - Mike

 

[Andyleates]

Whenever I get the "no enough server storage space" message, I always check that the registry has enough room to expand.

May or may not help you!

Andy

Andy Leates MCSE CCNA MCP+I

 

[cjkenworthy]

Cheers,

The BDC is a re-install, i.e. a brand new clean install, I can't even seem to add it to the domain as a member server either!

I'll try an nslookup- I am sure the DNS settings are correct because I add machines every day to the network, and they go on fine (Win2k clients).

Am I doing the correct proceedure? I simply want to add another BDC.

Can I join as member server, to get it onto the domain- then make it an additional BDC??

 

[tahoe2]

In the event log it should say if the service failed due to a logon error. If thats the case, check to see what account the services are starting under and make sure you have the right password in there.

Hope this helps!

Corie

 

[Andyleates]

As Stiddy said earlier, you can't upgrade a member server to a BDC. Unless you have some (dodgy) third party software that will bodge it for you!

Andy Leates MCSE CCNA MCP+I

 

[cjkenworthy]

I see - so the only option to add another server as a BDC is at installation (the first wizard that appears)?

When attempting to locate the domain controller, does the new BDC server attempt to use the DNS/WINS IP settings specified?

The damn server really can't see the domain at all! Is there any way to add the BDC manually on the PDC? I am aware of 'server manager' - at what point do i add the computer to the server manager as a new BDC, or does it appear automatically?

 

[Stiddy]

cjkenworthy,

Yes the BDC will have to use DNS or Wins or an lmhosts file.

You could in server manager manually add an account for the BDC on the domain but you should not have to do that for the installation should automatically create the account for you. Are you positive that when you are using the (the first wizard that appears)? that you are supplying a domain account that has rights to add the BDC to the domain. Simply using an account that can add machines to the domain does not nessasarily mean that the account can add BDC's to the domain.

 

[GregDarby]

Just a silly question - You don't say if you can actually ping the PDC. Of course if you can't and your NIC is not functioning correctly in NT4 how on earth can you expect to connect to the PDC in the first place ???

 

[ajtmcse]

Guys,

If he's having the problem during a clean install then he isn't getting far enough into the OS to do a ping or traceroute.

You need to check the basics again:
- Is the NIC good?
- is the patch cable good?
- are you using the right NIC driver? Download the latest from the manufacturer.
- Is the NIC set to the same speed/duplex as the hub/switch port?
- Plug another pc into that hub/switch port and confirm it works.
- Confirm subnet mask, wins, and gateway addresses.

It HAS to be one of those items.

 

[cjkenworthy]

-NIC is good as it works with other OS (win2k)
-Patch is good for same reason, I have tested it all in win2k, as it was previously a client
-Is the right NIC driver, WINNT's own, the NIC lights are on displaying 'active' and the 100Mbps light is on - it even flashes with actvity when the switch does!
-Have had another PC in the same switch and confirmed it worked.
-subnet mask etc.. are correct.

I know the settings are correct, as I have copied them from the other servers that are already in the domain (with the exception of not putting in the same computer names/IP address).

Windows NT doesn't even appear to even try to look for the domain, as soon as I press 'Next' the error message "Cannot locate the domain controller for this domain" message pops up.

I am absolutely stumped - as I recall another server did exactly the same when i tried to join the domain, with a completely different hardware setup, so I doubt that it is computer-specific problem.

Is the domain not accepting new servers? - is this possible??

 

[dodgygeezer]

I recently had a similar problem to this with a Compaq server. NT detected and installed the NIC driver, all seemed fine (even the flashing activity light) but no network connection.

Turns out it was the wrong driver.

I suggest you get that cover off, confirm the make and model of the network card and get the latest driver from the manufacturer. Restart installation and when it says it's recognised the card, untick it and click the button to select your own card.

 

[cjkenworthy]

You're an absolute star!

WINNTs drivers were obviously wrong, so I downloaded some from Intel themselves, as a last attempt, and it looks like they work.

You would have thought that NT would have worked with its own supplied drivers?

Now for the next step, upgrading domain to Win2K - see you all in the Win2K forum!!

Thanks to everyone for their prompt responses and suggestions!

 

[ajtmcse]