INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Remote connection issues cant Telnet to 1433

Remote connection issues cant Telnet to 1433

(OP)
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!

RE: Remote connection issues cant Telnet to 1433

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

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close