Hello, Mark. The idea is great! However, I am surprised it works if the central machine really does not route.
I thought that the browser would only download the java vncviewer from port 5800, and then the java vncviewer connects directly to port 5900 on the VNC server. Wez @ RealVNC, isn't java vncviewer working this way? Is it connecting to the VNC Server directly or via the http proxy? Mark, are you sure the central machine does not route? On your local desktop on the company network, try to telnet to port 5900 on a VNC server on the local network to see whether you don't get a response. Merry Christmas and Happy New Year, Miro > -----Original Message----- > From: Mark Ceulemans [mailto:[EMAIL PROTECTED] > Sent: Friday, December 23, 2005 16:01 > To: Luptak, Miroslav > Cc: [email protected] > Subject: Re: vnc proxy > > Wow, thanks. > The problem is that there are many machines in the second cloud, and > this means opening a port for every single machine in this cloud. > > I also found a simple workaround. > > 1. On the central machine, install FreeProxy (a simple HTML proxy > server), and have it reroute requests from NIC1 to machines > in the local > network > > 2. on your local desktop, install ProxySwitcher (a proxy switching > tool), and define a proxy for the central machine. > > 3. From your browser, connect to the ipaddress in the local > subnet, and > this request will be routed via the central machine to the manager. > (connect to the port 5800). > > This works fine (as far as I can see) > > Thanks for your support, > > Cheers, > > I also > Luptak, Miroslav wrote: > > >Hello, Mark. > > > >You don't need a special VNC proxy. Any TCP forwarder will do, try > >rinetd from http://www.boutell.com/rinetd. > > > >Here is how it could work: > > > >1. let's suppose this: > > - Nic1 on the Windows Server is 192.168.1.1 > > - vncviewer will be running on a host on the {company network} > > - you want to open a VNC session to a server on the > {local network} > > with IP 10.10.10.10 and VNC Server running on the default port > > > >2. on the Windws Server, create rinetd.ini containing the following > >line: > >192.168.1.1 5901 10.10.10.10 5900 > > > >3. on the Windows server execute "rinetd.exe -c rinetd.ini" > > > >4. on any machine on the {company network}, execute "vncviewer > >192.168.1.1:1". > > This will connect you to the VNC Server on machine 10.10.10.10 on > >the > > {local network} > > > >Best regards, > > > >Miro > > > > > > > >>-----Original Message----- > >>From: [EMAIL PROTECTED] > >>[mailto:[EMAIL PROTECTED] On Behalf Of Mark Ceulemans > >>Sent: Friday, December 23, 2005 09:07 > >>To: [email protected] > >>Subject: vnc proxy > >> > >> Hi All, > >> I am trying to setup a rather complex environment. > >> { company network }<-> tcpip< -> ( Nic1 Windows > >>Server Nic2) <-> > >> tcpip <-> { local network } > >> The server in the middle has 2 network cards (with no > >>routing). The > >> local network is in a local tcpip range (f.e. 10.x addresses). > >> Now, I want from within the company network to open a > >>session to a > >> machine in the local network. > >> Can this be done? > >> Is there f.e. a vnc proxy that can reroute the vnc > >>request from a > >> server within the company network to a machine in the > >>local network? > >> Any help will be greatly appreciated. > >> Cheers, > >> -- > >>Kind regards, > >>Mark Ceulemans > >>_______________________________________________ > >>VNC-List mailing list > >>[email protected] > >>To remove yourself from the list visit: > >>http://www.realvnc.com/mailman/listinfo/vnc-list > >> > >> > >> > > > > > > > > > > > -- > Kind regards, > Mark Ceulemans _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
