General discussion

Locked

domain woes

By KristenK ·
When trying to create a BDC during installation, I got an error message saying that it could not find the PDC. So, I installed the machine as a stand-alone in hopes that I could join the domain once I was up and running. The machine ran through the installation and I am able to ping the PDC from the stand-alone and vice-versa. However, when I tried to join the domain through Network Properties I got the same error message as before. Here's what I have tried already:
1- I tried adding the server through Server Manager on the PDC and it will add it but when you try to look at it's properties it says "the network path was not found".
2- I tried configuring the lmhost file on the PDC and the stand-alone.
3- I have tried simply browsing from one to the other with Network Neighborhood.

Nothing has worked thus far. What am I doing wrong?

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

domain woes

by curlergirl In reply to domain woes

This appears to be a network connectivity or hardware issue. Check the NIC card drivers and the physical portions of the network connection (cables, hubs, etc.) to make sure all is properly connected and configured. Try pinging the loopback address (127.0.0.1) - if this doesn't work it means that TCP/IP isn't working properly - uninstall and reinstall TCP/IP. If that's OK, try moving the server from its current wall jack position to a different one - this checks the cable connection between the wall jack and hub. If that doesn't work, try uninstalling and reinstalling the NIC card drivers. If that doesn't work, try a different NIC card. BTW, you cannot "promote" a member server to a BDC, so if you really want a BDC you will have to start over and reinstall NT from scratch anyway. Hope this helps!

Collapse -

domain woes

by KristenK In reply to domain woes

Even tho' I knew this wasn't a hardware issue, I did re-examine the TCP/IP properties and found an error in the subnet mask settings.

Collapse -

domain woes

by Green Lantern In reply to domain woes

First off - if you create this as a server you CANNOT change it to a Domain Controller without reinstalling. So, if this is supposed to be a BDC you must reinstall again.
Since the machines can ping each other your hard ware is functional. You have a NetBIOS name resolution issue. Is NetBEUI running on both machines? If not, and they are both on the same wire, then setup NetBEUI on the PDC, reboot it and then install your new BDC using just NetBEUI and leave TCP/IP until after you are in.Once you establish your new DC, install TCP/IP, making sure you have a functional LMHOSTS file or a properly running DHCPS server to help resolve your name problem.

ralph

Collapse -

domain woes

by KristenK In reply to domain woes

At this point, I no longer want a BDC. I just want the server to be able to join the domain. As it turned out, it was a TCP/IP problem.

Collapse -

domain woes

by BeerMonster In reply to domain woes

Hi,
In respect of the LMHOSTS file, it's possible that you got caught out the same way I did. The sample lmhosts doesn't tell you this, but there must be a certain number of spaces \ characters in the netbios name of the domain controller as well as a service entry. This is all explained in technet article Q180094 - search for it at microsoft.com\technet ...Hope this helps

Collapse -

domain woes

by KristenK In reply to domain woes

I had actually already read the technet article and configured the lmhosts file accordingly.

Collapse -

domain woes

by KristenK In reply to domain woes

This question was closed by the author

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums