<SteveMorgan@discussions.microsoft.com> wrote:

>Hi Sue
>
>Thnx for the reply but thats not my question - I know how to check the port
>numbers currently being used.
>
>What I need to work out is whether during the install the option to
>dynamically assign instance port numbers was choosen or if they were
>pre-choosen & hardcoded.
>
>According to a technet article on connectivity problems this decision
>affects whether on the client machine you can use the <server>\<instance
>name> in your connection string or whether you have to use <server>\<port
>number>
>
>I'm having intermittent connection problems usine <server>\<instance name>
>and want to know if the install port decision could be the root cause.
>
>Steve
>
>
>"Sue Hoegemeier" wrote:
>
>> If you are looking for a registry key to determine if SQL
>> Server is listening on the default port, it's located at:
>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Tcp
>> That will give you the listening port.
>> You can also get the information from the SQL Server log.
>> You can also get the information using various network
>> commands, tools.
>>
>> -Sue
>>
>> On Tue, 30 Nov 2004 08:55:09 -0800, Steve Morgan
>> <SteveMorgan@discussions.microsoft.com> wrote:
>>
>> >I undstand that if you choose to dynamically assign a port number to an
>> >instance this is a once only operation performed the first time that instance
>> >is started and from then on it always attepts to use that port number.
>> >
>> >Having just started with a new company I'm trying to work out if instance
>> >port numbers were assigned dynamically or hardcoded during install as this
>> >affect the client connection properties for connections (if hardcoded each
>> >client needs to be configured with the port number rather than allowing an
>> >instance to be resolved to a port).
>> >
>> >Is there a regkey or anything that says how ports were assigned?
>> >
>> >Steve
>>
>>