Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 9243
  • Last Modified:

SQL Server Express 2005, TELNET, and Port 1433

I was configuring a client yesterday for a SQL Server 2005 Express DB.  Before building the ODBC connect string, I ran ping <IP Address>; the server replied.  I then ran TELNET <IP Adress> 1433 (1433 being the SQL over TCP port number).  I received the following response: "Connecting To <IP Address>...Could not open connection to the host, on port 1433:"  Here's the weird part, I tried the ODBC connect string, and it worked.  I double-checked, the host name specified in the ODBC connect string does match the IP address.  Up until yesterday, I'd assumed that port 1433 had to be open on the SQL server for a client / server connection to be successful.  Am I wrong.  Or, is my understanding of TELNET as a "port pinger" flawed.  
0
jdana
Asked:
jdana
  • 6
  • 5
1 Solution
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
port 1433 is the default, but your sql instance installed might have been configured to use another port...
0
 
jdanaAuthor Commented:
I installed the instance of SQL Server 2005 on the server.  I used the default install settings.
0
 
osiaraCommented:
Do you have enabled TCP/IP Protocol ??
(SQL Server Configuration Manager -> Network configuration)
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
jdanaAuthor Commented:
Yeah, recall that that the ODBC connect string DOES work.  I have full access to the SQL Server from the client machine.  The only thing I can't do from the client machine is TELNET the server on port 1433.  
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
the question of osiara was to clarify if the TCP/IP protocol is enabled.
if it's not, you can still connect via named pipes protocol, for example, which would explain why the telnet does not work.
0
 
jdanaAuthor Commented:
Angel III,

Good point.  Shared Memory and TCP/IP are enabled.  Named pipes and VIA are not.  
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
huh, spooooky :)

maybe your local firewall blocked your telnet application as such ?
0
 
jdanaAuthor Commented:
I wish that was it.  Windows Firewall is off.  There are no other firewall apps on the machine.  
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
can you show the sql network utility, to see the configuration of the tcp/ip protocol?
0
 
jdanaAuthor Commented:
The SQL Server Configuration Manager?  Surface Area Configuration?  Something else?
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
0
 
jdanaAuthor Commented:
angelIII,

Sorry for the slow response.  I appreciate the follow through.

J
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now