PMH4514
asked on
SQL Server / Telnet Can't connect to port 1433
I can't telnet into port 1433 going from A to B, but I can from B to A...
I have an XP Pro SP3 box and a Win2003 Server, each running MS SQL Server 2005, the XP Pro box running Express, the 2003 Server running the full edition.
Anyway, they are both on the same network.
Win2003 - 10.10.1.86
XP Pro - 10.10.1.65
From 86 if I try to 'telnet 10.10.1.65 1433' and it fails "could not open the connection to the host, on port 1433: Connect Failed"
From 65, I can telnet into port 1433 on 86 without problem.
I have attached to a code snippet, the output of netstat -an | find "1433" for both sides.
The SQL Server instance IS running on 10.10.1.65, surface area configuration manager is setup to allow remote connections, TCP/IP and Named Pipes.
I turned off the firewall for testing, on the XP box but it made no difference, I suspect because on XP for some reason 1433 is not listening.
Any idea how I can fix this?
I have an XP Pro SP3 box and a Win2003 Server, each running MS SQL Server 2005, the XP Pro box running Express, the 2003 Server running the full edition.
Anyway, they are both on the same network.
Win2003 - 10.10.1.86
XP Pro - 10.10.1.65
From 86 if I try to 'telnet 10.10.1.65 1433' and it fails "could not open the connection to the host, on port 1433: Connect Failed"
From 65, I can telnet into port 1433 on 86 without problem.
I have attached to a code snippet, the output of netstat -an | find "1433" for both sides.
The SQL Server instance IS running on 10.10.1.65, surface area configuration manager is setup to allow remote connections, TCP/IP and Named Pipes.
I turned off the firewall for testing, on the XP box but it made no difference, I suspect because on XP for some reason 1433 is not listening.
Any idea how I can fix this?
--------- ON THE XP BOX THAT I CANNOT CONNECT TO ------
C:\>netstat -an | find "1433"
TCP 10.10.1.65:3619 10.10.1.86:1433 TIME_WAIT
TCP 10.10.1.65:3669 10.10.1.65:1433 SYN_SENT
--------- ON THE 2003 SERVER THAT I CAN CONNECT TO ------
C:\>telnet 10.10.1.65 1433
Connecting To 10.10.1.65...Could not open connection to the host, on port 1433:
Connect failed
C:\>netstat -an | find "1433"
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
TCP 10.10.1.86:1433 10.10.1.86:2485 ESTABLISHED
TCP 10.10.1.86:2485 10.10.1.86:1433 ESTABLISHED
C:\>
ASKER
Hi, as I said "I turned off the firewall for testing, on the XP box but it made no difference"
Thanks for commenting though. Any other possibilities?
Thanks for commenting though. Any other possibilities?
Thanks for the update. On the XP machine what is result of the below command?
C:\>telnet localhost 1433
It should show some banner.
C:\>telnet localhost 1433
It should show some banner.
ASKER
On the XP machine, that command shows this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>telnet localhost 1433
Connecting To localhost...Could not open connection to the host, on port 1433: Connect failed
C:\>
----------------
It appears 1433 is not "listening" but why?
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>telnet localhost 1433
Connecting To localhost...Could not open connection to the host, on port 1433: Connect failed
C:\>
----------------
It appears 1433 is not "listening" but why?
Thanks for the update. Eliminate the network issues. Your port 1433 is not opened even locally.Check if port 1864 is open?
C:\>telnet localhost 1864
C:\>telnet localhost 1864
ASKER
same exact output as my last post, only on port 1864.. Again, personal firewall is off, but I did go in and turn it on and ensured 1433, 1434 (and now) 1864 were added to the exceptions list, saved and rebooted, and still see the same results. so I turned firewall off again, and rebooted.
Just googled and found that a similar problem to another user. He did the below;
"I had to run a security checker, provided by MS called SQLCritUpdPkg_ENU.exe http://www.microsoft.com/downloads [...] laylang=en
for Windows XP to allow SQL Server to open the ports. "
"I had to run a security checker, provided by MS called SQLCritUpdPkg_ENU.exe http://www.microsoft.com/downloads [...] laylang=en
for Windows XP to allow SQL Server to open the ports. "
ASKER
actually I already ran that SQLCritUpdPkg_ENU.exe last week
incidentally - when I ran it, it informed me that my installation does not need it. It is looking for SQL Server 2000 or desktop engine. I am running 2005 Express
incidentally - when I ran it, it informed me that my installation does not need it. It is looking for SQL Server 2000 or desktop engine. I am running 2005 Express
Hi, did you ever get this resolved? I'm having the same issue but on Win 2008 64bit with MS SQL 2005 Enterprise.
Thank you,
Mike
Thank you,
Mike
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
PMH,
That saved me a lot of trouble. Thanks
That saved me a lot of trouble. Thanks
ASKER
good to hear. You're welcome.
Thank you, I spent 4 days on this problem. So much thanks
"I did actually. Under control panel->computer management ->Services and Applications->SQL Server Configuration Manager->SQL Server 2005 Network Configuration->Protocols for SQL Express.. Under TCP/IP window, IP Addresses tab, I had to make sure that 1433 was specified as the TCP port in all 3 sub-windows of the dialog (IP1, IP2, IP All). IP1 and IP2 specified 0 as TCP Dynamic ports, and 1433 fixed to TCP Port.
That solved my issue at least, hope it helps you!"
-worked for me
That solved my issue at least, hope it helps you!"
-worked for me
On your XP Pro box, check if the Windows Personal Firewall is 'ON'. Try again by turning it 'OFF'