Problems with FreeNX to VNC

I am able to use the NoMachine Mac OS X nxclient to connect to FreeNX on my Linux box and it’s fantastic!

I can’t however get FreeNX to reliably proxy to a TightVNC server on our Windows XP laptop. It pretty much always times out.

cat /home/Marc/.nx/T-C-tbird-1003-309AA9190583314C6E14CADAD449AFBC/session

Info: Proxy running in server mode with pid '15932'.
Info: Waiting for connection from '127.0.0.1' on port '5003'.
Info: Accepted connection from '127.0.0.1' on port '53755'.
Info: Connection with remote proxy established.
Info: Aborting the procedure due to signal '15', 'SIGTERM'.
X connection to nx,options=/home/Marc/.nx/C-tbird-1003-309AA9190583314C6E14CADAD449AFBC/options:1003.0 broken (explicit kill or server shutdown).

7 thoughts on “Problems with FreeNX to VNC

  1. Of course right after posting this, I got it to work, but only once and X11.app did not seem to like the encoding as the image has a yellowish tinge to it – something which in my experience is fixed by switching from the tight or hextile encodings to zlib or raw.

    It only worked once. I’ve tried a bunch of times since and it keeps timing out.

  2. I presume you’re on a PowerPC mac. I can’t use NX because I’ve got an intel mac.

    Do you know any solutions for us bleeding-edge-eager Intel mac people?

  3. Me again. The PPC NX client works fine on intel macs. Guess I just didn’t have the X11 working or something on my first attempt. Can’t remember what went wrong to be honest but it works now.

  4. Hi, do you have a link to a howto setting up a tunnel like this?

    I am in the same boat, but can’t find any help. thanks!

  5. Hi –

    I just tried to do about the same thing and learned that you have to have an nx server on the distant end, whether you’re running vnc or not. You can’t just have vnc by itself. And it looks like there’s no nx server for windows, which makes sense in retrospect, since it’s all about X-Window system after all.

    HTH —

    dave

Leave a Reply

Your email address will not be published. Required fields are marked *