Hi,

I access my Linux systems remotely from a Mac running OS X and Chicken of the VNC. Up until now using VNC and the vncserver from RealVNC has worked well. With KDE4 using this setup the output in the viewer window is no longer legible, and some text is missing completely. This is also true if I run vncviewer on another Linux system.

I have tried using x11vnc and the output looks good but the lag is horrible.

I have tried using the remote desktop sharing feature of KDE4 but the result is a distorted view with malformed windows and random blotches of colour.

I'm looking for other alternatives to try or suggestions that might improve upon what I have already tried.

Thanks,
Randy

This is a known problem with the KDE4 desktop at the moment. I do believe the developers are working toward making remote access a better experience though.

You could try NoMachines' NX to access the machine. This may provide some better results than VNC.

Thanks for the suggestion. I'll look into it.

Randy

I've been trying to get the nomachine NX to work without any success. I did a default installation of the server and client. When I try to connect from the client to the server I get an authentication error. From the messages in the log it looks like the nx user is failing to authenticate. I have ssh set up so that only public key access is supported, would this be a problem?

Here's what the log shows:

Jul 23 13:12:36 galactic sshd[5070]: Accepted publickey for nx from 192.168.1.32 port 50533 ssh2
Jul 23 13:12:36 galactic NXSERVER-3.3.0-22[5073]: ERROR: Failed authentication. NXSsh exit status is:255 'NXNssUserManager::auth'
Jul 23 13:12:36 galactic NXSERVER-3.3.0-22[5073]: Failed SSHd authentication for user 'xxcooper', to '127.0.0.1', port '22': 'NX> 204 Authentication failed.\n ' 'NXNssUserManager::auth'
Jul 23 13:12:36 galactic NXSERVER-3.3.0-22[5073]: ERROR: Error while trying to authenticate user:xxcooper. NXNssUserManager::auth returned 255 'NXShell::handler_login'
Jul 23 13:12:36 galactic NXSERVER-3.3.0-22[5073]: ERROR: failed 'sshd authentication' for user 'xxcooper' from '192.168.1.32'. NXShell::handler_login NXShell 373

Any suggestions?

Thanks,
Randy

From memory, I believe that only "normal" sign on is supported.

Try searching the FAQs on the nomachine web site.

I "think" this can be overcome, by using the "internal" NX authentication, instead of the local system authentication.

Cheers.

**Update**

I found my old server config file. Update it to use both the UserDB and PasswordDB.

Cheers.

Thanks for your reply.

I decided to try an unmodified sshd_config file (i.e. one that didn't require public keys) and that worked. I was able to establish a connection. However, I have gibberish on the screen. For example the clock appears to be a random set of pixels. Window frames and other structure appears OK but the text is gibberish as well, again it appears to be random pixels, this includes menu names, text entered and in a terminal window the responses to that text as well.

Not sure what to do now.

Again, any suggestions are appreciated.

Thanks,
Randy