If this solution doesn't fit what you are asking, please provide a little more information on why you have two NICs instead of just the one and transferring through them. I'm assuming that the IP Networks are different on the NICS that are connected with a cross over cable. (They should be-- otherwise you <b>WILL </b>have connectivity problems.) I will call this the private network. I would create a hosts or lmhosts entry on the first server for the second server pointing to the private network address of the second server. The hosts and lmhosts files are located in <i>C:WINDOWSsystem32driversetc</i> on windows. The format of the entry would be (substituting your IP address and server name): 192.168.0.1 Server2 Then do the same for the second server pointing to teh first server and it's IP address, like so: 192.168.0.2 Server1 That should ensure the transmission goes across the secondary nics. Some things to think about: 1. Make sure your nics are set to a specific speed, and that they are the same. With out switches I would not recommend trying a setting of AUto or Auto-Negotiate. 2. Under the network properties of the secondary Nics (in TCP/IP settings) be sure and uncheck "register this connection with DNS" so that it doesn't announce that connection to a DNS server (if you every have AD, this setting will save you some greif.) 3. You might also want to try to disable the Microsoft Client (But not file and print sharing for Microsoft Networks) so the Secondary NIC's don't get used in the event teh servers ever win a browser election. (If they did win and the NIC was used your client machines wouldn't be able to communicate to the master browser and create issues in Network Neighborhood.

If this solution doesn't fit what you are asking, please provide a little more information on why you have two NICs instead of just the one and transferring through them. I'm assuming that the IP Networks are different on the NICS that are connected with a cross over cable. (They should be-- otherwise you <b>WILL </b>have connectivity problems.) I will call this the private network. I would create a hosts or lmhosts entry on the first server for the second server pointing to the private network address of the second server. The hosts and lmhosts files are located in <i>C:WINDOWSsystem32driversetc</i> on windows. The format of the entry would be (substituting your IP address and server name): 192.168.0.1 Server2 Then do the same for the second server pointing to teh first server and it's IP address, like so: 192.168.0.2 Server1 That should ensure the transmission goes across the secondary nics. Some things to think about: 1. Make sure your nics are set to a specific speed, and that they are the same. With out switches I would not recommend trying a setting of AUto or Auto-Negotiate. 2. Under the network properties of the secondary Nics (in TCP/IP settings) be sure and uncheck "register this connection with DNS" so that it doesn't announce that connection to a DNS server (if you every have AD, this setting will save you some greif.) 3. You might also want to try to disable the Microsoft Client (But not file and print sharing for Microsoft Networks) so the Secondary NIC's don't get used in the event teh servers ever win a browser election. (If they did win and the NIC was used your client machines wouldn't be able to communicate to the master browser and create issues in Network Neighborhood.