up vote 0 down vote favorite
share [g+] share [fb]

Am trying to set up an ODBC connection between a Windows 2003 server and a remote MS SQL 2005 server. We have already done this with multiple customers successfully, but we've encountered a "Connection Failed" error at a specific customer site. Given that some customers work, we are certain that the SQL 2005 box we are connecting to is accepting remote connection via TCP/IP.

I ran a utility to test ports called Port Test, and confirmed that port 1433 is able to reach my SQL server host. We suspect that this maybe a firewall issue on our client side (not at the SQL host).

Am not sure what to ask my customer for, or if there's something else we need to do to unblock this error?

enter image description here

link|improve this question
Where did you run the Port Test from? – joeqwerty Oct 10 '11 at 12:10
Port Test was run on the client machine. – Kendor Oct 10 '11 at 13:29
If you ran Port Test on the client and it was able to connect to port 1433 on your SQL server, then it's not a firewall issue. How are you connecting from the client to the server, via FQDN or ip address? – joeqwerty Oct 10 '11 at 14:31
If you can telnet to port 1433 from the client and get the blank screen then the port is open. If you're using a named instance you may also have to open up 1434 UDP for the SQL Browser connectivity, but if it's a default instance then this should not be required. What's the connection string you are using? – Jason Cumberland Oct 10 '11 at 15:29
@joeqwerty am connecting via FQDN – Kendor Oct 10 '11 at 17:55
show 1 more comment
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.