[coLinux-devel] networking question

[Nigel S. <Nig...@BT...>]

using the latest binaries provided colinux is working for me 
on win2k.

I got the 'fsck' problem on startup but i've hacked the 
scripts so the check is ignored, and linux starts up nicely.

however, the linux machine doesn't seem to be able to 
communicate to the win2k through tcp/ip. the tap-win32 driver 
becomes 'connected' when the linux daemon is started, and 
windows reports that it gets a autoconfig ip address 
(169.253.x.x).

the colinux instance think's it's interface is up, and is 
configured the private ip of 192.168.0.40. pinging this ip 
causes ping to report:
   ping: sendto: Invalid argument
   ping: wrote 192.168.0.40 64 chars, ret=-1

have i missed a configuration step of the Tap-win32 driver ?

thanks

nigel