Who will be the first to post a how to, configuring freenx on ubuntu and a windows client?
Printable View
Who will be the first to post a how to, configuring freenx on ubuntu and a windows client?
I assumed that the Windows client would be the easy part! Unless, of course, you don't use a Nomachine key... Then, you're on your own to google for how to install keys & such.
hmn
after a
chmod 700 /home/.nx
chmod 700 /home/.nx/.ssh
chmod 700 /home/.nx/.ssh/*
everything worked
It should be noted that the packages on kanotix.com has been upgraded and FreeNX can't be installed according to the guide because the libnxcomp0 and libnxcompext0 packages on kanotix depends on libpng being >= 1.2.7 and Warty has only 1.2.5. So using the libpng in Hoary should solve this problem. You might want to update your guide with suitable changes so that more people can start using FreeNX.Quote:
Originally Posted by jdong
Tried to install freenx from aforementioned repos, and got error
Anyone know where I can get these?Quote:
freenx:
Depends: nxagent but it is not going to be installed
Depends: nxproxy but it is not going to be installed
hi there I have read this review and am somewhat confused!Quote:
Originally Posted by jdong
I need to access and control a windows xp computer (my dad's) and need to be able to give really simple instructions over the phone of how to set up the xp machine as the client.
Then I need simpler instructions - after installing nx how do I get it to work and connect to the xp machine.
The two computers both are on broadband.
Thanks for your help so far!
puzzledm, in that case you'll need to use VNC.
The FreeNX server will only work on computers using the X protocol, like Linux and Solaris.
There's client software for Windows, but not server software.
On Linux, there's both client and server software.
I get the same error.Quote:
Originally Posted by shoelessmike
I've packaged working freeNX in my warty-extras repository (see the Backports forum).
It's currently undergoing beta-testing in the -staging tree, I'll have it out of there by Jan 10th.
If you get a "Parse error in remote options string" type error message it could be because you have a space in the name of the session. I found this info in the mailing list linked. I could not connect the client to the server until I removed the space in the session name.
http://mail.kde.org/pipermail/freenx...er/000529.html
Edit: I find this to be faster and more flexible compared to VNC. TightVNC anyway, thats all I have used. but I'm wondering how i could use freenx instead of vnc for what I use it for. can you have a session start automaticly with a program running in it when the computer boots/reboots? so you can connect to it whenever you need it and its right there?