Re: Change SQL Port doesnt change

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Anthony
I cannot set the static port - it goes back to the dynamically set port when
I have changed it. The manual is BOL and Help file of SSCM. I have another
cluster where this is no problem so I wondered if there is a bug somewhere in
the software. I am using version 2153.

I want all my instances to use port 1433 since there are applications that
have hardcoded port 1433 as database port.

Regards
Rune

"Anthony Thomas" wrote:

By default, the Default instance is assigned TCP 1433, Named Instances use
Dynamic Ports; however, this same manual states that the best practice when
supporting connectivity through firewalls is to declare a static port
assignment, and then proceeds to note how to do this through the SSCM. So,
I am not sure which "manual" you are referring to.


Anthony Thomas


--

"ipconfig2" <ipconfig2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4778F614-5C49-43C3-BD45-A9E24EE1535E@xxxxxxxxxxxxxxxx
As I thought. But there is nothing in documentation that says that it's
not
possible.
I have a x64 cluster where this works great and a x64wow cluster which is
troublesome.

I hoped MS would comment on this but I guess I have to file a support
case.

To Khwaja - please read the manual. When installing clustered named
instances the port number is randomly assigned.

Thanks for replies.
Rune

"Geoff N. Hiten" wrote:

For some reason, SQL Server does not like assigning named instances to
port
1433. Even though a clustered instance lives in its own virtual server
and
should not have a problem with 1433, I have run into problems trying to
get
it to work. I would suggest choosing another port and assigning all
your
instances to that port.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP




"ipconfig2" <ipconfig2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9EFC71C2-CAD3-45CE-910E-A831ACCB8562@xxxxxxxxxxxxxxxx
I am trying to change the port of an instance via the SSCM. Afther
changing
the TCP/IP protocol -> ALL IP -> Blank/1433 and restart the service it
goes
back to previous configuration.

Any ideas why? I want all my named instances to be using 1433.







.

Relevant Pages

  • Re: setting up a LAT service via a terminal server
    ... > node in my hobbyist cluster. ... Żou can put the download incantations in NCP, ... HELP DEFINE PORT will give you a pretty good idea what to do. ... > connections, but just one address for OUTgoing connections as well, the ...
    (comp.os.vms)
  • Re: How to Create a TCP/IP PrinterPort on a MS Cluster 2k3 via Scr
    ... XP is not in the cluster so I'm not clear on the failure question. ... the user running the script should be admin on the remote print server. ... thus the creation of the port on the node. ...
    (microsoft.public.windows.server.clustering)
  • Re: How to Create a TCP/IP PrinterPort on a MS Cluster 2k3 via Scr
    ... XP is not in the cluster so I'm not clear on the failure question. ... the user running the script should be admin on the remote print server. ... thus the creation of the port on the node. ...
    (microsoft.public.windows.server.clustering)
  • Re: client cant connect when instance on one particular node
    ... Best practice is to specify a specific port and then code the client to ... SQL 2000 SP4 for SQL version. ... Then server guys evicted ... cluster configuration. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Change SQL Port doesnt change
    ... on a single cluster must "listen" on a unique set of ports, one or more, as ... Geoff has stated that he has had difficulty running named instance on ... I guarantee you that you can run on static ports. ... I've never tried to run a named instance under the default port, ...
    (microsoft.public.sqlserver.clustering)