Discussion Locked

No domain server after BDC promotion

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

After I promote my NT4.0 (SP6a) BDC and take down my PDC NT 4.0 (SP6a) I receive a " No Domain server" error message on logon. I can run server manager for domains from the PDC and BDC ,make changes and net account /sync works, It is listed as a domain controller in server manage, I have logged on with both up and I see the logon script is running from the BDC most of the time.( Script is replicated back to both netlogon shares). It doesn't matter if the (original) BDC is promoted and the PDC is demoted automatically on BDC promotion and then taken off line, or just the PDC is taken down, if the (original) PDC is not up, no one can log in and get a roaming profile. Profiles are stored on the BDC and all user have the path in their account(\\bdc\user$\%USERNAME%). NTFS Permission are full for each user and his folder
The one thing that stands out is the previous administrator said the company that demonstrated NT 4.0 for them used a demo NFR copy or a 120 day demo copy and used a utility called Udeployit or something like that to bring it up to a full legal version. This way they did not have to reinstall users, groups and Apps. We have 100 plus CALs and less then that of actual users. We also have a legal LIC for each server.Thanks for any help
Jeff

10 replies

by jeffw

PDC name is PDC BDC is BDC, name stays the same on promotion/demotion. Path used in question is not real just an example so you know roaming profiles still should be available. NT workstations still log on just with a cached profile, and the message"no domain server found. You will be logged on with a local profile" Not sure how they can be authenticated at all if no Domain Controller

by colang

Did you changed name to the server?
Check the wins to tombstone and delete the old entries for that server.
Check if wins or lmhosts identifies as domain controller a wrong machine.
Did you deleted the computer account from server manager? The sid of the domain in the new PDC can be different even the domain name is (or better it seems) the same.
Try to restore the old PDC.
Install a little computer as PDC of a new dummy domain. Let you bdc join the new domain, then reboot and then join again the good domain, and reboot again.
Repeat the Promote/demote procedure without deleting entries from server manager.
Hope it can be the case.
Good Luck

by jeffw

I added a second BDC and promoted it, then rebuilt the old pdc and then promoted it. Seems to work but now I must rebuild the old BDC. It is weird because I know that clients are logging in because I can see BDC01 as the place it is getting the login script. Thanks for the help. Had to delete account fronm server manager ot messenger service fails because of another "PDC" name on the network
Jeff

by agibbs

I had a very similar problem at my office until a few months ago. Different symptoms, but the same cause.

We had a single-server NT network with a PDC that was an older, slower machine. We added a second server, I installed it as a BDC then promoted it to PDC afterwards. Since then everytime I took down the BDC (which was ORIGINALLY the PDC) no one could log on -- the proxy server quit working, basically anything that required authentication wouldn't work.

So, I removed the static mappings for the PDC and BDC from the WINS server, killed any straggler entries in the WINS database & everything works fine now.

by stillatit

You might check LMHOSTS files on all machines. If you previously put in an entry to let your users find the domain faster (with #PRE and #DOM: tags) the stations are going to try the controller you specified, and not even try broadcast or wins.

If your user profiles all point to \\bdc\... then you need a machine named 'bdc' to be visible also.

Some other things to check:
From a user machine, is the user logging into the domain (ignoring the profile issue)? If not, check the 'server' service on the remaining machine, and check permissions on the netlogon share.
From a user station, go to a command prompt and type NBTSTAT -A This will tell you if the server's netbios name is what you think it is.
From a user station, click start, run, and type \\servername where servername is the bdc name. See if the station finds the server.

Good luck.

by hicksdustin

Jeff, your answer may be in your last paragraph. I would seriously suggest reinstalling NT4.0 and the SP's. I have had strange problems in the past with demo and "time bombed" software that was supposedly brought up to full legal, only to find that I had to install a fully legal version for everything to work right.
Probably not the answer you wanted to hear.

Dusty

by jeffw

I think yours may have been the right one. I did reinstall as my comments indicate above, And it seems to work. I guess you get the points:)
I did HAVE to remove the old account, that is why I gave points to you not the first guy
Thanks everyone for all the help
Jeff

This discussion is closed to new replies.