Re: [coLinux-users] andLinux not working on Windows 2000

[Luco <luc...@gm...>]

Hi all,

I'm still no further in getting this to work. Has anyone had any success 
using andLinux on Windows 2000? No matter what I do I can't get anything 
to happen.

The problem seems to stem from the absence of network bridge support in 
Windows 2000, and the internet connection sharing method produces the 
following error Terminal is run:

Could not launch 'Termnial': could not connect to 192.168.11.150:81

However, currently any changes to the network configuration have no 
effect on this. It is possible that I have missed something in the 
internet connection sharing settings, though if I have, it is not 
documented.

I have had this problem for around two months now, and discussions on 
coLinux IRC have verified that there should not be any problems. The 
problem is identical on both my machines, but andLinux runs first time 
on XP on the same machines.

Does anyone know the sequence of events that occurs when starting an ap 
in andLinux so that I might be able to track what is going wrong?

Thanks

NB: On installation I always get the error 'could not execute file: ss'

* Luco wrote, On 20/02/2008 01:28:
> Hi,
> 
> I actually posted this on the dev list, but this may be a better
> location. Although it is a tough one ;)
> 
> I have installed andLinux and enabled connection sharing on the physical
>  ethernet. The tap adaptor is currently on DHCP. Applications try but
> fail to connect to 192.168.11.150:81. The ethernet is currently static
> at 180.*
> 
> I've tried every possible combination of adjustments to my network
> settings for both adaptors, and disabled the firewall altogether but
> still no luck.
> 
> Of course this is on 2000. On XP everything works immediately and perfectly.
> 
> After the first installation attempt, I received the following message
> on subsequent attempts:
> 
> "Unable to execute file:
> sc
> 
> ShellExecuteEx failed; code 2
> The system cannot find the file specified"
> 
> Running a linux ap, such as Thunar produces the error:
> 
> "could not launch 'Thunar': could not connect to 192.168.11.150:81"
> 
> I've read most of the list archives, wiki, and website, and there isn't
> much more I can think of to do.
> 
> Interestingly (in the bad way), if I set the Tap adapter to DHCP,
> disable it, diable ICS on the ethernet, enable the tap, enable ICS on
> the ethernet, the tap will be set a static IP. Is this the cause of the
> problem?
> 
> Thanks
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/