andlinux.org

[kroesjnov]

Hi,

I ran into the can't connect to 192.168.11.150:81 issues which can be found on the forum quit often. As I have found a solution for my specific case, I thought I'd share it here;

Problem
Although everything seemed to be configured correctly on the TAP interface and in Ubuntu, I was unable to get any form of network communication going between 192.168.11.1 and 192.168.11.150, and as such could not start any programs via andLinux.

No proposed solution on the forum did any good, but I did get a somewhat helpful hint when I did an <INSTALL_DIR>\colinux-net-daemon.exe -i <PID> -u 1 (as explained in [1]), as this yielded a hardware error. (It might be nice to note the PID of a process is not shown by default in taskmgr, and you need to enable this under view[/b] -> [i]select columns)

[1] http://www.andlinux.org/forum/viewtopic.php?p=681#681

Solution
As it turns out I was (most likely) experiencing a conflict with an already install TAP driver (which at least claimed to be the same version). In my case this TAP device was installed by SSH Sentinel (v1.3.22). After uninstalling SSH Sentinel and andLinux, rebooting, and installing andLinux again, I was finally able to use andLinux to it's full extend without any form of a problem.

A possible other explanation could be that SSH Sentinel also does something with your TCP/IP stack if I recall correctly. If I were to bet though, I'd set my money on the first horse, and I think it's worth a try if you run into similar problems and also have another TAP device on your system.