Note: I’ve obviously changed the server names and IPs to fictitious ones.
Here’s what’s going on. I’ve got a server, which I’m calling MYSERVER. running Microsoft SQL Server Express 2005. Right on this server itself, I’ve got an ODBC connection set up pointing at itself, and that already works perfectly. I log in using SQL Server Authentication (not Windows authentication), and it’s set up like this:
Like I said, that one works. But next, I’ve got another computer which is on a totally different domain/not on the intranet, that needs to access this same SQL Server hosted on MYSERVER. Because it’s on a different domain, it doesn’t recognize the name “MYSERVER”; I have to point it at the IP address of MYSERVER, which we’ll say is 123.456.789.012. But the ODBC connection doesn’t seem to work there. I tried setting it up like this:
This doesn’t work. When I put in the username and password and press Next, it stalls for a good 10 to 20 seconds, and then finally comes back with the following error:
If I try the same thing, but change the “server” from 123.456.789.012\SQLEXPRESS to just plain old 123.456.789.012. I get a different error:
Now I know what you’re thinking. You might be thinking, “duh, you probably didn’t open the firewall for port 1433, dummy.” Except I did, and I verified this, as I can successfully run:
from the command line all I want. So I’m not sure what to do. I know the SQL Server exists, works, and an ODBC connection can be set up properly; I’m just not sure what it is I’ve got wrong in my connection settings that’s throwing these errors. Based on the latter error I listed, it would seem that it can connect to the server, but simply cannot find the instance (since I didn’t specify one that time). So does that mean I just need to use some different syntax to specify the IP along with an instance name? What do I do? Thanks in advance.
asked Nov 6 ’09 at 0:22
I m accepting your answer because it got me on the right track. Under SQL Server Configuration Manager, TCP/IP was already enabled all along under SQL Server 2005 Network Configuration Protocols for SQLEXPRESS and SQL Native Client Configuration Client Protocols. Named Pipes was already enabled in the latter. I enabled it in the former, but that didn t seem to help (same error messages). Finally, I switched the ODBC source to use the SQL Native Client driver instead of the SQL Server driver, and that finally DID work. SoaperGEM Nov 9 ’09 at 14:08
Thank you SoaperGEM! I never would have thought to have tried SQL Native Client! Worked like a charm! Phillip Senn Nov 15 ’12 at 22:02
If you are running SQL Server 2005 by using an instance name and you are not using a specific TCP/IP port number in your connection string, you must enable the SQL Server Browser service to allow for remote connections. For example, SQL Server 2005 Express is installed with a default instance name of Computer Name\SQLEXPRESS.
I had this same issue and managed to resolve it by changing the SQL driver to the SQL Native Client driver too. This was weird as in my case this had been working fine for years and then just stopped working. I suspect this is something along the lines of the driver being corrupt, perhaps a reinstal of MDAC might assist, but for the time being I’m happy that it is working at all!
answered Feb 8 ’10 at 12:56
Just a wild shot here but what happens if you put a double backslash before the server name or IP address? It just seems to me that it’s normally required for most other Windows/Microsoft connections.
answered Nov 6 ’09 at 3:02
Trying the double backslash results in the same 1326 error (the first one I listed). SoaperGEM Nov 6 ’09 at 3:10
I had a similar issue. In my case another sw configures the ODBC setting so i cannot change the driver. I solved my case like this:
- Set TCP/IP settings for server to use the port 1433
- On the client enter the server address like: 192.168.1.5,1433 (no instance name)
Then it started to work. Client OS: Win7 x64 Driver: sqlsrv32.dll