andlinux.org

[Quentin QueerPiece]

Could some of you Linux egg heads out there, please throw me a fricking bone, before I go flipping bonkers?

Like many Linux virgins on here, I just cannot seem to run any of the andLinux programs in the main menu bar, without getting the now infamous "konsole: cannot connect to X server 192.168.11.1:0.0" error type messages,
for each and everyone of the menu icons.

After auto-running at Windows startup (with loads of Disk thrashing!) and inspecting the console Co-operative Linux window, after Linux attempts to boot, it always finishes with the following error messages:

[godjonez]

You error messages seem similar to mine.

For me it works this way:

1. Start andLinux service with the Kmenu and Xming
2. Wait for everything to settle down (a few seconds)
3. Open Network Connections
4. Right click on TAP-Colinux and Disable it
5. When it has been disabled, right click on it again and Enable it
6. Since now it says Network cable unplugged, stop andLinux and restart it again.

I don't know why it works like it does, but that's the procedure I need to do after every clean boot to get andLinux work properly.

[wap3]

This worked for me.
Considering your network IP is in 192.168.x.x and not 172.16.x.x or 10.x.x.x

In network setting of windows, right click on TAP-Colinux.
Go down to TCP/IP and select Properties.
Change the Subnet Mask from 255.255.255.0 to 255.255.0.0.
Do the OK dance then REBOOT.

My network is based on 192.168.10.x [router is 10.1] that's fine
andLinux uses 192.168.11.x that is fine
But the 2 can not work together as the 3rd 255. is restricting networking to an exact match - either 10 or 11 but not both.

Yes there is some obscure number like .251 or such that will basically open up only 10 and 11 but what the heck, it is all behind a router anyway..

[Quentin QueerPiece]

[Quentin QueerPiece]

[wap3]

Mr. QueerP,

I will forgo asking who lit the fuse on you tampon, as that is evident by your *word-salad* post.

So, to the point, networking is probably the root of your issue.
[that is what you don't understand about my post]

Please do the following.

1) Start>Run
2) type CMD and hit enter
3) type IPCONFIG /ALL and hit enter
4) highlight the results
5) right click on the title bar and chose EDIT > COPY
6) paste that in your reply

PS: by the way my head does not look like an egg

PS2: you missed the part on the download page about BETA-1 software and for that matter so is MS Vista.
Sound is not working for me on Win2k but it is not important at this
point and there are forum posts how to fix it.

[gap]

I have a similar problem.

My installation worked once, when installed as a service. I didn't want that, so I uninstaled/reinstalled everything several times, trying to get "on demand" to work. ("on-demand" doesn't work at all, even in an fltk terminal, but I'm not here to talk about that.)

Running as a service, I can log in using an fltk window. But no X.
I get "can't connect to 192.168.11.1:0.0 " if I try to lauch xterm from an fltk window, but if I try to launch a terminal from the tray icon, it's 192.168.11.150:81 that won't connect.

both addresses are in X0.hosts.

But there's more: Each time I uninstall/reinstall, a new TAP-Colinux is installed. I now have five of them, and I can't get rid of them. (right click "delete" is grayed out)

And:

C:\Documents and Settings\Gary>ipconfig
Windows IP Configuration
An internal error occurred: A device attached to the system is not functioning.
Please contact Microsoft Product Support Services for further help.
Additional information: Unknown media status code.


Anyone got a clue?

-gap

[Quentin QueerPiece]

[kroesjnov]

[nick.barlow]

I also experienced a problem with my TAP-Colinux connection.

After much mucking around I found that the installer had named my connection:

Local Area Connection2

Rather than:

TAP-Colinux

After renaming the connection to the correct name, the problem was fixed and I can now connect.

[adub]

i have the same exact problem and i have been working on this for a while.

"can't connect to 192.168.11.1:0.0 "

and when trying to launch kde apps i get cannot connect to konsole 192.168.11.150:81

when not having the cooperative linux

I have tried all the suggestions in this post tried reinstalling with NT service and not nt service starting up manually

I am clueless at this point as to what to do

[LeeDB]

On my desktop, I had the same problem until I reinstalled andLinux and checked the box to run it automatically as an NT service. On my laptop, however, even that didn't work.

Here's what I did to get the laptop up and running. First I moved the launcher port to 8081 using the procedure below from the Wiki (quick tips).

Add the following text to a text file and rename it to Launcher.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\andLinux\Launcher]
"IP"="192.168.11.150"
"Port"=dword:00001f91

Then double-click the Launcher.reg file to add it to your registry.
Also, in your control panel, double-click Windows Firewall and click the exceptions tab. Then click the add port button. Name it whatever you want and enter 8081 for the port. Leave TCP checked and click OK.

In my case, the above got it working until the next re-boot. I got it working permanently by doing the following: From control panel (classic view), double-click "administrative tools", then double-click services. (note: you have to be running andLinux as a service.) Right click on the andLinux service and click properties. Click the logon tab, then click on "this account". Next click the browse button, then the advanced button, then the find now button. Find the user account you are currently using, highlight it, and click OK. Then click OK on the previous 2 open windows to finish out the login selection. I don't know why this worked, but it did for me.

[LeeDB]

Well, I spoke too soon. The procedure in my previous post worked for several hours even after a couple of restarts, but as soon as I did a full shutdown and a cold start, the same problem returned. When I try to launch any KDE app, the result is "could not launch 'appname': could not connect to 192.168.11.150:". Strange, while I was writing the above, I kept trying, and on about the 5th or 6th try, Konsole finally came up. And I can ping 192.168.11.150 now, but I could not when things were failing previously. Oh well, maybe the service is taking forever to start for some reason.

[fuujuhi]

[fuujuhi]

Note that actually, the name of the network interface must match the one given in the configuration file settings.txt.

For instance in my case I have: