NX Client in DSL Embedded?

Forum: DSL Embedded
Topic: NX Client in DSL Embedded?
started by: matthinckley

Posted by matthinckley on April 14 2006,21:16

Hello everyone,

I use Ubuntu at home on my desktop PC and I use DSL Embedded on my usb-key so I can get away from windows when I'm at work and school.. anyways I use the freenx server at home and I can connect to it from work and my linux notebook but when I try to connect from DSL Embedded it just sits there at the black screen with the !M logo and then it pops a dialog box telling me there was no response from the server, but i can't click on it.. I have to restart X to get back to normal.

Is there something i'm not doing right?

I know qemu has some weird networking via the host so maybe NX just doesn't work with DSL Embedded?

Thanks

Matt

Posted by dare2dreamer on April 14 2006,22:29

If you are going over ssh, make sure your sessions' got the "enable ssl encryption of all traffic" box checked under the advanced tab. That way, it _only_ routes over port 22/ssh. Since you are probably going through firewalls and the like, it's a common culprit.

I've used the NXclient extension with embedded without issues in the past, so I'm willing to wager that the problem lies in some other portion of the "connection chain".

Feel free to post details so we can try and sort you out.

Posted by matthinckley on April 15 2006,15:45

I double checked and the "enable ssl encryption of all traffic" is checked.. also i did a 'ps -U matt' on my home computer this morning and apparently every time I try to log in with nxclient from DSL it leaves nxnode and sshd running on my home computer.. I had like six of each running.

What kind of details would you like?

I looked for a log file for NX but couldn't find it..

Thanks

Matt

Posted by matthinckley on April 15 2006,17:58

OK I set the server to create logfile..

here is the servers logfile after trying to connect from DSL

< server log >

here is the client log from DSL

< DSL client log >

here is the client log from Windows at work (which works fine)

< WIN client log >

I'm wondering if the 'no suitable cache file found' is causing my problem?

Thanks

Matt

Posted by matthinckley on April 22 2006,15:14

Oh I don't have to restart X.. if I wait about 3 minutes it will close the nxclient screen and tell me that the session has closed

any suggestions?

Thanks

Matt

Posted by dare2dreamer on April 24 2006,03:12

From the looks of it, (and I'm guessing from the output) you're experiencing some sort of timeout on the dsl-client side. Of course this could be from it simply erroring out.

Is it running through a proxy or firewall? Post back with how the network is laid out between nxserver, winclient and dslclient for reference.

As for troubleshooting, I'd start with the basics. Can you ssh into the linux box that acts as nxserver from the dsl-nxclient?

You might also try clearing out your ~/.nx client directory on the client, just to be sure no garbage is still lying about. I'd delete the whole thing and recreate your sessions, just to make sure your nx temp directory isn't munged or anything silly like that.

Keep plugging at it, we'll sort it out.

Posted by dare2dreamer on April 24 2006,03:14

oh, one more thing worth trying. Create a session that isn't fullscreen. It might be causing qemu some headaches to be passing focus around like that.

Posted by dare2dreamer on April 24 2006,03:26

Also, in dsl-embedded, check the settings you used when you launched the qemu session. I just noticed on the version I downloaded from the DSL repositories I did not have an eth0 device by default. I'm sure there is a magic switch you have to throw somewhere to get networking going between the host and guest machine.

As a good friend of mine once said, "You ain't got a thing, if you ain't got ping."

Posted by dare2dreamer on April 24 2006,04:39

Definitely was the lack of networking that got you. I did a little reading up, and apparently qemu creates a ne2000 interface by default. For whatever reason, most operating systems can't see this interface until they are explicitly pointed at it.

The solution is the following:

sudo modprobe ne2k-pci
sudo pump
sudo ifconfig -a

After that, you'll see your eth0, have networking and nxclient should work without issues.

To automate this, I'd add it to a script or toss it in bootlocal.sh and create a backup on your usb key.

Post your results!