Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote connection issues cant Telnet to 1433

Status
Not open for further replies.

grippy

Programmer
Dec 2, 2004
161
US
Hello,

I have SQL Server 2012 and I can not for the life of me to get this to remotely connect via ODBC or other. I have disabled the firewall, enabled the TCP and Named Pipes in the SQL Server Manager as well as enabling the Remote Connection check box in SSMS. I made sure the SQL Server authentication credentials work locally to login. I just cant get telnet to respond to port 1433? I have all the newest ODBC drivers and all windows updates on both client and server. I have run out of ideas of what else to check? Please someone help me.

Thank you!
 
Port 1433 is the standard SQL Server port, but it may not be the port your server is configured for. To determine the port...

1. Click Start -> Programs -> Microsoft SQL Server 2012 -> Configuration Tool -> SQL Server Configuration Manager.

2. In the configuration manager, expand "SQL Server Network Configuration"
Click on "Protocols for xxxxxxx".

3. On the right side, you will see a list of protocols. Make sure TCP/IP is enabled. If it's not, enable it.

4. Now, right click on TCP/IP and click properties.
Click on the IP Addresses tab
Scroll down to the IPAll section

5. The port number that SQL Server is configured to use will be displayed in the "TCP Dynamic Ports" section.

If TCP/IP was not enabled, you will need to enable it and then restart the SQL Server service before you can see the port number that SQL Server will use.

There is a "trick" I use when testing connectivity.

1. Create a new text document on the desktop.
2. rename it to "test.udl"
3. double click it.
4. Click on the provider tab and select "Microsoft OLE DB Provider for SQL Server".
5. Click Next
6. Select your database
7. Enter logon information.
8. Select the database.
9. click "Test Connection"

If your connection succeeds, you can close the data link properties window. You can then rename the "Test.udl" file to test.txt and open it with notepad. This will show you the connection string.

-George
Microsoft SQL Server MVP
My Blogs
SQLCop
twitter
"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top