David, Thank you for your advice which solved the TCPIP startup problem. It is now possible to telnet a Linux virtual machine (at 192.168.1.2) from another virtual machine. What does not work yet, is the connection from Windows. (We do not use Linux on the workstations.)
After the Windows command route add 192.168.1.0 mask 255.255.255.0 192.168.0.4, it is impossible to ping 192.168.1.2. Pinging 192.168.1.1 works (there is a virtual lan 192.168.1 on the harware router). But I suppose that these Windows problems are not in the scope of this list. Thanks again. Best regards, Antoon Vekeman Software Product Research Software Solutions for DB2 http://www.sprdb2.com B-2288 Bouwel Belgium On Fri, 10 Aug 2007 18:13:53 -0400, David Boyes wrote: >You are using the VM TCP stack as a layer 3 router. That means that you >must have different subnets for the LCS and hipersocket interfaces >(either by splitting the 192.168.0 network with the netmask, or by using >a different subnet of the 192.168 space for the hipersocket link. >The easy way is to set the hipersocket interface to 192.168.1.1, number >all your linux guests as 192.168.1.x with a default gw of 192.168.1.1. >The last step is to make sure that the other devices on your network >that need to reach machines on the hipersocket LAN have a routing entry >for 192.168.1.0/255.255.255.0 via 192.168.0.4 as the gateway. For Linux, >that would look like: >route add net 192.168.1.0 netmask 255.255.255.0 gw 192.168.0.4 >Windows should be something similar.
