Solved

Domain users cant see system DSN on Terminal Server

Posted on 2009-05-12
6
2,500 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
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 
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

Use Case: Protecting a Hybrid Cloud Infrastructure

Microsoft Azure is rapidly becoming the norm in dynamic IT environments. This document describes the challenges that organizations face when protecting data in a hybrid cloud IT environment and presents a use case to demonstrate how Acronis Backup protects all data.

Question has a verified solution.

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

Suggested Solutions

Every system administrator encounters once in while in a problem where the solution seems to be a needle in haystack.  My needle was an anti-virus version causing problems with my Exchange server. I have an HP DL350 with Windows Server 2008 Stand…
My previous article  (http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/A_4466-A-beginners-guide-to-installing-SCCM2007-on-Windows-2008-R2-Server.html)detailed one possible method to get SCCM 2007 installed an…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

770 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