Any Old Port In A Storm? <g>
kzinti "at" gmail.com
Sun Jul 18 05:37:00 2004
I have a similar problem with my employer. I use SSH to establish a
connection from my office workstation to my linux machine at home. I
then forward a port, using ~C to break into the SSH command mode, then
issue a -L 5900:bexpoz:5900, where bexpoz is the name of my Windows
PC. (The hostname is interpreted on the remote side of the connection,
so the hostname need not be a fully qualified name.) Once the port is
forwarded, I can connect to localhost:0, but in reality I'm connecting
across the Internet to my PC.
Our firewall people recently locked down their setup, allowing only a
few poirts like 80 (HTTP) and 443 (HTTPS) to go out. I just changed my
SSH daemon to list on 443, and I still get through.
Our security people would freak out if they knew what could be done
with SSH and port forwarding.
On Sat, 17 Jul 2004 18:51:21 -0700, Jerry Moore <jerryamoore "at" cox.net> wrote:
> I've been using VNC for several years with great success. I run the
> server software on my Home PC and use the viewer software on both my
> Office PC and PocketPC to access the Home PC. Recently the viewer
> software stopped working on my Office PC. I suspect my employer has
> tightened security and closed more ports. I can still access my Home PC
> from the office via a web browser, but not with VNC Viewer. Does anyone
> know if there is a way to modify this software so it can make a
> connection between my Office PC and Home PC using ports that have not
> been closed?
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: