sql server not accepting TCP/IP connections on port 1434?

Question

hi,

im using sql server 2000, the port of sql server is set to 1434.

So i go to command prompt in windows and execute: telnet localhost 1434, but i got message:

"Connecting To localhost...Could not open connection to the host, on port 1434: Connect failed"

so im gessing sql server is not accepting TCP/IP connections on port 1434.

what can i do, so that sql server accept connections on that port?

thanks...

Answer 1

i also did netstat -b in command prompt, and i dont see sql server there, and i dont see an application using that port.

what shall i do?

Answer 2

Try following the connection troubleshooting guide on the SQL Protocols blog: http://blogs.msdn.com/b/sql_protocols/archive/2008/04/30/steps-to-troubleshoot-connectivity-issues.aspx

Answer 3

Try following the connection troubleshooting guide on the SQL Protocols blog: http://blogs.msdn.com/b/sql_protocols/archive/2008/04/30/steps-to-troubleshoot-connectivity-issues.aspx

in this link, im on step 2. When i went to errorlog, i see:

"SQL server listening on Shared Memory, Named Pipes."

So, im guessing TCP/IP protocol must be in that list, but is not.

i went to start menu--microsoft sql server--Server network utility, and in enabled protocols i see: Named Pipes and TCP/IP.

so i dont undertand why on errorlog i dont see TCP/IP.

what's going on here and how do i solve it?

Answer 4

Try following the connection troubleshooting guide on the SQL Protocols blog: http://blogs.msdn.com/b/sql_protocols/archive/2008/04/30/steps-to-troubleshoot-connectivity-issues.aspx

in this link, im on step 2. When i went to errorlog, i see:

"SQL server listening on Shared Memory, Named Pipes."

So, im guessing TCP/IP protocol must be in that list, but is not.

i went to start menu--microsoft sql server--Server network utility, and in enabled protocols i see: Named Pipes and TCP/IP.

so i dont undertand why on errorlog i dont see TCP/IP.

what's going on here and how do i solve it?

any tip would be good, thanks

Answer 5

Have you restarted the SQL Server service since you enabled the TCP protocol?

---

This post is provided 'as is' and confers no express or implied warranties or rights.

Answer 6

Have you restarted the SQL Server service since you enabled the TCP protocol?

---

This post is provided 'as is' and confers no express or implied warranties or rights.

yes

Answer 7

i'm doing this project on one computer only.

In that computer, besides having sql server 2000, i also have installed sql server 2005 and 2008.

Having these 3 sql server installations could cause some kind of conflict?

Answer 8

i did netstat -nabo, and i got this:

 Proto Local Address     Foreign Address    State      PID
 TCP  0.0.0.0:80       0.0.0.0:0       LISTENING    2004
 [httpd.exe]
 
 TCP  0.0.0.0:135      0.0.0.0:0       LISTENING    1148
 e:\windows\system32\WS2_32.dll
 E:\WINDOWS\system32\RPCRT4.dll
 e:\windows\system32\rpcss.dll
 E:\WINDOWS\system32\svchost.exe
 E:\WINDOWS\system32\ADVAPI32.dll
 [svchost.exe]
 
 TCP  0.0.0.0:443      0.0.0.0:0       LISTENING    2004
 [httpd.exe]
 
 TCP  0.0.0.0:445      0.0.0.0:0       LISTENING    4
 [System]
 
 TCP  0.0.0.0:2869      0.0.0.0:0       LISTENING    1528
 E:\WINDOWS\system32\httpapi.dll
 e:\windows\system32\ssdpsrv.dll
 E:\WINDOWS\system32\RPCRT4.dll
 [svchost.exe]
 
 TCP  0.0.0.0:3306      0.0.0.0:0       LISTENING    2428
 [mysqld.exe]
 
 TCP  0.0.0.0:4400      0.0.0.0:0       LISTENING    2592
 [nlsvc.exe]
 
 TCP  0.0.0.0:7511      0.0.0.0:0       LISTENING    204
 [raysat_3dsmax2010_32server.exe]
 
 TCP  127.0.0.1:1028     0.0.0.0:0       LISTENING    3080
 [alg.exe]
 
 TCP  127.0.0.1:5152     0.0.0.0:0       LISTENING    188
 [jqs.exe]
 
 TCP  192.168.0.101:139   0.0.0.0:0       LISTENING    4
 [System]
 
 TCP  127.0.0.1:5152     127.0.0.1:1163     CLOSE_WAIT   188
 [jqs.exe]
 
 TCP  192.168.0.101:2869   192.168.0.1:4563    CLOSE_WAIT   4
 [System]
 
 UDP  0.0.0.0:500      *:*                  908
 [lsass.exe]
 
 UDP  0.0.0.0:445      *:*                  4
 [System]
 
 UDP  0.0.0.0:4500      *:*                  908
 [lsass.exe]
 
 UDP  0.0.0.0:1434      *:*                  3036
 [sqlbrowser.exe]
 
 UDP  127.0.0.1:123     *:*                  1284
 e:\windows\system32\WS2_32.dll
 e:\windows\system32\w32time.dll
 ntdll.dll
 E:\WINDOWS\system32\kernel32.dll
 [svchost.exe]
 
 UDP  127.0.0.1:1135     *:*                  3508
 [iexplore.exe]
 
 UDP  127.0.0.1:1040     *:*                  1284
 e:\windows\system32\WS2_32.dll
 E:\WINDOWS\system32\WINHTTP.dll
 E:\WINDOWS\system32\upnp.dll
 E:\WINDOWS\system32\RPCRT4.dll
 E:\WINDOWS\system32\ole32.dll
 [svchost.exe]
 
 UDP  127.0.0.1:44301    *:*                  2880
 [PnkBstrA.exe]
 
 UDP  127.0.0.1:1900     *:*                  1528
 e:\windows\system32\WS2_32.dll
 e:\windows\system32\ssdpsrv.dll
 E:\WINDOWS\system32\ADVAPI32.dll
 E:\WINDOWS\system32\kernel32.dll
 [svchost.exe]
 
 UDP  192.168.0.101:1900   *:*                  1528
 e:\windows\system32\WS2_32.dll
 e:\windows\system32\ssdpsrv.dll
 E:\WINDOWS\system32\ADVAPI32.dll
 E:\WINDOWS\system32\kernel32.dll
 [svchost.exe]
 
 UDP  192.168.0.101:137   *:*                  4
 [System]
 
 UDP  192.168.0.101:123   *:*                  1284
 e:\windows\system32\WS2_32.dll
 e:\windows\system32\w32time.dll
 ntdll.dll
 -- unknown component(s) --
 [svchost.exe]
 
 UDP  192.168.0.101:138   *:*                  4
 [System]

Answer 9

When running SQL Server 2000 along with SQL Server 2005 or SQL Server 2008, the SQL Server 2000 must be running Service Pack 3 or 4. Otherwise the SQL Server Browser service (of SQL Server 2005 or SQL Server 2008) will grab UDP port 1434 and will interfer with the old SQL Server 2000 port resolution system. SQL Server SP3 added the ability for SQL Server 2000 to play nice with the SQL Server Browser service. The service pack of SQL Server 2005 and SQL Server 2008 shouldn't matter. Here is a list of the SP version numbers that someone put together http://www.sql-server-performance.com/tips/service_packs_p1.aspx Here is SQL Server 2000 SP4 http://www.microsoft.com/downloads/en/details.aspx?familyid=D5BB816A-6E1A-47CB-92BE-51C565EE184C&displaylang=en

---

Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

Answer 10

When running SQL Server 2000 along with SQL Server 2005 or SQL Server 2008, the SQL Server 2000 must be running Service Pack 3 or 4. Otherwise the SQL Server Browser service (of SQL Server 2005 or SQL Server 2008) will grab UDP port 1434 and will interfer with the old SQL Server 2000 port resolution system. SQL Server SP3 added the ability for SQL Server 2000 to play nice with the SQL Server Browser service. The service pack of SQL Server 2005 and SQL Server 2008 shouldn't matter. Here is a list of the SP version numbers that someone put together http://www.sql-server-performance.com/tips/service_packs_p1.aspx Here is SQL Server 2000 SP4 http://www.microsoft.com/downloads/en/details.aspx?familyid=D5BB816A-6E1A-47CB-92BE-51C565EE184C&displaylang=en

---

Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

thanks,

i went to the first link, and verified this is the sql 2000 version im using:

* 2000.8.00.194.0 SQL Server 2000 "gold" release, no SP

i went to the second link, and downloaded the SP4, but when trying to install i got this message:

The product instance MSSQLServer has had update 194 applied. You cannot install GDR update 2055 overtop update 194. An update of build equal to or greater than 2280 should be downloaded.

The product instance SQLTools has had update 194 applied. You cannot install GDR update 2055 overtop update 194. An update of build equal to or greater than 2280 should be downloaded.

so,

can i really update my sql version to SP4?

or this means that my sql has already the SP4?

Answer 11

When running SQL Server 2000 along with SQL Server 2005 or SQL Server 2008, the SQL Server 2000 must be running Service Pack 3 or 4. Otherwise the SQL Server Browser service (of SQL Server 2005 or SQL Server 2008) will grab UDP port 1434 and will interfer with the old SQL Server 2000 port resolution system. SQL Server SP3 added the ability for SQL Server 2000 to play nice with the SQL Server Browser service. The service pack of SQL Server 2005 and SQL Server 2008 shouldn't matter. Here is a list of the SP version numbers that someone put together http://www.sql-server-performance.com/tips/service_packs_p1.aspx Here is SQL Server 2000 SP4 http://www.microsoft.com/downloads/en/details.aspx?familyid=D5BB816A-6E1A-47CB-92BE-51C565EE184C&displaylang=en

---

Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

thanks,

i went to the first link, and verified this is the sql 2000 version im using:

* 2000.8.00.194.0 SQL Server 2000 "gold" release, no SP

i went to the second link, and downloaded the SP4, but when trying to install i got this message:

The product instance MSSQLServer has had update 194 applied. You cannot install GDR update 2055 overtop update 194. An update of build equal to or greater than 2280 should be downloaded.

The product instance SQLTools has had update 194 applied. You cannot install GDR update 2055 overtop update 194. An update of build equal to or greater than 2280 should be downloaded.

so,

can i really update my sql version to SP4?

or this means that my sql has already the SP4?

so, im guessing my sql 2000 version has already the SP4,

but still, the sqlbrowser.exe is not listening on the port.

what can i do?

Answer 12

You can test this. Stop the SQL Server Browser Service (which might block new access to SQL Server 2005 and 2008), and then restart the SQL Server 2000 instance. Can you connect now? I guess, yes. Because SQL Server 2000 can grab UDP port 1434 for named instance resolution. And if you then try to start the SQL Server Browser service I would expect it to fail, because it can't get UDP port 1434.

---

Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

Answer 13

You can test this. Stop the SQL Server Browser Service

when you say stop the SQL Server Browser Service, you mean ctrl+alt+supr in windows and stop it there?

and then restart the SQL Server 2000 instance.

---

you mean with SQL Server Service Manager(stop then start)?

Answer 14

there's one thing i dont have clear:

when doing netstat -nabo, i see processes:

sqlbrowser.exe and sqlservr.exe. Each one of them with a specific port asigned to them.

Which one of them should i telnet?

Answer 15

its sqlservr.exe. Im doing telnet on sqlservr.exe now, and its working fine, but is in a different port than 1433 or 1434.

 

thanks guys!!!