System DSN reverts to dynamic port for non-admin

We have an XP Pro SP3 client machine that connects to a database on MS SQL Server 2000 SP2 on a non-standard port.  I migrated the database to a different server and need to update the System DSN.  Easy enough on most machines, but on this machine, for one non-administrator, it insists on reverting back to "Dynamically determine port," which of course tries to use 1433 instead of our port.  And this is a System DSN, not User.

We've searched through the registry and verified that there are no entries trying to use 1433.  If you have the non-admin log in and run ODBC Data Source Administrator with admin credentials, the settings are correct.

Run it as the non-admin user and it's back to dynamic.

We've completely deleted the DSN and added it back under a different name and the same thing occurs.  What am I missing?
Quark-EAsked:
Who is Participating?
 
Quark-EAuthor Commented:
Although I still don't know the exact cause, we determined that it was tied to a user profile.  Two other people who use the same workstation were able to make the database connection properly (inheriting the system DSN as they should).

We removed and re-created the user profile for the person who couldn't connect, and the system DSN was inherited and the connection made.
0
 
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
Check Network Protocols in Enterprise Manager for the Default ports from your login.
If that is set to the one configured earlier, then there shouldn't be any issues. If not configure it back and try again.
0
 
Quark-EAuthor Commented:
It's not the server side that has the problem.  It's indeed configured with our non-standard port.  Other client workstations can also access the database once we made the change to the new server name.

This particular workstation has an issue where it doesn't retain the System DSN port change (made as an Admin) for the non-admin user.

To get things working I temporarily made the user a local admin and the DSN settings were suddenly as I'd configured them.  Tomorrow I'll see what happens when I move the user back to Power Users.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.