Groups | Blog | Home
all groups > sql server connect > september 2005 >

sql server connect : SQL Server doesn't respond to broadcast request


Sylvain
9/13/2005 1:53:01 AM
Hi,

A problem since few weeks, all my SQL servers located on the LAN (clients
too) don't respond to the broadcast request (255.255.255.255:1434), so my
clients must set manually the TCP/IP port of their named instance. No
firewall are placed between servers and clients. Any help appreciated.

Regards
Sylvain
Matt Neerincx [MSFT]
9/29/2005 6:29:47 PM
SQL Server itself will always attempt to listen for these broadcasts.
So something else on your network system is blocking these broadcasts from
traveling around your network.

For example perhaps the network admin added a new firewall or turned on a
group policy blocking port 1434.

You can verify if SQL is listening for the broadcasts by running the
following on the SQL machine from command prompt:

E:\>netstat -aon

Active Connections

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 140
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1504
....

UDP 0.0.0.0:1434 *:* 4344

You should see an entry for UDP 0.0.0.0:1434 and the PID should be the same
PID as SQL Server service (in Task Manager).

--
Matt Neerincx [MSFT]

This posting is provided "AS IS", with no warranties, and confers no rights.

Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

[quoted text, click to view]

AddThis Social Bookmark Button