Discussion Locked

verifying NT4.0 wkstns domain membership

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

i have several school sites that all have the same issues. there are 7 sites each with its own individual domain, at this time none of the domains are interconnected, all the domains have a single PDC with no BDC's or Member Servers the largest sitehas about 750 users on about 100 workstations
all the servers are running NT4.0 sp6
all the workstations are running NT4.0 sp5
the workstation accounts apear to be created properly but whan viewed in server manager with show domain members only checked all the workstations apear to be off line, if show domain members is unchecked all the workstations are visable & apear as online

is there any way of verifying that these workstations ar in fact active members of the domain?? this error apears to be causing a variety of logon problems ranging from corrupt profiles & user data to restricted users gaining administrative access.

i DO know that all these workstations have the same SID as they were all setup using ghost without ghost walker to generate unique SIDs. is this the root of my troubles or just another issue???

i have just recently been brought in as a consultant to fix up the problems on this network & this has me stummped..

Thank you for any assistance

Todd Francis
tfrancis_trf@sasktel.net

5 replies

by frobo

Hi Todd,

i am realy wondeering that you haven?t more problems then logonproblems. Normaly their should be more action with same SID on hundret?s of machines.
OK
1.) Take the Nltest.exe from the NT-Reskit,
with this you can check the security channel of the Comp-Account (Oh boy the same SID !!)
2.) ...

Forget all what i wrote. !!
You must first look that you have uniqe SID?s in your Windows-Network. Take the Tool GetSID and put this an an Logon script, Genarte a File with the COMP-Name and the SID.
Take the SID changer Tool from MS (it?s free) and change the SID on these Machines who has got the Same SID. Be care of the Useres Profile, you can change these SID to with the SubinACL Tool from NTReskit.

Hope it helps

Frobo

by rudolph(uk)

It is clear that the problem is repeated SIDs. You could run a test in a small site changing the name of all workstations for unique ones. That would change the SIDs so the problem should disappear in that site.

This discussion is closed to new replies.