to force TCPIP, you can include the port number in the connection string
e.g.
Data Source=ipaddress,port
Some examples at:
http://www.connectionstrin
also see more here:
http://www.connectionstrin
Main Topics
Browse All TopicsI'm very green to SQL so please excuse my ignorance...
A contractor setup a SQL server this past weekend and converted our access database to a SQL back end. All is well in house, but a remote office is having a heck of a time connecting. I've determined that it's an issue making a named pipe connection. I've used the makepipe.exe and readpipe.exe utilities to test this. Some client machines are smart enough to start using the TCP/IP connection instead, but most just provide an error:
Connection failed:
SQLState: '01000'
SQL Server Error: 1326
[Microsoft][ODBC SQL Server Drive][Named Pipes]ConnectionOpen (CreateFile()).
Connection failed:
SQLState: '08001'
SQL Server Error: 1326
[Microsoft][ODBC SQL Server Driver] Client unable to establish connection
Makepipe and Readpipe also return error 1326. When a client succesfully makes a connection, I see no PIPE connections on the server for that user, just TCP/IP. I've tested the makepipe and readpipe on a client that can access the database, and the same error is returned. With all this in mind, I believe that the user is making a TCP/IP connection isntead of a named pipe connection to the SQL server.
Problematic clients can ping the SQL server by name, as well as telnet to port 1433 on the SQL server. MDAC version on all clients is 2.8, as well as the server. The ODBC connection is made in the front end, rather than making through the Data Connections All clients Win XP SP2. The only thing I haven't tried is repairing the MDAC....which will happen tomorrow.
There IS a firewall between the remote offices, ipfw rules to be exact. All IP traffic is permitted to and from the SQL server to the remote office. I suspect that this cannot handle the named pipe connections, but am not 100% sure. Unfortunatley there's nothing I can do about this.
My question is how can I force the users to connect via TCP/IP instead of named pipes? Should the named pipes connection be working through a firewall using ipfw which allows all IP traffic through? I would imagine it would be encapsulated....like SMB traffic since they're so closley related.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
to force TCPIP, you can include the port number in the connection string
e.g.
Data Source=ipaddress,port
Some examples at:
http://www.connectionstrin
also see more here:
http://www.connectionstrin
Hi Megs28
You need to use the SQL Client Network Utility on the workstations so that they use TCP/IP in preference to named pipes.
You can find this on the SQL Server installation CD - you need the Client Tools installation option.
You can use this utility to define the order of preference for different communication methods. Unfortunately I don't have a PC to hand, so I can't remember exactly which tab you need. One of them will give you up and down arrows that allows you to select the order in which the libraries will be used.
You can also define specific server aliases here where you can manually specify the way that the clients connect.
Does that help?
Steve
Sorry, forgot to post the link :http://www.tritac.nl/defa
This shows you how to set up a server alias in the client network utility
Business Accounts
Answer for Membership
by: megs28Posted on 2007-07-04 at 14:58:06ID: 19420790
Forgot to mention...
SQL Server - 2000 SP4 running on Windows 2003 Ent. SP1