Connect Requests are Specific to IP Addresses

In a connection-oriented transport, the definition for a connect end hard-configures a specific IP address at the listening end.

Consider these consequences:

• A connect end transport definition can operate on several different host computers, as long as the listening end port is already open.
• A listen end transport must run at the location where its connect end counterparts expect to find it.
• If you move a listen end process to another host computer, you must reconfigure its counterpart connect end so it can find the listen end.
• If you move a connect end process to another host computer, you need not modify its counterpart listen end.
• A connect end must direct its connection requests to a listen port on one specific network interface of the host computer at the listen end. That is, you must specify either an IP address or a host name, but asterisk (*) is not valid. The listen port must be open on that network interface, otherwise the connection request fails.
• A listen end transport may open a listen port on all available network interfaces, or on only one. That is, you may specify asterisk (*) as the host interface, or you may specify a specific IP address or host name.