Hi all,
I've inherited an application that is used to change (sync) passwords on four different Windows servers (one 2003, others 2000). There is NO domain. The app reads the current users name, prompts for old and new password, then connects to the remote server and uses the NetUserChangePassword function from netapi32.dll to make the change.
After the 2003 server was 'hardened' by Corporate, the app no longer works for that server. Additionally, the target user account becomes locked out.
I've requested a list of changes made in the 'hardening' but was wondering if someone might have any ideas.
Thanks!
-Jeff
I've inherited an application that is used to change (sync) passwords on four different Windows servers (one 2003, others 2000). There is NO domain. The app reads the current users name, prompts for old and new password, then connects to the remote server and uses the NetUserChangePassword function from netapi32.dll to make the change.
After the 2003 server was 'hardened' by Corporate, the app no longer works for that server. Additionally, the target user account becomes locked out.
I've requested a list of changes made in the 'hardening' but was wondering if someone might have any ideas.
Thanks!
-Jeff
