RE: VNC, KDE and XDMCP - more acronyms inside !----- Original Message -----
From: Beerse, Corni
To: 'Matthew J. Salerno'
Sent: Monday, January 13, 2003 4:07 AM
Subject: RE: VNC, KDE and XDMCP - more acronyms inside !

Saw one more thing, see below:

> From: Matthew J. Salerno [mailto:[EMAIL PROTECTED]]
> Sent: zondag 12 januari 2003 18:19
>
> I am trying to configure my gentoo linux server so that I can remoely
> connect with a vnc client and see the entire desktop.  I have
> done this in
> the past, but I must be missing something.  I would really
> really appreciate
> any help anyone can offer.
<cut>
>
> {
>         disable = no
>         port = 5901
>         socket_type = stream
>         wait  = no
>         user = root
>         instances = 5
>         server = /usr/local/bin/Xvnc
>         server_args   = -inetd -query localhost -once -geometry
> 1024x768 -depth 8
>         log_on_failure += USERID HOST
Don't let inetd or xinetd handle the security until you have a successfull
setup. Once it works, you can add this security and know problems are to
blame on it.
> }
>
> Restart xinetd, xdm, kdn and usually I am ready to connect.
>
> Well, when restarting the xinetd service, it shows me that it
> started my vnc
> entry.
It should not. It only starts vncserver once you connect. If you already
have a vncserver running at this point, it is not started by xinetd and it
will cause problems.
Btw: if you do a `netstat -a`, you will see the running vnc sessions do not
run at the origional port. That's how xinetd works.
> When I scan UDP 177, XDMCP is running.
> But when I try to connect, all I get is the following enrty
> in the syslog:
>
> Jan 12 01:00:39 [xinetd] START: vnc pid=24377 from=192.168.0.2
> Jan 12 01:00:39 [xinetd] FAIL: vnc address from=192.168.0.2
>
> I cannot find a further explanation of what is going on. I's
> a very very
> vague error message.
>

Thanks for the link and the help, unfortunately I am still having the same
problem.  That link would have been perfect if it worked for me.  Here is
what I did, step-for-step.

Thanks again.

Matt

1. Edit xdm-config
- The last line now reads: ! DisplayManager.requestPort:   0

2. Edit 'kdmrc' and enable XDMCP
- the top of the XDMCP section of the kdmrc now reads.
[Xdmcp]
Enable=true

- It does not ask for a port.

4. Edit Xaccess enabel access
- Done, line reads:  *       #any host

5. Update the /etc/services
- Done:  vnc             5950/tcp

6. Update xinetd configuration
Done - Taken directly from
http://www.sourcecodecorner.com/articles/vnc/linux.asp#vncserver.xinetd

Rebooted
Same error in the /var/log/messages:
Jan 13 10:38:42 [xinetd] START: vnc pid=1734 from=192.168.0.2
Jan 13 10:38:42 [xinetd] FAIL: vnc address from=192.168.0.2

I wish I knew what it means.
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to