Valid port ranges for SQL Server 2000
From: Glen Moffitt (gd.moffitt_at_verizon.net)
Date: 07/29/03
- Next message: Audrey Lim: "Permissions to syslogins"
- Previous message: Marc Melfi: "Password for SQL Server"
- Next in thread: Kevin: "Re: Valid port ranges for SQL Server 2000"
- Reply: Kevin: "Re: Valid port ranges for SQL Server 2000"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 29 Jul 2003 07:16:09 -0700
I'm looking at tweaking a few SQL 2000 servers, some with multiple
instances, to use non-standard TCP port assignments. Question is,
what's good and bad? Much of the MS documentation just alludes to the
fact you can (should) do this, but makes no specific recommendation as
to *what* port values can/should work. I did find a reference to the
iana official list of port numbers:
http://www.iana.org/assignments/port-numbers
So these are divided into three major sections: 1) 0-1023 ("well
known port numbers"), 2) 1024-49151 ("registered ports"- hmm, someone
called the "Cinderella Collaberation" has their own port?..), and 3)
49152-65535 ("Dynamic and/or Private").
Anyone had any good/bad luck with these port ranges? I would take it
avoid the registered and already assigned ones? Can sql and standard
client take a range up to 65535?
thks
- Next message: Audrey Lim: "Permissions to syslogins"
- Previous message: Marc Melfi: "Password for SQL Server"
- Next in thread: Kevin: "Re: Valid port ranges for SQL Server 2000"
- Reply: Kevin: "Re: Valid port ranges for SQL Server 2000"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|