MEMBER SERVER DOES NOT RECOGNIZE THE PDC

[fitfixer]

I run a small 50+ pc's NT4 Server network with Win98 and W2K clients, a PDC and a BDC, and a member server also running NT4 Server for our SQL database
recently both the PDC and the BDC suffered hard drive failures, while they were down no network log-on was possible, the domain is back up now but this member server seems to be using itself as the log-on server, it will not trust clients who have logged-on to the PDC
I have checked that the domain name is the same and the IP addresses are the same as before, but the only way I can work around this is to set up an account for each user on this breakaway server which is not a PDC or BDC
The W2K clients are also having a similar problem recognizing the new NT4 Server installation, the Win98 clients are working OK
I would be grateful for any suggestions

 

[FilthPig]

Remove each NT/2000 machine from the domain and re-add it.

Just in case you're not familiar with how to do that:

NT: Properties of network neighborhood, Identitification tab, change it to a workgroup, hit OK, don't reboot yet, go back into change and re-add it to the domain, then reboot.

2000: Properties of My Computer, Network Identification Tab, Properties button, change to workgroup, hit OK, don't reboot, go back into properties and re-join domain, hit OK, reboot. Marc Creviere

 

[jtb]

I would have given a star to Marc; but I just don't feel right because of the handle... JTB
Solutions Architect
MCSE-NT4, MCP+I, MCP-W2K, CCNA, CCDA,
CTE, MCIWD, i-Net+, Network+
(MCSA, MCSE-W2K, MCIWA, SCSA, SCNA in progress)

 

[fitfixer]

Thanks for the tip Marc, I'll give you a star for that,
I tried this with one of the W2K PC's, for good meausure i did it at the PDC as well, it gave a message saying that it would take 15 minutes to update the list, but it worked!

I rejoined the client to the domain and the login worked
On Monday I will try it on the member server, I will let you know how I do
Thanks
F.Farrell
MCSE wannabee

 

[meastaugh1]

Another thing you might want to try if the above suggestions don't work...

1) Create a new temp computer account for the standalone server on the domain.
2) Change the server name to the new temporary name and reboot.
3) Delete the old computer account for the server from the domain.
4) Recreate the old computer account for the server.
5) Change server name back to original and reboot.

*You must 'Synchronise Entire Domain' in server manager between each step.

I've had a similar problem when the PDC has had a hardware fault and been down for a few days. When the PDC comes back online the domain is out of sync. Theres an MS KB article on it somewhere, don't remember it though.

 

[fitfixer]

It worked!
taking the member server out of the domain and then rejoining it sorted out the log-on problem,
The Windows 2000 clients needed this fix also, the only problem is that once you rejoin a W2K client to the domain again, it thinks it has a brand new user and loads a fresh profile, the user loses all her desktop and local settings including e-mail address book and messages
I have to back up each W2K client and then restore to the new profile, is there an easier way to do this?
Thanks for the help
f.farrell

 

[FilthPig]

Right-click on My Computer and select properties, go to the User Profiles Tab, find the old profile, and copy to the new location. Make sure you specify the user who has access to it. Marc Creviere