You can specify any port number using the -x switch:
dbsrv10 -x tcpip(port=12345)
will listen on port 12345.
The default port number is 2638, so we listen on that port if none is
specified. If that port is not available, we begin at 49152 and keep
incrementing until we find a port number that is available. If your
clients are on the same subnet as the server (or you are using LDAP or
dbns), it doesn't really matter which port number you choose, since the
client will be able to find the server anyway. If your clients are on a
WAN or on the other side of a firewall, then they DO need to know what
port number the server is listening on, so it's a good idea to specify
the port number when you start the server.
Sybase has been assigned port number 2638 for use in SQL Anywhere, so no
other application is supposed to use that port number. Other port
numbers less than 49152 may be assigned to other companies and
applications, so we don't use those unless the user specifies them. Port
numbers from 49152 to 65535 are the dynamic and private port numbers,
which means that any application can use them.
Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering
SQL Anywhere Developer Community
http://www.sybase.com/developer/libr...ere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs
Claude wrote:
Quote:
Without specifying a port paramter, the first database start at port 2638.
I set up a second database ( as another service ) and it starts on port
49152.
What is the logic of this port 49152.
I suspect it is better to impose the port, but which port can be used ?
Claude |