tightvnc: "Network error: remote side closed connection"

KShots · Guru Joined: 09 Oct 2003 Posts: 595 Location: Florida

I get the above when I tunnel into my vnc server via the java interface.

I point my web browser to the server's IP on port 5800 (tightvnc running on :0), enter my password in the authentication dialog, then I get the message in the title along with a "login again" button.

My config:

net-misc/tightvnc-1.2.9-r3

~/.vnc/xstartup:

KShots · Guru Joined: 09 Oct 2003 Posts: 595 Location: Florida

Well, emerging xorg-server changed nothing. I'm still unable to run a vnc session.
_________________
Life without passion is death in disguise

KShots · Guru Joined: 09 Oct 2003 Posts: 595 Location: Florida

It's been a while. I'm still looking to solve this, though I've had to re-install the machine because it was diskless and the server went belly-up.

As I've said, emerging xorg-server didn't solve the problem, so I haven't bothered. Here's the new environment:

net-misc/tightvnc-1.3.8-r1

relevant USE flags: java server tcpd

connection port: 5801 via web browser

log file:

Hu · Administrator Joined: 06 Mar 2007 Posts: 23066

If you use a full VNC viewer, instead of the Java applet, does it work? What does a tcpdump (from net-analyzer/tcpdump) on the VNC server show happening during the time that you connect from your client? You can use net-analyzer/wireshark to view the pcap file in a GUI. Have you considered using a different VNC server, such as net-misc/vnc (which unfortunately conflicts with net-misc/tightvnc, so you can only have one installed at a time)?

Can you avoid VNC entirely, and instead use X11 forwarding to display the contents elsewhere? To do this, configure sshd on the MythTV box to allow X11 forwarding (see the sshd_config manpage), then on your client machine, run ssh -X medusa. When the prompt comes up, you should be able to start an X11 application and have it display on the machine from which the ssh connection originated. Both ssh and sshd are part of net-misc/openssh. The X11 application is running on medusa, so it should be just as effective as using VNC.

KShots · Guru Joined: 09 Oct 2003 Posts: 595 Location: Florida

Well, I found something interesting. Here's more detail.

To get to madusa, I am tunneling from outside of my network, connecting to the tunnel via localhost:5801 (which goes through the tunnel and gets sent to madusa:5801 on the ssh server side - also has the side effect of encrypting the authentication)

This fails. However, I have another host on the same network configured as an actual desktop, which I have configured another tunnel to go to 5802 (localhost:5802 points to basilisk:5802 on the server side of the tunnel)). This works fine... and the REALLY weird thing is that I can then connect to madusa:5801 from the web client on basilisk successfully and run mythtv-setup, which then segfaults under VNC, but not locally after I finally threw my hands in the air and hauled a monitor over to the thing, compiled xorg-x11 and xorg-server (which were not installed) along with some vesa drivers, typed "startx", then tried REAL hard to look at things on an ancient 15 year old standard VGA that just "technically" supported the resolution that was being used and did so with serious contrast issues (very dark).

Anyways... long story cut short, the machine has now been configured and I no longer need X. I'm hesitant to unmerge it because I'm not sure which pieces Qt must tie into for the mythbackend, and as long as it's not called it's not really slowing me down either.
_________________
Life without passion is death in disguise