change user passwords

(0) Share

Report

Posted on by Jim Schimmels

I'm having an issue when a user forgets a password. We're using Window7 or XP with a 2008 R2 server running GP2010. The issue started about 6 months ago...

Here's the scenario:

When logged in as sa, I reset the user password to something simple like "password", then mark the box so that the user must change the password on the next login. Only problem is, the user still cannot change the password and is still not able to log in. I have to actually go the user's machine, log into GP as sa, then change the password, then change user so that the user can log in. Now everything works fine.

I get the same issue if I want to have a particular user (both a GP and a SQL user) attempt to log into SSMS. The user cannot do this until I actually go the user's machine and change the password there and then have the user log in after I change it.

So, why can I not change the user's passwords while I'm logged into the SQL server in GP as sa? Why do I have to get on the user's physical machine to change the password? Is this an admin issue with Windows 7 or what?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Ian Grieve 22,784 on at

Like (0)

Report

Hi Jim,

This sounds like the ODBC connection you have has a different Server defined than the user.

In the System DSN the Server must be exactly the same (including the case).

For example if your Server is defined as GPServer and the users as GPserver the password you set for them will not work.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Adding to Jim's response, you must provide Server IP address instead of server name in order to avoid such issues. Such problems happen if server have two LAN cards installed and working i.e., the users are distributed in two IPS's.

Was this reply helpful? Yes No
Ian Grieve 22,784 on at

Like (0)

Report

Using the Server IP is not necessary. Using the server name, or a CNAME alias, is fine as long as you use the same entry, in the same case, on all clients.

Was this reply helpful? Yes No
Suggested answer

Frank Hamelly | MVP... 46,623 Super User 2025 Season 2 on at

Like (0)

Report

I concur with Ian. And the reason the server name must be EXACT is because GP uses the server name in encryption of the user's password. All client ODBC's must use the same server name during setup or you will run into login issues at some point.

Was this reply helpful? Yes No
Jonathan Fear on at

Like (0)

Report

Hey All,

GP actually doesnt use the name you give the ODBC connection but rather the name of the SQL instance. Which I believe Ian was referring to but I just wanted to make that clear.

Was this reply helpful? Yes No