We have Win2k SP2 workstations running in a NT 4 domain. We use a mandatory
user profile that configures a User DSN to allow an application to query a
SQL server. I needed to change the DSN information so that it now connects
to a different server. The new server is using a different port number,
(4951), for the connection. When I config the new User DSN, I enter the new
IP address for the server and in client configs, I deselect "dynamically
determine port" and enter the port number. I complete the config and test
connection, then logoff. After i change the profile to mandatory, and log
on as that user, I am unable to connect. If I then logon with my admin.
account, create the same User DSN, make connection and log-out, I can log
back in as a regular user and things work fine, seem to continue to work
fine eeven after a restart. Also, if I look at the client config area as
that user, the port infomation has defaulted back to "dynamically determine
port". I know that this is a port issue, I have looked at the firewall logs
and seen what port was being used when connections worked and didn't work.
I have tried different methods of changing the profile, I tried making the
user a member of local admin group when creating the profile, thinking that
there might be a registry permissions problem, which is where I still think
the problem lies, but once I switch the user back and make the profile
mandatory, I have the problem.. If I look at DSN setting when user is part
of admin group, the correct port number is still in the client config area.
Any ideas how I can get this to work correctly?