DSL Embedded :: NX Client in DSL Embedded?
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.
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.
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."
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!
original here.