"Zakiuddin Mohammed" wrote:

> I am not sure on SQL 2005 but in SQL 2000 you need to start the service
> again to take the effect of new port numbers...
> Zaki.
>
> "FredG" <FredG@discussions.microsoft.com> wrote in message
> news:6A9E45E1-E591-4086-B8A3-A5A1556BFFDC@microsoft.com...
> > SQL 2005 AS installed on a Cluster.
> >
> > We are using a named instance and only one currently exists. MS White
> paper
> > reads: The default instance listens on port 2383, while named instances
> are
> > dynamically allocated. This behavior can be changed by explicitly
> assigning a
> > port to either the default or named instance of SSAS. If the value for
> Port
> > is 0, the default behavior described above is achieved. Otherwise, the
> value
> > is treated as an absolute (static) port number to use for the specified
> > instance.
> >
> > I have modifed the Server PORT property, on the named instance (a default
> > instance does not exist) to listen on port 2382 and have added a rule to
> our
> > firewall to allow this traffic. However, AS continues to listen on port
> 2383.
> > Does anyone have any experience on this and how to change it.
> >
> > Is there a range of ports I can tell our network team to open?
>
>