Christo
November 22nd, 2000, 10:58 AM
I have two separate NT 4 servers both in the same domain. Users log onto 1 server, which runs a logon script (DOS batch) which enables mappings to another server. The users exist on both servers. When a user changes their password on the initial server, the logon script runs, then asks them for the password to the second server. If they want to change their password to the second server they have to go to a DOS prompt which will become a headache. If they do manage to successfully change their password to the second server, and it is not the same password as they used for the first server, it asks them each time the logon script runs. Is there a way to synchronize the passwords, so they change it on the first server and it updates the second server?
Any help is appreciated.
------------------
Christo Lee.
evillage
November 23rd, 2000, 06:40 AM
Originally posted by Christo:
I have two separate NT 4 servers both in the same domain. Users log onto 1 server, which runs a logon script (DOS batch) which enables mappings to another server. The users exist on both servers. When a user changes their password on the initial server, the logon script runs, then asks them for the password to the second server. If they want to change their password to the second server they have to go to a DOS prompt which will become a headache. If they do manage to successfully change their password to the second server, and it is not the same password as they used for the first server, it asks them each time the logon script runs. Is there a way to synchronize the passwords, so they change it on the first server and it updates the second server?
Any help is appreciated.
Since you state you are in a Domain environment there is no need to have local user accounts on the second server. Use the user's domain accounts to control access to the resources on the servers. The standard method recommended for this is to create a local group on the server with the resource. Create a global group on the Domain Controller. Populate the global group with domain users who need access to the resource. Place the global group in the local group. Use the local group in the permissions to the share and NTFS permissions. This allows you to centralize administration, controlling individual user's access to the resource by adding or deleting their accounts from the global group.
Herb Cumbie MCSE, MVP
Network Analyst
CENCOR CSS LAN Support
evillage@knology.net