Solved

Domain users cant see system DSN on Terminal Server

Posted on 2009-05-12
6
2,490 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
Complete Microsoft Windows PC® & Mac Backup

Backup and recovery solutions to protect all your PCs & Mac– on-premises or in remote locations. Acronis backs up entire PC or Mac with patented reliable disk imaging technology and you will be able to restore workstations to a new, dissimilar hardware in minutes.

 
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

Do email signature updates give you a headache?

Constantly trying to correctly format email signatures? Spending all of your time at every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

Join & Write a Comment

The environment that this is running in is SCCM 2007 R2 running on a Windows 2008 R2 server. The PXE Distribution point is running on its own Windows 2008 R2 box. This is what Event viewer showed after trying to start the WDS service:  An erro…
Have you considered what group policies are backwards and forwards compatible? Windows Active Directory servers and clients use group policy templates to deploy sets of policies within your domain. But, there is a catch to deploying policies. The…
This video discusses moving either the default database or any database to a new volume.
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

762 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

20 Experts available now in Live!

Get 1:1 Help Now