You couldnt make a keyboard work through NX in 2 releases? (11/12) PATHETIC !!

[cuban_cigar]

In a local network, a connection with freenx conencts with the arrow keys working

In a remote system, arrow keys dont

any ideas

Fedora 12 look pretty good otherwise

[brunson]

I don't think anyone on this forum would have recommended Fedora for a production environment. Nearly every thread I've ever seen asking about the subject, the overwhelming response is Fedora for fun, Centos/RHEL for production. Yeah, you made a stupid decision.

As far as your existing problem, why not use VNC? NX is not a core Fedora technology, VNC is built into the gnome desktop. However, in my opinion, if have to adminsister a fleet of servers any competent system administrator would use ssh and the command line, and that's only if not automating the administration through scripts or some centralized management system like puppet.

[smr54]

Actually, Fedora's vnc client, tigervnc, is pretty bad with Windows hosts-it shows the mouse as a one pixel gif, which sometimes works, but often doesn't. I haven't been able to get NX working properly in Fedora in awhile, among other things, the docs were all wrong, last I looked, so just use the nomachines free version. On the other hand, I don't need more than 1 connection at a time.

[forkbomb]

Oh, yeah. The devs will definitely see this.

Also, +1 to SSH. If you need a GUI to administer servers so bad that NX not working drives you to fits, something's gravely wrong.

Hello,

I don't use a GUI when administering a machine remotely but you could try login in with ssh -Y and run this CLI to get a Xnested GUI:

startx -- /usr/bin/Xnest :3

You can also specify window geometry by adding something like this to the end of the command :

-geometry 1250x710

Notice that you can use sizes that are not supported by your monitor, so you can tweak the numbers to get the window size you want without issue.

Hope this Helps,

Ky