Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Sql Server broadcasts on port 1434
116 views
Skip to first unread message
rskohman
Jul 14, 2003, 2:57:11 PM7/14/03
to
Can anyone shed some light on what conditions make Sql
Server broadcast over port 1434? Security at my company
drives me nuts with emails complaining that this or that
server are broadcasting on 1434 and that this is not
allowed here. I try to tell them this is expected behavior
under certain circumstances but no one is listening. I
have read the BOL and surfed the net for more specific
info but haven't found any. Any help would be greatly
appreciated.
Server broadcast over port 1434? Security at my company
drives me nuts with emails complaining that this or that
server are broadcasting on 1434 and that this is not
allowed here. I try to tell them this is expected behavior
under certain circumstances but no one is listening. I
have read the BOL and surfed the net for more specific
info but haven't found any. Any help would be greatly
appreciated.
Vinodk
Jul 15, 2003, 9:08:52 AM7/15/03
to
Yes, This is an expected behaviour only. The UDP port 1434 also needs to be open to ensure that you can correctly access and browse named instances. Searching SQL Server Books Online for "1434" returns three valuable hits. To put it in a nutshell, SQL Server establishes a listener service on UDP port 1434 that lets a client query the server for a list of named instances and their network configuration information. This listener service always runs on UDP port 1434 and can't be configured to run on another port.
--
HTH,
Vinod Kumar
MCSE, DBA, MCAD
SCT Software Solutions
http://www32.brinkster.com/sqlvinod
"rskohman" <rsko...@hewitt.com> wrote in message news:08c401c34a39$bb9f0ca0$a001...@phx.gbl...
Dan Guzman
Jul 15, 2003, 9:38:02 AM7/15/03
to
To add to Vinod's response, excessive *outbound* activity from the SQL
Server on UDP 1434 is an indication of Slammer virus infection. This is
probably why your company's security department is concerned. You can
prevent such infection by installing SQL Server SP3a.
Server on UDP 1434 is an indication of Slammer virus infection. This is
probably why your company's security department is concerned. You can
prevent such infection by installing SQL Server SP3a.
--
Hope this helps.
Dan Guzman
SQL Server MVP
-----------------------
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
-----------------------
"rskohman" <rsko...@hewitt.com> wrote in message
news:08c401c34a39$bb9f0ca0$a001...@phx.gbl...
rskohman
Jul 15, 2003, 12:27:58 PM7/15/03
to
This is what I thought, but I needed to confirm it.
Thanks so much!
Thanks so much!
>.
>
0 new messages