You are not logged in.

#1 2008-01-06 05:07:14

arew264
Member
From: Friendswood, Texas, US
Registered: 2006-07-01
Posts: 394
Website

VNC Network Terminal Issues

I finally tried to get my personal Holy Grail to work under Arch... and failed.

I've wanted for quite some time to have a setup where I can start a KDE session remotely. Ideally, I would pop up a VNC client somewhere on my home network, connect to the linux box, get a KDM login screen, and go.
I googled this for a while and started following my tradition of improvising on the guide given for a different distro.

I first installed tightvnc (pacman -S tightvnc)

I set up xinetd and added a VNC service to it, which looks like this:

service vnc-800x600x32
{
        type = UNLISTED
        disable = no
        socket_type = stream
        protocol = tcp
        wait = yes
        user = root
        server = /usr/bin/Xvnc
        server_args = -inetd :1 -query localhost -geometry 800x600 -depth 32 -once -DisconnectClients=0 -NeverShared 
        port = 5901
}

I set KDM's Xdmcp settings to this:

[Xdmcp]
Enable=true
Port=177
Xaccess=/opt/kde/share/config/kdm/Xaccess
Willing=/opt/kde/share/config/kdm/Xwilling

I then set the aforementioned Xaccess file to contain these settings:

*       #any network host can get a login window
*               CHOOSER BROADCAST       #any indirect host can get a chooser

I think that was all I did. It feels like I did more, but I guess I was just playing with it for quite some time.

I rebooted xinetd and KDM, and away I went, or so I thought.
After that was set, I fired up a neighboring Windows box (sorry, some of us have family members who are slow to adopt anything new), installed RealVNC, and told it to connect to [My IP]:1
Nothing. Connection refused.
I then tried [My IP]:5901
Connection refused again.

I do use IPtables, but it is set to allow everything within the local network.
I can see in the logs that xinetd is loading my service and shows it as available, and when I connect, the log prints this:

Jan  5 23:01:53 Lagbox xinetd[12523]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12525]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12527]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12529]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12531]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12533]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12535]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12537]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12539]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12541]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12543]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12545]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12547]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12549]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12551]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12553]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12555]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12557]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12559]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12561]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12563]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12565]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12567]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12569]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12571]: warning: can't get client address: Transport endpoint is not connected
Jan  5 23:01:53 Lagbox xinetd[12521]: Deactivating service vnc-800x600x32 due to excessive incoming connections.  Restarting in 30 seconds.
Jan  5 23:02:23 Lagbox xinetd[12521]: Activating service vnc-800x600x32

As you can see, it starts the service back up after 30 seconds.

I can't find any output from Xvnc, am I calling it wrong somehow? Does that error mean the client connection is screwed up? Should I try a different client?

Last edited by arew264 (2008-01-06 05:08:48)

Offline

#2 2008-01-06 05:13:30

arew264
Member
From: Friendswood, Texas, US
Registered: 2006-07-01
Posts: 394
Website

Re: VNC Network Terminal Issues

I just tried again with tightvnc on windows and got the same result; something is definitely wrong server-side. But what?

Last edited by arew264 (2008-01-06 05:13:43)

Offline

#3 2008-01-06 05:31:08

arew264
Member
From: Friendswood, Texas, US
Registered: 2006-07-01
Posts: 394
Website

Re: VNC Network Terminal Issues

Okay, I have at least one thing working. I can start Xvnc independently and connect to it from localhost using this:

sudo Xvnc :2 -query localhost -once -geometry 640x480 -depth 8 -fp /usr/share/fonts/misc/,/usr/share/fonts/75dpi/,/usr/share/fonts/100dpi/,/usr/share/fonts/Type1/

Everything behaves exactly as it should, I see the KDM login screen and can log in to my KDE desktop.

With some extrapolation, the service file becomes this:

service vnc-800x600x32
{
        type = UNLISTED
        disable = no
        socket_type = stream
        protocol = tcp
        wait = yes
        user = root
        server = /usr/bin/Xvnc
        server_args = -inetd -query localhost -once -geometry 800x600 -depth 32 -fp /usr/share/fonts/misc/,/usr/share/fonts/75dpi/,/usr/share/fonts/100dpi/$
        port = 5901
}

I still have the same issue though, what would be keeping Xvnc from loading from Xinetd?

Last edited by arew264 (2008-01-06 05:42:44)

Offline

#4 2008-01-06 17:25:36

arew264
Member
From: Friendswood, Texas, US
Registered: 2006-07-01
Posts: 394
Website

Re: VNC Network Terminal Issues

Okay, I have VNC working as it should. I ended up adding the "vnc" service to /etc/services and updating the service file to look like this:

service vnc
{
        protocol = tcp
        socket_type = stream
        wait = no
        user = nobody
        server = /usr/bin/Xvnc
        server_args = :50 -inetd -query localhost -once -geometry 1024x768 -depth 32 -fp /usr/share/fonts/misc/,/usr/share/fonts/75dpi/,/usr/share/fonts/100dpi/,/usr/share/fonts/Type1/
}

Now the issue is getting audio somehow. If someone knows of a better server that supports audio, I would love to hear about it, but unless there's a better solution, I'm going to try pulseaudio.

Offline

Board footer

Powered by FluxBB