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.
