Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mbosch
Starting Member
6 Posts |
 Posted - 2008-03-25 : 15:05:44
|
| I have been reading every resource available out there about getting this connection to work. Can someone help me diagnose what the problem is? As the client, what ports do I need to have open? I'm using ReliableSite.net web hosting and trying to connect to their sql server.I've also asked for help on their forum and opened a ticket to see if perhaps its listening on a different port, but they say its my issue.For reference:http://forum.reliablesite.net/index.php?topic=232.0 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-25 : 15:14:18
|
| Try connecting via IPAddress,PortNumber. They probably aren't using 1433 or 1434 for your named instance though, so you need to find out what port they are using. 1433 is typically for the default instance which according to your image isn't the case.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
mbosch
Starting Member
6 Posts |
Posted - 2008-03-25 : 15:20:10
|
| Hi Tara - I just finished reading one of your blog entries! I hope you can help me. One of the first things I tried doing was using telnet and it would not connect. The support person said it wouldn't connect because SQL does not allow it to connect like that regardless. This seemed odd to me. I also figured they would be using an unconventional port number but the person said it was probably my firewall. Is there anything I need to do from the client side? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-25 : 18:28:57
|
| The support person is correct in that we don't use telnet to connect to SQL Server. However what the support person apparently doesn't understand is that telnet is used to determine if we can connect to the server via a specified port. This is basic network troubleshooting and not SQL Server troubleshooting. We need to be able to connect to the server by the port that SQL Server is listening on and telnet allows us to test that.Until you know what port SQL Server is listening on, we can't help troubleshoot this issue. I'd highly recommend switching hosts if the support person is unable to provide such important information to you.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
mbosch
Starting Member
6 Posts |
Posted - 2008-03-25 : 18:53:19
|
| This might be off-topic as far as SQL is concerned, but before I approach the support person again, can you confim that there are no settings on my side (client) that would prevent me from telnet to see if the port is listening? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-25 : 20:28:36
|
| I'm not aware of anything, but perhaps something at your ISP.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
Error 26 - Connecting to a remote SQL 2005 Instanc