From: Joe Freeman (joe.freeman@CenturyTel.com)
Date: Mon Feb 14 2005 - 19:53:18 GMT-3
You might run into problems using VNC. Even though you can connect and
load the java client using a web browser, the java client still
communicates using the same ports as the VNC client (5800/5900). I had
problems with this for awhile.
My solution ended up being rather slow, but effective. I can ssh from
inside the corporate network out, so I run a vnc session inside a ssh
tunnel. My box at work runs an X-server, so I simply have to start the
vnc session on my linux box at home, and point the output down the ssh
pipe to my box here. Makes for a nice encrypted session, but it is slow.
HTH-
Joe
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
John Aitken
Sent: Monday, February 14, 2005 4:29 PM
To: ccielab@groupstudy.com
Subject: Re: Remotely Accesing Lab
Some great suggestions there guys, much appreciated - I'm thinking the
VNC through the browser looks simplest & cheapest (Got it working
between machines at home easily already).
If I only allow port 80 through firewall, restricting source networks
and using authentication plus strengthing local security that should
be secure enough?
On Mon, 14 Feb 2005 15:05:39 -0500, 22Cent@gmail.com <22cent@gmail.com>
wrote:
> Hey John,
> Here is another option. IF you have a spare computer ( 486 will do
> fine with 2 NIC cards) go to www.ipcop.org and download and install
> it. Its linux but has an easy to use web interface to port forward.
> Lots of features. Hope this helps.
>
>
> On Mon, 14 Feb 2005 20:31:34 +0100, Daniel Sheedy
<dansheedy@gmail.com> wrote:
> > Hi there John,
> >
> > I don't know what type of licenses you have available to you, but if
you set
> > up a terminal server at home, you can use the old 'microsoft
terminal client
> > in a web page' trick...
> >
> > Should do the trick hey? You only need to use port 80, and you can
gain
> > access to a desktop, or publish an app, such as telnet on the
server.
> >
> > Dan
> >
> >
> > ----- Original Message -----
> > From: "John Aitken" <john.aitken@gmail.com>
> > To: <ccielab@groupstudy.com>
> > Sent: Monday, February 14, 2005 6:04 PM
> > Subject: Remotely Accesing Lab
> >
> > > Hi folks,
> > >
> > > Wondering if anyone can come up with some suggestions to help me
get
> > > round a home lab access problem I'm facing.
> > >
> > > I'd like to access my home lab, from work, during the quiet
periods.
> > > However the company policy where I'm at only allows http/https
traffic
> > > via a proxy (Ie. No telnet, or telneting on 80 and NAT'ing at my
home
> > > end).
> > >
> > > I'm thinking maybe a webserver running some sort of telnet locally
at
> > > home which I can access via http and then to my access router.
> > >
> > > But I'm open to any better ideas, or even recommendations on a
> > > solution I can implement with minimal outlay.
> > >
> > > Your help is very much appreciated.
> > >
> > > John
> > >
> > >
This archive was generated by hypermail 2.1.4 : Thu Mar 03 2005 - 08:51:20 GMT-3