System DSN reverts to dynamic port for non-admin

Posted on 2009-02-23
Last Modified: 2012-05-06
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?
Question by:Quark-E
    LVL 57

    Expert Comment

    by:Raja Jegan R
    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.

    Author Comment

    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.

    Accepted Solution

    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.

    Featured Post

    Top 6 Sources for Identifying Threat Actor TTPs

    Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

    Join & Write a Comment

    Having an SQL database can be a big investment for a small company. Hardware, setup and of course, the price of software all add up to a big bill that some companies may not be able to absorb.  Luckily, there is a free version SQL Express, but does …
    The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
    This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
    Viewers will learn how the fundamental information of how to create a table.

    732 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    17 Experts available now in Live!

    Get 1:1 Help Now