Problem socket.bind() with multiple modems and multiple IPs

Question

I've connected 2 or more modems in Windows control panel and made up windows dail ups. Then I dail up each modem and obtain the local DHCP IPs of each modem.
My target is : to set up sockets using separate modems.
the code is like: create a socket instance , and use Socket.bind()method to bind the socket to a specified modem's local IP , then do socket.connect().
but the problem is : although there are several modem dail ups and at the same time I bind each socket to different IPs , the program always connect via the first modem dailed up.
Does Socket.bind() method really bind the socket connection to the IP's or hardwares?

Answer 1

I think you are trying to use a Socket where you want a ServerSocket to accept the incoming connection. Check this out (I have underlined what
should interest you):
public ServerSocket(int port, int queueLength) throws IOException, BindException
This constructor creates a ServerSocket on the specified port with a queue length of your choosing. If the machine has multiple network interfaces or IP addresses, then it listens on this port on all those interfaces and IP addresses. The queueLength argument sets the length of the queue for incoming connection requests--that is, how many incoming connections can be stored at one time before the host starts refusing connections. Some operating systems have a maximum queue length, typically five. If you try to expand the queue past that maximum number, the maximum queue length is used instead. If you pass 0 for the port number, the system selects an available port.
For example, to create a server socket on port 5,776 that would hold up to 100 incoming connection requests in the queue, you would write:
try {
  ServerSocket httpd = new ServerSocket(5776, 100);
catch (IOException e) {
  System.err.println(e);
}The constructor throws an IOException (specifically, a BindException) if the socket cannot be created and bound to the requested port. An IOException when creating a ServerSocket almost always means one of two things. Either the specified port is already in use, or you do not have root privileges on Unix and you're trying to connect to a port from 1 to 1,023.
So once you receive a connection, it looks like it is up to you parse any
relevant info you want out of the Socket you get from ServerSocket.accept();
-Cludge