Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

telnet some_ip 1433

On Windows 7 this line doesn't work. It says it cannot establish connection. I'm 100% percent sure that the server has this port open. For a friend of mine this line works.

I suspect 2 reasons:

  • My ISP blocks this port.
  • My system blocks it.

I turned off the firewall and windows firewall. Is there anything else I can do to make sure the problem is not related to my system configuration?

BTW, I don't know if it's important, but

telnet some_ip 80

works fine


Wireshark log here

I replaced the ip I tried to telnet with

share|improve this question
If you have a second system at home (e.g. desktop and a laptop) then try it from the other system. If it works from the other then you know it is case 2. – Hennes Jan 12 '13 at 20:54

Using telnet is a very good and useful tool to trace/troubleshoot connectivity.

Here is what I do:

a) On the SQL Server box itself: telnet localhost 1433 -- This is to make sure a remote connection is even possible

b) On another box, on the same local net where the SQL server box lives: telnet 1433 -- This tells you if it is even possible to hit the port "off the box"

c) Now, if everything is working... it depends on what tools and access you have. Ex 1: Can the telnet be done from the firewall where the SQL Server lives? Ex 2: Can telnet be done from another non-local-to-SQL system that has to go through that firewall?

Often you can only get through 'b', and then you have to look at three things step by step:

  • Firewall where SQL Server lives
  • Firewall hardware on your side (where you run telnet)
  • Local OS firewall on the machine you are at running telnet (e.g. outbound filter or such blocking your outbound connection)
share|improve this answer

On the PC, run a traffic sniffer like Wireshark or Network Monitor and see what the network responses are when you try to open a telnet connection. That will tell you if outbound traffic on that port is being blackholed or otherwise tampered with.

It is highly unlikely that an ISP would be blocking port 1433 or application layer traffic that bares the marks of Telnet. Try another PC or device on the same LAN, like a smart phone, to narrow the possibilities down.

share|improve this answer
I added a Wireshark log to the question. Can you please help me interpret it? – gisek Jan 13 '13 at 2:21

just to be sure what does the following query returns

declare @dir nvarchar(4000)    

exec master.dbo.xp_instance_regread
    @dir output

select @dir

or, after editing your instance name

declare @dir nvarchar(4000)

exec master.dbo.xp_regread
    N'SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.SQL110EXP02\MSSQLServer\SuperSocketNetLib\Tcp\IPAll',
    @dir output

select @dir
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.