Hi, Another data point for VNET problems: Last time I used Win4Lin 3 I had just restarted my machine. I use DHCP on eth0, but the DHCP server wasn't available so eth0 didn't get configured. I'm was using an ethertap configuration with Win4Lin (see an earlier post), so W4L should be binding to the same subnet as my tap0 device, *not* eth0. When I started W4L without the eth0 device configured, the networking failed (windows pops up with a "network device not working" message box). Configuring the eth0 device by hand solved the problem, as did putting 'tap0' as the VNET interface in /etc/default/merge. W4L started fine, and was talking via the tap0 device. I had to restart the vnetd between each of these configuration changes. Hope this is of some interest to somebody! -- Jonathan Paisley [EMAIL PROTECTED] _______________________________________________ Win4Lin-users mailing list [EMAIL PROTECTED] https://lists.netraverse.com/mailman/listinfo/win4lin-users
