#64 Connecting to a inetd started server fails

v1.3.6
closed-wont-fix
Jason Harris
Networking (54)
5
2004-08-18
2004-08-11
Gerard Hickey
No

When attempting to connect to a VNC server that is
started by inetd/xinetd receive a "Connection refused:
connect()" dialog box. There is not an issue connecting
to the same display with other VNC clients.

The VNC servers are configured to receive incoming
connections on port 50-52 (three different resolutions)
and present a XDM logon screen. In this mode, a
password is not required and so all connections are
initiated in an unauthenticated state and XDM provides
the authentication mechanism.

The following is a copy of the xinetd file for the VNC
service on port 5951 (display 51) so that you may
recreate the environment if needed. Note, XDM (GDM,
KDM, etc.) still needs to be configured to make this work.

service vnc51
{
disable = no
socket_type = stream
wait = no
user = root
server = /cte/local/linux-2-i386/bin/Xvnc
server_args = -inetd -query jhadur -once
-geometry 1024x768 -depth 24
log_on_failure += USERID
}

Discussion

  • Jason Harris
    Jason Harris
    2004-08-18

    • assigned_to: nobody --> smeger
    • status: open --> closed-wont-fix
     
  • Jason Harris
    Jason Harris
    2004-08-18

    Logged In: YES
    user_id=351330

    Chicken interprets display numbers less than 100 as port numbers, so
    you'll need to enter the port number explicitly as 5951.

    Not a bug, but not the clearest thing in the world, either.

     
  • Gerard Hickey
    Gerard Hickey
    2004-08-18

    Logged In: YES
    user_id=25757

    OK. Entering 5951 does work. It seems to be more rational
    that numbers below 1024 (because of the reserved ports)
    would be display numbers (or at least below 100) and
    anything above would be ports. Just seems to be reverse logic.

     
  • Jason Harris
    Jason Harris
    2004-08-18

    Logged In: YES
    user_id=351330

    Whoops, sorry, that's what I meant to say. Numbers below 100 are
    interpreted as display numbers, numbers above are interpreted as ports.

    It used to be 10, not 100. Since your number 52 didn't work, maybe that
    change got lost in the transition to the new connection manager. I'll
    check this.

     
  • Jason Harris
    Jason Harris
    2004-08-18

    Logged In: YES
    user_id=351330

    Just to clarify, it is indeed 100 in Chicken 2.0b1 and 10 in Chicken 1.3.6.