<div>
Are you using named pipes?<br />
<br />
If not then go into the the second page of the ODBC call and click on the Client configuration button.<br />
<br />
Then select TCP/IP and configure from there.<br />
<a href="https://filedb.experts-exchange.com/incoming/2008/10_w40/65027/ODBC-Page2.jpg" target="_blank" class="file-inline" title="ODBC Page2 (32 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>ODBC-Page2.jpg</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2008/10_w40/65028/ODBC-Client-Configuration.jpg" target="_blank" class="file-inline" title="ODBC Client Configuration (19 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>ODBC-Client-Configuration.jpg</a>
</div>


Are you using named pipes?

If not then go into the the second page of the ODBC call and click on the Client configuration button.

Then select TCP/IP and configure from there.
ODBC-Page2.jpg [https://filedb.experts-exchange.com/incoming/2008/10_w40/65027/ODBC-Page2.jpg]
ODBC-Client-Configuration.jpg [https://filedb.experts-exchange.com/incoming/2008/10_w40/65028/ODBC-Client-Configuration.jpg]

ODBC-Page2.jpg

ODBC-Client-Configuration.jpg

<div>
We are not using a DSN to access the SQL Server. We use ADO to connect to SQL server specifying a connection string.
</div>


We are not using a DSN to access the SQL Server. We use ADO to connect to SQL server specifying a connection string.

<div>
Can we see the connect string?
</div>


<div>
ADO Connection String: driver={Sql Server}; server=dsi;database=agh; uid=dsi; password=pwd;<br />
<br />
We tried adding Network=dbmssocn to the end but to no avail.<br />
I am thinking it is SQL Server driver related. 
</div>


ADO Connection String: driver={Sql Server}; server=dsi;database=agh; uid=dsi; password=pwd;

We tried adding Network=dbmssocn to the end but to no avail.
I am thinking it is SQL Server driver related.

<div>
From a command prompt fire the cliconfg (Client Network Utility) and see what protocols are neabled and in what order. 
</div>


From a command prompt fire the cliconfg (Client Network Utility) and see what protocols are neabled and in what order.

<div>
<div class="content wysiwyg-content">
We have an Access 2003 database that connects to SQL Server 2005 via ADO 2.5 fine on all the machines but one. When we try to open the ADO connection in VBA, an error occurs: ....<br />
[microsoft][odbc sql server driver][dbnmpntw] Connection broken<br />
Error number is -2147467259<br />
<br />
This is a little odd and I can't find the reason for this disconnect. Suggestions?
</div>
</div>


We have an Access 2003 database that connects to SQL Server 2005 via ADO 2.5 fine on all the machines but one. When we try to open the ADO connection in VBA, an error occurs: ....
[microsoft][odbc sql server driver][dbnmpntw] Connection broken
Error number is -2147467259

This is a little odd and I can't find the reason for this disconnect. Suggestions?

Error trying to connect MS Access 2003 to SQL Server 2005

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.

Microsoft Access

VBScript (Visual Basic Scripting Edition) is an interpreted scripting language developed by Microsoft that is modeled on Visual Basic, but with some important differences. VBScript is commonly used for automating administrative and other tasks in Windows operating systems (by means of the Windows Script Host) and for server-side scripting in ASP web applications. It is also used for client-side scripting in Internet Explorer, specifically in intranet web applications.