Consultor Eletrônico

Unable to find server with protocol "tcp" in /etc/services.

The following error can result when trying to either start a broker
to allow for remote clients, or when trying to start a remote client
session:

Unable to find server xx with protocol "tcp" in /etc/services. (777)

If you see this error, do the following:

1. In /etc/services on the host machine you will need to make the
following entries:

Example (using demosv as the service for this example):

demosv 2500/tcp
demosv1 2501/tcp
demosv2 2502/tcp
demosv3 2503/tcp
demosv4 2504/tcp
nextdbsv 2510/tcp
nextdbsv1 2511/tcp
nextdbsv2 2512/tcp
etc.

For each service you need to specifically enter a service for
each of the remote client servers. Then leave a space to the
next 10th entry. Notice how the nextdb service starts at 2510
instead of 2505. This leaves room for additional remote client
servers to be spawned if appropriate.

2. Make the same changes to the /etc/services file on the remote
machine. The entries must be identical for the connection to be
made.

3. Start the broker on the host machine by typing:

proserve <dbname> -H hostname -S demosv

where "hostname" is the hostname of the machine where you are
starting the broker.

Example: proserve demo -H sun4 -S demosv

4. Start a client session on the client machine by typing:

mpro <dbname> -H hostname -S demosv

where "hostname" is the hostname of the machine where you
started the broker.

Example: mpro demo -H sun4 -S demosv

5. If you still see the error 777 and have made the changes to
/etc/services, you may be running yellow pages in which case there
is one master services file that may not have been updated.

To verify if this is the case, type:

ypcat services

you can pipe this output to more: ypcat services | more
If the service entries are not in that file, you will need
to make these additions. Then the broker and client should start
up without error.

Progress Software Technical Support Note # 13818