As I said in a previous post, I am in the process of securizing a
group of sqlservers.
After finishing a SQLServer installation, I noticed that UDP port 1434
was listening on the machine. I did some researches about that port
and it seems it is used to map TCP ports to instance names. This port
would then act similarely to the RCP Portmapper.
I dont want this port to be openened since my unique db client is an
asp server and that this asp server always "know" the tcp port (the
port is hardcoded within the asp code).
So my questions are:
1. Did I correctly understand the usage of UPD 1434?
2. How can I shut it down?
3. If it cannot be shut down (that would not surprised me), how can I
change it?
thank you
BTG"Before The Gods" <before.the.gods@.gmail.com> wrote in message
news:c1e81694.0408240459.3d4cf54d@.posting.google.com...
> As I said in a previous post, I am in the process of securizing a
> group of sqlservers.
> After finishing a SQLServer installation, I noticed that UDP port 1434
> was listening on the machine. I did some researches about that port
> and it seems it is used to map TCP ports to instance names. This port
> would then act similarely to the RCP Portmapper.
> I dont want this port to be openened since my unique db client is an
> asp server and that this asp server always "know" the tcp port (the
> port is hardcoded within the asp code).
> So my questions are:
> 1. Did I correctly understand the usage of UPD 1434?
> 2. How can I shut it down?
> 3. If it cannot be shut down (that would not surprised me), how can I
> change it?
I believe the following article addresses your questions and explains how to
change the default setting:
How to use static and dynamic port allocation in SQL Server 2000
http://support.microsoft.com/defaul...kb;en-us;823938
Steve
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment