NOTICE: Our Community is moving. Get more information.
Why can"t the CaliberRM Client connect to MPX Broker installed on multi-homed host?
Problem: Some or all CaliberRM Clients receive
the following message when starting:
MPX support was enabled, but client failed to connect to MPX server
(MPXHost). Continuing without MPX.
Potential Cause: The MPX Broker host has
multiple NICs attached to different networks
If the machine hosting the StarTeam MPX Message Broker service has
multiple Ethernet cards (NICs) attached to different networks
(different IP address ranges), the Broker may have bound itself to
an IP address different than the one the host"s network name
To confirm that this is indeed the issue affecting you, first run
"ping (MPXHost)" from a CaliberRM Client machine,
replacing "(MPXHost)" with the name of the actual machine
hosting the MPX Broker, and note the IP address returned.
Next, run "netstat -a -n -p TCP" on the MPX host, find
the line in the "Local Address" column that ends in
":5101" and note the IP address preceding
":5101". If these IP addresses differ, then the MPX
Broker has bound itself to a different IP address than the client
is attempting to access.
Solution: Manually bind your MPX Broker to a
client-accessible IP address
First, stop the "StarTeam Message Broker" service in the
Windows Management Console and stop the CaliberRM Server.
Next, locate the directory where the MPX Broker is installed and
open the "STMessageBroker...ini" file found there.
The exact file and directory names will depend on the MPX Broker
version installed, but the default install location for recent
releases is in the ..\Program Files\Borland directory.
Add the following line to the bottom of the file, replacing
"W.X.Y.Z" with the MPX Broker host machine"s IP
address as seen in the "ping" test (Note: not the
setopt conn_names tcp:W.X.Y.Z:5101
NOTE: If there are multiple
NIC’s and/or multiple IP’s that are in the same domain
and requests are valid for *any IP on that server, then it
may be necessary to bind all IP addresses, separated by commas, as
in the example below:
setopt conn_names tcp:W.X.Y.Z:5101, A.B.C.D:5101
Save the changes to this file and restart the "StarTeam
Message Broker" service, then restart the CaliberRM
The "netstat" test should now show port 5101 associated
with the same IP address the CaliberRM Client attempts to contact,
and your CaliberRM Clients should now be able to use MPX
Please note that the MPX Broker must be bound to an address that is
accessible to all MPX clients, which may complicate matters.
If you are unable to resolve the issue for some clients without
breaking MPX for others, please contact Borland Support for