Advertisement

07.04.2007 at 02:57PM PDT, ID: 22675801
[x]
Attachment Details

SQL connection error - 1326

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
7.4
Zones:

Databases Miscellaneous, MS SQL Server

Tags:

1326, error, sql
I'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.
Start your 7 day free trial to see this answer
Answered By: Computer101
Expert Since: 04/07/2001
Accepted Solutions: 39510
Computer Expertise: Advanced
Computer101 has been an Expert for 7 years 9 months, during which he has posted 147805 comments and answered 39510 questions. Computer101 is just one of 1707 experts in the Databases Miscellaneous Zone. 3 experts collaborated on this answer, which was graded an "A" by the asker.
 
 
20081119-EE-VQP-48