4 replies
by mark neller
Use SETPASS to change the passwords.
Setpass.exe checks to see what type of client it is running on, and sets the
corresponding password. It checks for the SMB client first. If both an SMB and
NCP redirector are loaded, Setpass.exe will detect the SMB redirector, and only
change the password on the SMB network. If this should occur, run Setpass.exe with the -N switch. Doing this forces
Setpass.exe to change the password on the NCP network. You can also use the -S
switch to force Setpass.exe to change the password on the SMB network.
by shepherr
by wayne.maples
taken from a migration document http://www.microsoft.com/TechNet/Analpln/Cs/MIGRAT.asp
FPNW provides CHGPASS, a utility that allows users to change their password from a command line and replaces NetWare's SETPASS command. CHGPASS changes user passwords in the domain and in the FPNW accounts database, but many users were accustomed to logging on to other NetWare servers using local copies of the SETPASS utility. If users continued to use SETPASS, their Windows NT domain password would staythe same but the password would change on all servers they were attached to and on FPNW. Since all users were logging in exclusively through the FPNW service (which SETPASS was correctly changing the password to) the problem did not present itself until MIS converted users to log into the Windows NT domain.
At that point, domain passwords got out-of-synch with the FPNW passwords and MIS had to reset the domain password when each user was converted. Educating users on how to change their
by shepherr
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending