Solved

Domain users cant see system DSN on Terminal Server

Posted on 2009-05-12
6
2,502 Views
Last Modified: 2013-11-21
Hi,
I have a Windows 2008 server configured as TS, and I lave made an system DSN to one of our programs. The problem is that it only works, when I am logged in as local administrator.
As soon as one of my domain users is loggin on, the program reports that it cant find the DSN name.
I'm sure its a permission issue, but I can't find the right solution... I tried adding the domain users to the local admin group without luck.
Anybody knows how to fix this ?
0
Comment
Question by:Syswatch6000
6 Comments
 
LVL 7

Expert Comment

by:vikasjus
ID: 24363457
I am not sure but check can DSN work with terminal server.
0
 
LVL 1

Expert Comment

by:itinfserv
ID: 25569437
Well this used to work in 2003 and now it doesn't in 2008; any one have a solution to this? It seems that only the user that created the system DSN can see it?
0
 

Accepted Solution

by:
Syswatch6000 earned 0 total points
ID: 25572140
I have made an export from the reg. And then I import it to every user through the login script.
0
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

 
LVL 1

Expert Comment

by:itinfserv
ID: 25578699
Could you clue me in on the reg key please?
0
 

Expert Comment

by:edward47150
ID: 26601995
You can find it under HKLU.  Do a search for your DSN name.

This post was very helpful.  I used this on a Windows Server 2008 R2 that was having this issue and it worked great.

Thanks!
0
 

Expert Comment

by:npdodge
ID: 38149427
What I found today is that the ODBC Data source connections in the Admin Tools points to c:\windows\system32\odbcad32.exe.  However, when a domain user is logged on, they're actually reading from c:\windows\syswow64\odbcad32.exe which contains completely separate DSNs.  So if you want them to be able to read a system DSN on a 2008 R2 server, you'll need to add these system DSNs as a local admin using c:\windows\syswow64\odbcad32.exe
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

1. Boot PC and press F10, select storage options and change the compatibility from “AHCI” to “IDE”, save and exit 2. Boot PC and press F12 3. Upon PXE display of searching for DHCP server, press Pause break to obtain MAC address 3. Open Configu…
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
Although Jacob Bernoulli (1654-1705) has been credited as the creator of "Binomial Distribution Table", Gottfried Leibniz (1646-1716) did his dissertation on the subject in 1666; Leibniz you may recall is the co-inventor of "Calculus" and beat Isaac…

820 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