vnc: I can't monitor my thinclient: connection refused

[ekkard gerlach]

I can't monitor my thincClient PC, it's a Itona VXL from Sphinx. I make
XDMCP to the Server and I'm running KDE. The desktop is given free for
remote access, but I always get: connection refused when trying
vncviewer localhost:1.

When I exchange the Itona with a old standard PC with SuseLinux8.2
installed on and log in as same user, I've no problems to access the KDE
desktop. It works.

I think I haven't understood all concerning X. The X on the standard PC
is perhaps the reason why it works and the X or whatever is realised in
the Itona box denys remote access .. ... , right?
What has to be configured with the Itona ThinClient that remote access
to the desktop is possible?
I remember "remote frame buffer" ... hmmmm ... is vnc monitoring
hardware dependant? Perhaps the X-System of the itona has to provide a
interface to read data from the frame buffer of the graphics card?
But why is a vnc session started on e.g. "localhost:1" and not on the
clients IP?

tia
Ekkard

[ekkard gerlach]

ekkard gerlach wrote:
> I can't monitor my thincClient PC, it's a Itona VXL from Sphinx. I make
> XDMCP to the Server and I'm running KDE. The desktop is given free for
> remote access, but I always get: connection refused when trying
> vncviewer localhost:1.

solution: the firmware of itona allows a entry for xhost. Put the IP of
the server in.

Ekkard