Hi Felix, If proxychains is supposed to "socksify" standard TCP-based applications but doesn't work with vncviewer, then your best bet is to report the problem to the proxychains developers.
Cheers, Wez @ RealVNC Ltd. > -----Original Message----- > From: Felix E. Klee [mailto:[EMAIL PROTECTED] > Sent: 09 May 2006 13:18 > To: James Weatherall > Cc: [email protected] > Subject: Re: socksifying vncviewer fails > > On Tuesday 09 May 2006 13:28, you wrote: > > What are you expecting those commands to do? > > > > The first opens an SSH connection to a machine and > listenings for SOCKS4 or > > SOCKS5 connections to port 1080 on the client side. What > is the second > > intended to do? > > It should automagically tunnel a VNC session to port 5902 on > host 192.168.3.43 > in the remote network. Note that with "krdc" commands such as > > proxychains krdc 192.168.3.43:2 > > *do* work. However, krdc has stability problems, at least > the version that > we're employing. > > Also, tools such as "ssh" and even "nxclient" do work with > "proxychains". > > -- > Dipl.-Phys. Felix E. Klee > Email: [EMAIL PROTECTED] (work), [EMAIL PROTECTED] (home) > Tel: +49 721 8307937, Fax: +49 721 8307936 > Linuxburg, Goethestr. 15a, 76135 Karlsruhe, Germany _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
