RE: Windows Client to Debian TightVCN server active denial

[Bob M. <rvm@CBORD.com>]

Mike,

It's best to keep conversations on the list, so my mistakes misunderstandings can be seen and corrected.

I haven't tried recent versions of the TightVNC server on Linux, but the versions I did test would not attach the console session. They always open a secondary session which you cannot see from the console. I used a different server, I believe it was x11vnc, on my Slackware workstations so I could connect to the console (desktop:0).

Bob McConnell

> -----Original Message-----
> From: Mike Lieberman [mailto:mi...@ne...]
> Sent: Friday, September 21, 2012 12:14 PM
> To: Bob McConnell
> Subject: RE: Windows Client to Debian TightVCN server active denial
> 
> Thanks that helped... I now get a connection on the server side... but no
> local window opens up on the workstation!
> 
> -----Original Message-----
> From: Bob McConnell [mailto:rvm@CBORD.com]
> Sent: Friday, September 21, 2012 8:55 AM
> To: VNC...@li...
> Subject: Spam:*****, RE: Windows Client to Debian TightVCN server active
> denial
> 
> 
> From: Mike Lieberman
> >
> > I have installed tightvcn server on a Debian server, supposedly
> successfully.
> >
> > I have installed tightvcn viewer on a Windows 7 workstation.
> >
> > I can run Windows RDP (it's flaky but it works) from the Windows computer
> to the Debian Server.
> > BUT
> > When I run tightvcn viewer I get the message that the connection failed
> because the server 'actively refused it.'
> >
> > How can I tease out why it was actively refused. There are no ACL's
> between the two computers.
> 
> What TCP ports are open on the server, and which port is the viewer trying
> to connect with?
> 
> netstat or lsof will tell you the former, you may need Wireshark to find the
> latter.
> 
> Bob McConnell