Trouble Hooking Windows NX Client to Linux FreeNX Server
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Trouble Hooking Windows NX Client to Linux FreeNX Server
I'm trying to connect the nxclient 2.0 program for Windows 2000 that I got from nomachine.com with the FreeNX 1.4 server for Ubuntu.
On the Windows 2000 desktop, I use the client program to try and connect to the server. I enter my username and password. If I enter either of these incorrectly, there is an authentication error, so I know the two machines are definitely talking. The progress dialog tells me that it manages to connect and start an X session... and then the dialog box disappears... but doesn't leave me with any visible results (an X session, for example).
Under the NX Session Admin program, I can see that there is indeed a session registered and running on the Windows client. The log file for this session always looks like so:
Quote:
Info: Display running with pid '1172' and handler '0x2a031e'.
NXPROXY - Version 2.0.0
Info: Proxy running in client mode with pid '2052'.
Session: Starting session at 'Fri Jun 30 14:00:36 2006'.
Warning: Connected to remote NXPROXY version 1.5.0 with local version 2.0.0.
Info: Synchronizing local and remote caches.
Info: Handshaking with remote proxy completed.
Warning: Font server connections not supported by the remote proxy.
Info: Using lan link parameters 1536/24/1/0.
Info: Using image streaming parameters 50/128/1024KB/6144/768.
Info: Using pack method '16m-jpeg-9' with session 'unix-kde'.
Info: Not using NX delta compression.
Info: Not using ZLIB data compression.
Info: Not using ZLIB stream compression.
Info: Not using persistent cache.
Session: Session started at 'Fri Jun 30 14:00:37 2006'.
Warning: Cookie mismatch in the authentication data.
According to all of my Google results, that last warning doesn't mean anything relevant.
On the Linux box, I can find zero log files. /var/log/nxserver.log is there, but it's empty. I can find no evidence that the FreeNX server running there is even aware of any connections being made.
Googling reveals surprisingly little. I'm really at a loss! Does anyone know what might be wrong? Does anyone have any ideas as to what else I could do to try and figure this out?
Thanks in advance, even if only for reading my post!
I'm running into basically the same issue; Haven't really found anything useful online.
Maybe if we compare notes we might come up with something. Do you see anything like the following in your winlog?
error opening security policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy
(EE) No primary keyboard configured
(==) Using compiletime defaults for keyboard
names.keymap=(null)Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(null)"
Couldn't load XKB keymap, falling back to pre-XKB keymap
_FontTransOpen: Unable to Parse address "/mnt/NX/fonts/TTF
Could not init font path element "/mnt/NX/fonts/TTF, removing from list!
Could not init font path element /mnt/NX/fonts/misc, removing from list!
Could not init font path element /mnt/NX/fonts/Speedo, removing from list!
Could not init font path element /mnt/NX/fonts/Type1, removing from list!
Could not init font path element /mnt/NX/fonts/75dpi, removing from list!
Could not init font path element /mnt/NX/fonts/100dpi, removing from list!
Could not init font path element /cygdrive/c/Program Files/NX Client for Windows/usr/X11R6/lib/X11/fonts/TTF, removing from list!
Could not init font path element /cygdrive/c/Program Files/NX Client for Windows/usr/X11R6/lib/X11/fonts/base, removing from list!
Could not init font path element /cygdrive/c/Program Files/NX Client for Windows/usr/X11R6/lib/X11/fonts/misc, removing from list!
Could not init font path element /cygdrive/c/Program Files/NX Client for Windows/usr/X11R6/lib/X11/fonts/Speedo, removing from list!
Could not init font path element /cygdrive/c/Program Files/NX Client for Windows/usr/X11R6/lib/X11/fonts/Type1, removing from list!
Could not init font path element /cygdrive/c/Program Files/NX Client for Windows/usr/X11R6/lib/X11/fonts/75dpi, removing from list!
Could not init font path element /cygdrive/c/Program Files/NX Client for Windows/usr/X11R6/lib/X11/fonts/100dpi, removing from list!
winBlockHandler - Releasing pmServerStarted
winBlockHandler - pthread_mutex_unlock () returned
Last edited by jmeadows111; 07-03-2006 at 02:58 PM.
I've discovered that using the client and server provided by nomachine.com, I can use the Linux machine to remote in to... itself. It's VERY low latency when the entire network is confined to the loopback device :-)
Still no luck with running from the remote Windows client. I wish I had another Linux machine in this building so I could test and see if it's just this machine / OS / client...
I did two things on the Ubuntu machine, and now it all works.
First, I ran "xhost +" from the machine locally (not via ssh but in front of the actual machine) to enable remote display. Not sure this was necessary, but I did it, so I'm mentioning it.
Second, I went to nomachine.com and downloaded the client, node and server packages- all three of them are necessary to have installed *on the server*. I don't know why, and it's very counter-intuitive, but there you go, right?
Absolutely beautiful. Drop shadows work, my funky mouse button order is preserved, it's great!
Let me know if you need any further help, jmeadows111 (or anyone else).
I'm trying to connect the nxclient 2.0 program for Windows 2000 that I got from nomachine.com with the FreeNX 1.4 server for Ubuntu.
On the Windows 2000 desktop, I use the client program to try and connect to the server. I enter my username and password. If I enter either of these incorrectly, there is an authentication error, so I know the two machines are definitely talking. The progress dialog tells me that it manages to connect and start an X session... and then the dialog box disappears... but doesn't leave me with any visible results (an X session, for example).
Under the NX Session Admin program, I can see that there is indeed a session registered and running on the Windows client. The log file for this session always looks like so:
According to all of my Google results, that last warning doesn't mean anything relevant.
On the Linux box, I can find zero log files. /var/log/nxserver.log is there, but it's empty. I can find no evidence that the FreeNX server running there is even aware of any connections being made.
Googling reveals surprisingly little. I'm really at a loss! Does anyone know what might be wrong? Does anyone have any ideas as to what else I could do to try and figure this out?
Thanks in advance, even if only for reading my post!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
