Trust problem b/t workst & PDC

Every time you change a name of a workstation, you need to re-add it to nt server. In the Server Maniger, delete all the non-functioning coputer names. Then go to each of the workstations and add them back into the domain by changing the workstation domain and checking the box that tells the computer to add itself to domain. Enter in the Admin username and password. This will establish the trust between the workstation and the server. Make sure that you logon to the domain instead of the workstation for full benifits of the domain.
hope this helps,
-juan

What you describe with the local logons may not be a problem, depending on the share permissions. A local logon to a domain member NT box is a member of the domain's Everyone group, but not necessarily any other domain Global groups. You can test this by creating some shares permitted to other machines' local groups.

What you describe with the trusts is definitely a problem. When you enter a machine name into Server Manager, or join a domain with the "Add to Domain" option, the Domain Controller listens for the first NT machine that comes up with that name. It logs the machine name with the security token to establish the trust. If the machine name is changed, or the security token changes (for example, from a re-installation of the OS), the trust is broken.

Someone may be changing machine names without authorization or using an improper procedure. A technique that works for me is as follows:

Put SVRMGR.EXE on a network share which is available only to DOMAIN ADMINS. Ialso like to put USRMGR.EXE there. This allows you to administer machine and user accounts from any NT Server or Workstation in the domain, so you don't have to be physically at the server all the time.

Then, from a working computer in the same area as the bad one, log in with your Domain Admin ID and run SRVMGR.EXE (Server Manager). Add a new Workstation or Server name into the domain.

Then go to your offending PC, change to the new name and make it a member of the domain (without the "Add to Domain" option), and reboot. Then, go back to Server Manager and refresh the screen. If the new computer name's icon is blue (activated) then you can delete the old computer name, knowing that a fresh trust is established. If it's gray (inactive), you can troubleshoot the PC's network connection and software.

I'm out of space. If you need more info contact me through the peer directory.

Good fortune,
Don

The server lost its secure channel to the PDC,
To get this server back on the domain
1 Remove the computer account from the PDC server manager and manually synchronize with the BDC if you have one.
2 on the member server change it from domain to workgroup and reboot
3 when the server comes backup in Workgroup mode, You can now rejoin the domain you can create a computer account from the member server or create it on the PDC before joining the Member server to the domain.

P.S. All Domain controller?s and member servers use the Secure Channel. Member servers are easy to reestablish the Secure Channel as you can see from above. Primary and backup Domain controller the above won?t work because you can?t put a PDC or BDC in workgroup mode. In order to restore the channel on Domain Controllers you need NETDOM off the NT Resource Kit the help file will give instruction on use.

I hope this helps
George-

NETDOM /Domain:mydomain /User:mydomain\AUser /Password:apassword
BDC mybdc /ADD
NETDOM /Domain:mydomain BDC mybdc /ADD
NETDOM /Domain:mydomain BDC mybdc /DELETE
NETDOM BDC mybdc /QUERY
NETDOM BDC mybdc /RESET <------- this one works well for BDC

Netdom Help vers. ? copyright Microsoft Corporation 1996-1997