Hello, Petra. How about using a software for tunneling TCP connections over http proxy, e.g. http://www.taiyo.co.jp/~gotoh/ssh/connect.html?
Let's suppose you currently try to connect to customer1.dyndns.org:5800. I also suppose that you are connecting to Enterprise Edition VNC Server, serving both VNC and HTTP on port 5800. Download http://www.taiyo.co.jp/~gotoh/ssh/connect.exe and try the following example for MS Windows: Step 1: Execute "connect.exe -p 5800 -H your_http_proxy:proxy_port customer1.dyndns.org 5800" Step 2: Point your web browser to http://localhost:5800, or try "vncviewer localhost::5800". The solution will also work with VNC Free Edition, but requires different setup on the router, that forwards port 5800. In this case, you should also consider running VNC on top of SSH for better security. Best regards, Miro > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] > Sent: Friday, August 05, 2005 14:43 > To: [email protected] > Cc: [EMAIL PROTECTED] > Subject: RE: Java realVNC Viewer via HTTP-Proxy possible? > > Thanks Wez, > I know the restriction of the VNC Free Edition that was the > reason why we > give the Enterprise Edition 4.1.7 a try. But without HTTP > Tunneling it seams > to be that we have to go back and search for another > solution. Any Ideas ? > > How far are the plans with the HTTP tunneling? Reading the article of > http://www.ergotech.com/misc/VNCProxy.html it seams to be > quit easy (not for > me at all). > > Petra > > > > --- Urspr|ngliche Nachricht --- > > Von: "James Weatherall" <[EMAIL PROTECTED]> > > An: <[EMAIL PROTECTED]>, <[email protected]> > > Betreff: RE: Java realVNC Viewer via HTTP-Proxy possible? > > Datum: Fri, 5 Aug 2005 11:00:23 +0100 > > > > Petra, > > > > VNC Free Edition cannot serve both the VNC and HTTP > protocols on the same > > port number - this feature is currently available only in > the Enterprise > > and > > Personal editions. > > > > The VNC Viewer for Java requires that it be possible to > make a *direct* > > connection (i.e. not via a proxy) back to the server, on > the specified RFB > > port. Support for HTTP "tunnelling" may be added in future > but is not > > currently supported. > > > > Regards, > > > > Wez @ RealVNC Ltd. > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] > > > Sent: 05 August 2005 09:25 > > > To: [email protected] > > > Subject: Java realVNC Viewer via HTTP-Proxy possible? > > > > > > Hi everybody, > > > we test currently the remote administration of our customer > > > PCs from our > > > internal LAN and have still problems. Our security decided to > > > use only one > > > port 5800 for both Java an native viewer. To be flexible we > > > decided to use > > > first the Web-Interface of the realVNC Enterprise Version, > > > anyway with one > > > port for java and native viewer we are able to change > this anytime. > > > The communication starts on our internal clients, goes to the > > > http-proxy and > > > firewall to the internet. With dyndns we find the router, > > > that forwards the > > > port 5800 and come to the realVNC Server to administrate the > > > customer PC. > > > Our security is the opinion that there is no need to install > > > any firewall > > > rule for this connection because of the HTTP-Proxy. > > > > > > The current result is that we are able to connect to the > > > customer PC an see > > > the Website with realVNC Viewer Enterprise Edition 4.1.7 and > > > load the Java > > > applet. After entering the connection details we receive no > > > answer and get > > > the following exception: > > > java.net.NoRouteToHostException: Operation timed out > > > at java/net/PlainSocketImpl.socketConnect > > > at java/net/PlainSocketImpl.doConnect > > > at java/net/PlainSocketImpl.connectToAddress > > > at java/net/PlainSocketImpl.connect > > > at java/net/Socket.<init> > > > at java/net/Socket.<init> > > > at vncviewer/CConn.init > > > at vncviewer/VNCViewer.run > > > at java/lang/Thread.run > > > > > > Means this that the realVNC Viewer is not able to use the > > > HTTP-Proxy and we > > > need a additional firewall rule? > > > Any suggestions what we can change not to be bound to the > > > firewall rule that > > > our security currently doesn't want? > > > > > > Thanks for help! > > > Petra > > > > > > -- > > > 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail > > > +++ GMX - die erste Adresse f|r Mail, Message, More +++ > > > _______________________________________________ > > > VNC-List mailing list > > > [email protected] > > > To remove yourself from the list visit: > > > http://www.realvnc.com/mailman/listinfo/vnc-list > > > > > > > -- > 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail > +++ GMX - die erste Adresse f|r Mail, Message, More +++ > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
