all groups > sql server msde > august 2006 >
You're in the

sql server msde

group:

Broadcast on UDP/1434



Broadcast on UDP/1434 Adrian Grigorof
8/31/2006 12:53:50 PM
sql server msde: I have the MSDE (SQL Server 8.0.760) installed by a 3-rd party application
on a W2K Professional with the latest updates and I can see in my firewall
logs that there is a broadcast on UDP/1434 every 8 seconds. I know that
UDP/1434 is used by the SQL management utilities. I captured the traffic and
from what I can see the server is advertising the database instance running
on that machine. It is hard to believe that this is "normal" so how can I
stop this type of traffic (it's filling my firewall logs).
--
Adrian


Re: Broadcast on UDP/1434 Andrea Montanari
9/1/2006 12:00:00 AM
hi Adrian,
[quoted text, click to view]

first (and OT), MSDE 8.0.760 build is service pack 3 or service pack 3a
(http://www.aspfaq.com/SQL2000Builds.asp), and there's plenty of later build
releases, as long as service pack 4 you can (and should install)... ask you
ISV for problems/requirements in order to install them/it.

the SQL Server Resolution Service which operates on UDP 1434 port is only
required for SQL Server/MSDE "named" instances with dynamic tpc/ip port
allocations.. if you are running a "default" instance or a named instance
with fixex port allocation the SQL Server Resolution Server should stop
broadcasting the relevant info over the lan... obviously, in the latter
case, you have to define an ALIAS (with Client Network Utility,
cliconfg.exe) on all remote clients in order to resolve the new fixed port
MSDE is listening on, or just provide the fixed port in the connection
string...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
--------- remove DMO to reply

Re: Broadcast on UDP/1434 Adrian Grigorof
9/1/2006 9:50:17 AM
Thank you for the reply. I was in fact wrong about the MSDE broadcasting on
UDP/1434... it was the ISA firewall that did that. ISA installs MSDE for
logging purposes and starts the SQL Server Service Manager without
connecting it to the local SQL instance so this service is broadcasting
looking for servers to connect to. The other computer running with MSDE was
answering to the broadcast but the ISA would record the answer as a
potential port scan :(. So I stopped the SQL Server Service Manager and the
problem is gone.

I will upgrade the MSDE anyway!

--
Adrian


[quoted text, click to view]

AddThis Social Bookmark Button