Port number change not sticking? 
Author Message
 Port number change not sticking?
Hey all!

On Microsoft SQL Server 2000... why is it that when I change the Port number
that the server listens on, that it does not remember the change? Currently
the port is 2433. I change it, I'm told to restart the server for changes to
take effect (which I do), and the setting is back to 2433.

I'm trying to set it back to the default port number but it refuses to do
so.

Am I missing something or is this broken?



Tue, 27 Sep 2005 15:51:21 GMT
 Port number change not sticking?

Hi

Just wondering.. if you set it to a different number does it work?

This port may already be reserved for something else?

These are locations in the registry that should be changed... there may be
others!
HLM\Software\Microsoft\MSSQLServer\Client\SuperSocketNetLib\VIA\DefaultServe
rPort
HLM\Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Tcp\TCPPort
HLM\Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\VIA\ListenI
nfo
HLM\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters\ReservedPorts

John


Quote:
> Hey all!

> On Microsoft SQL Server 2000... why is it that when I change the Port
number
> that the server listens on, that it does not remember the change?
Currently
> the port is 2433. I change it, I'm told to restart the server for changes
to
> take effect (which I do), and the setting is back to 2433.

> I'm trying to set it back to the default port number but it refuses to do
> so.

> Am I missing something or is this broken?



Wed, 28 Sep 2005 17:06:54 GMT
 Port number change not sticking?
Thanks for the info!

Port 1433 and 1434 show up as reserved ports... not a clue as to what
is reserving them.

Tried to change the TCPPort number from 2433 to 1433, and it didn't do
any good. I honestly think I've wrecked something earlier trying to
get it to work.

Goign to uninstall/reinstall and see what happens.


Quote:
> Hi

> Just wondering.. if you set it to a different number does it work?

> This port may already be reserved for something else?

> These are locations in the registry that should be changed... there
may be
> others!

HLM\Software\Microsoft\MSSQLServer\Client\SuperSocketNetLib\VIA\Defaul
tServe
Quote:
> rPort

HLM\Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Tcp\T
CPPort
HLM\Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\VIA\L
istenI
Quote:
> nfo
> HLM\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters\ReservedPorts

> John



> > Hey all!

> > On Microsoft SQL Server 2000... why is it that when I change the
Port
> number
> > that the server listens on, that it does not remember the change?
> Currently
> > the port is 2433. I change it, I'm told to restart the server for
changes
> to
> > take effect (which I do), and the setting is back to 2433.

> > I'm trying to set it back to the default port number but it
refuses to do
> > so.

> > Am I missing something or is this broken?



Thu, 29 Sep 2005 13:39:30 GMT
 Port number change not sticking?
Hi

I would expect 1433-1434 to be reserved by SQL Server, this should obviously
change if you change the ports.

You are changing these in the Server Network Utility and the Client Network
Utility?

John


Quote:
> Thanks for the info!

> Port 1433 and 1434 show up as reserved ports... not a clue as to what
> is reserving them.

> Tried to change the TCPPort number from 2433 to 1433, and it didn't do
> any good. I honestly think I've wrecked something earlier trying to
> get it to work.

> Goign to uninstall/reinstall and see what happens.



> > Hi

> > Just wondering.. if you set it to a different number does it work?

> > This port may already be reserved for something else?

> > These are locations in the registry that should be changed... there
> may be
> > others!

> HLM\Software\Microsoft\MSSQLServer\Client\SuperSocketNetLib\VIA\Defaul
> tServe
> > rPort

> HLM\Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Tcp\T
> CPPort

> HLM\Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\VIA\L
> istenI
> > nfo
> > HLM\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters\ReservedPorts

> > John



> > > Hey all!

> > > On Microsoft SQL Server 2000... why is it that when I change the
> Port
> > number
> > > that the server listens on, that it does not remember the change?
> > Currently
> > > the port is 2433. I change it, I'm told to restart the server for
> changes
> > to
> > > take effect (which I do), and the setting is back to 2433.

> > > I'm trying to set it back to the default port number but it
> refuses to do
> > > so.

> > > Am I missing something or is this broken?



Thu, 29 Sep 2005 19:16:40 GMT
 Port number change not sticking?

Quote:
> I would expect 1433-1434 to be reserved by SQL Server, this should
obviously
> change if you change the ports.

> You are changing these in the Server Network Utility and the Client
Network
> Utility?

I was making the changes through the "SQL Server Network Utility"...
Click TCP/IP in the Enabled protocols to highlight it, click the
Properties button and change the port number, Click OK, Click OK on
the popup message that says to stop and start the server. I close the
Network Utility and Open the "SQL Server Service Manager" and stop the
server and wait a bit. Once stopped I start the server again. Once the
SQL server is started I go back to the Network Utility and go back to
the TCP/IP properties and it's back to the old port number of 2433.

To make this worse, I did an uninstall of SQL Server last night.
Deleted all my data files as well as the program files. I then
reinstalled SQL server and applied SP3. The server *STILL* insists on
using port 2433. (all steps had reboots in between)

I didn't have these issues with MySQL and I think it will be cheaper
in the long run to supply a dedicated server for my apps instead of
running on the 'customers' pre-existing server. If just getting a
development environment working is so hard I can image what will
happen if my application does something unexpected and needs to be
debugged.

Quote:
> > Port 1433 and 1434 show up as reserved ports... not a clue as to
what
> > is reserving them.

> > Tried to change the TCPPort number from 2433 to 1433, and it
didn't do
> > any good. I honestly think I've wrecked something earlier trying
to
> > get it to work.

> > Goign to uninstall/reinstall and see what happens.



> > > Hi

> > > Just wondering.. if you set it to a different number does it
work?

> > > This port may already be reserved for something else?

> > > These are locations in the registry that should be changed...
there
> > may be
> > > others!

HLM\Software\Microsoft\MSSQLServer\Client\SuperSocketNetLib\VIA\Defaul
Quote:
> > tServe
> > > rPort

HLM\Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Tcp\T
Quote:
> > CPPort

HLM\Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\VIA\L
Quote:
> > istenI
> > > nfo

HLM\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters\ReservedPorts

- Show quoted text -

Quote:

> > > John



> > > > Hey all!

> > > > On Microsoft SQL Server 2000... why is it that when I change
the
> > Port
> > > number
> > > > that the server listens on, that it does not remember the
change?
> > > Currently
> > > > the port is 2433. I change it, I'm told to restart the server
for
> > changes
> > > to
> > > > take effect (which I do), and the setting is back to 2433.

> > > > I'm trying to set it back to the default port number but it
> > refuses to do
> > > > so.

> > > > Am I missing something or is this broken?



Fri, 30 Sep 2005 05:04:38 GMT
 Port number change not sticking?
Hi

I am at a loss to see why you can't do this unless some other system
has already taken the port.

John

Quote:

> > I would expect 1433-1434 to be reserved by SQL Server, this should
>  obviously
> > change if you change the ports.

> > You are changing these in the Server Network Utility and the Client
>  Network
> > Utility?

> I was making the changes through the "SQL Server Network Utility"...
> Click TCP/IP in the Enabled protocols to highlight it, click the
> Properties button and change the port number, Click OK, Click OK on
> the popup message that says to stop and start the server. I close the
> Network Utility and Open the "SQL Server Service Manager" and stop the
> server and wait a bit. Once stopped I start the server again. Once the
> SQL server is started I go back to the Network Utility and go back to
> the TCP/IP properties and it's back to the old port number of 2433.

> To make this worse, I did an uninstall of SQL Server last night.
> Deleted all my data files as well as the program files. I then
> reinstalled SQL server and applied SP3. The server *STILL* insists on
> using port 2433. (all steps had reboots in between)

> I didn't have these issues with MySQL and I think it will be cheaper
> in the long run to supply a dedicated server for my apps instead of
> running on the 'customers' pre-existing server. If just getting a
> development environment working is so hard I can image what will
> happen if my application does something unexpected and needs to be
> debugged.

> > > Port 1433 and 1434 show up as reserved ports... not a clue as to
>  what
> > > is reserving them.

> > > Tried to change the TCPPort number from 2433 to 1433, and it
>  didn't do
> > > any good. I honestly think I've wrecked something earlier trying
>  to
> > > get it to work.

> > > Goign to uninstall/reinstall and see what happens.



> > > > Hi

> > > > Just wondering.. if you set it to a different number does it
>  work?

> > > > This port may already be reserved for something else?

> > > > These are locations in the registry that should be changed...
>  there
>  may be
> > > > others!

>  HLM\Software\Microsoft\MSSQLServer\Client\SuperSocketNetLib\VIA\Defaul
> > > tServe
> > > > rPort

>  HLM\Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Tcp\T
> > > CPPort

>  HLM\Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\VIA\L
> > > istenI
> > > > nfo

>  HLM\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters\ReservedPorts

> > > > John



> > > > > Hey all!

> > > > > On Microsoft SQL Server 2000... why is it that when I change
>  the
>  Port
>  number
> > > > > that the server listens on, that it does not remember the
>  change?
>  Currently
> > > > > the port is 2433. I change it, I'm told to restart the server
>  for
>  changes
>  to
> > > > > take effect (which I do), and the setting is back to 2433.

> > > > > I'm trying to set it back to the default port number but it
>  refuses to do
> > > > > so.

> > > > > Am I missing something or is this broken?



Fri, 30 Sep 2005 16:07:47 GMT
 Port number change not sticking?
Did another uninstall and this time scoured the registry for any MSSQL
type settings.

After this install it all seems OK. Now I'm having problems connecting
to the server. I'm sure I'm just configuring something wrong in the
authentication though. It does connect fine using the Windows Only
method with the current user (administrator) but none of my added
users.

I've picked up a book and will be stepping through that to understand
whats happening.

Thanks for the help!!!

Quote:
> I am at a loss to see why you can't do this unless some other system
> has already taken the port.

> John
> > I was making the changes through the "SQL Server Network
Utility"...
> > Click TCP/IP in the Enabled protocols to highlight it, click the
> > Properties button and change the port number, Click OK, Click OK
on
> > the popup message that says to stop and start the server. I close
the
> > Network Utility and Open the "SQL Server Service Manager" and stop
the
> > server and wait a bit. Once stopped I start the server again. Once
the
> > SQL server is started I go back to the Network Utility and go back
to
> > the TCP/IP properties and it's back to the old port number of
2433.

> > To make this worse, I did an uninstall of SQL Server last night.
> > Deleted all my data files as well as the program files. I then
> > reinstalled SQL server and applied SP3. The server *STILL* insists
on
> > using port 2433. (all steps had reboots in between)

<snip>


Sat, 01 Oct 2005 05:45:32 GMT
 
 [ 7 post ] 

 Relevant Pages 

1. Changing DB with sp_msforeachdb -- not "sticking"

2. Problems connecting to the default instance after changing the port number from 1433 to 1470

3. change port number

4. SQL Server Port Number Changed

5. How to change the SQL 7 server port number

6. change the default port number

7. Changing the default port number in SQL7

8. SQL Server Port Number Change

9. Changing TCP/IP port number on SQL 6.5

10. Changing Port Numbers

11. Changing port number

12. Changing the TCP port number for FMPro Server


 
Powered by phpBB® Forum Software