Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Reserved Ports

Author  Topic 

franco
Constraint Violating Yak Guru

255 Posts

Posted - 2005-03-11 : 08:24:13
I know this is not a SQL Server related question but I hope somebody can help anyway.
Environment:
Windows Server 2003
2 node cluster
SQL Server 2K sp3a
and finally (last week) Domino Server 6.5.3 and here comes the problem:

We have a problem with Reserved Ports and on the Internet I found this:

"The cluster service is installed by default as a part of Windows 2003 and
therefore has the registry configured to protect it´s default port 3343.
When Domino Server is installed it overwrites the registry key for the
cluster service with it´s own port, thereby breaking the cluster service.

The workaround is to delete the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ReservedPorts

and then recreat the registry key as a REG_MULTI_SZ value and include
3343-3343 and 1352-1352 as the values."

In fact we no more have the registry key with the value of 3343 but only a
key with the value of 1352.

2 Questions:

What can happen if we do not change this value?
Is it correct to modifiy the registry keys to there original value?

Please advise.


Franco

Franco

JCamburn
Starting Member

31 Posts

Posted - 2005-03-11 : 16:58:15
This is completely a guess, but:

If both ports are not reserved, you could have external requests interfere with the proper operation of either the Cluster Services or of the Domino Server.

Cluster Services is probably going to try to use port 3343 (according to what you have said) as its default port for monitoring the "health" of the active node.

Reserving port 1352 is probably necessary for Domino Server to function correctly on its default port as well.

I would say that you would probably be fine reserving both 3343 and 1352 by making the registry changes that are recommended in the knowledge base article (assuming nobody else has made configuration changes to either of the services to modify their default port).

Again, this is just a guess. So don't try to sue me if it turns out that I'm totally off base.
Go to Top of Page
   

- Advertisement -