For more information on static and dynamic ports, see:
823938 How to use static and dynamic port allocation in SQL Server 2000
http://support.microsoft.com/?id=823938

Also, I want to explicitly answer the question about whether you can change
the UDP 1434 port to something else - the answer is no. However, if all
instances of SQL Server and MSDE in your network are patched to SP3 or
higher then you are not vulnerble to Slammer.

Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

We have also blocked UDP 1434 and have to set up aliases on all the client
workstations for named instances. I would like to address the comment

"However, if all
[quoted text, click to view]
"

That is a little like saying if all the other kids in the world are
innoculated against diseases, you don't need to get your kid innoculated.
This is an insidious worm that can take down a network. We have seen home
users VPN'ed to our network cause massive data storms. Unpatched MSDE's go
up all the time since MSDE comes included w/ so many applications. Anyone
who does not block UDP 1434 at the switch level for every network that they
consider important is being extremely delinquent IMHO. This is clearly a
case of an incredibly useful feature (named Instances) being damanged
long-term by after the fact, security management.


[quoted text, click to view]