Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a DSN on machine A that points to a DB on machine B. We have a machine C, that we want to be able to use that DSN on machine A...but we don't want to create the DSN on machine C.

Is there a way to use the System DSN on machine A from machine C?

share|improve this question
up vote 2 down vote accepted

A system DSN, by definition, is local to the computer it's configured on. You'll need to create it on the other server.

An alternative option is to use a DSN-less connect string, if possible.

share|improve this answer
Unfortunate. We're trying to avoid creating a DSN on that computer, and the connection string option is failing and we can't figure out why. (and the driver/db vendor is no help so far.) Thanks for the answer. – Beska Jun 23 '09 at 16:14
(Assuming I don't get an answer that contradicts this, or provides a great deal more detail, relatively soon, I'll mark this as accepted.) – Beska Jun 23 '09 at 16:18

No, the purpose of a DSN is a connection from one machine to one data source. It is not possible to the best of my knowledge to "proxy" a DSN connection from one machine to the other.

share|improve this answer

yes, you can... i know this answer don't bother you after several years of asking this question, but i think it might help other people looking out for it.

You can achieve this using DSN less approach

For Example : connection string for SQL server DSN

oConn.Open "Driver={SQL Server};" & _
           ";" & _
           ",1433;" & _
           "Network=DBMSSOCN;" & _
           "Database=myDatabaseName;" & _
           "Uid=myUsername;" & _

I have already tried it myself, however you need to have sufficient access rights

More DSN connection strings can be found Here

share|improve this answer

Yes, you can, but it requires a third-party solution such as that from my employer.

These solutions typically entail installing some components on the data consuming machine (C) and some components on the machine with the ODBC DSN (A). The connection winds up looking like

ODBC consumer on C
   -> ODBC Bridge DSN on C
       -> ODBC Bridge components on A
           -> ODBC DSN on A
               -> target DBMS on B
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.