Connecting from work to home

[Scott C. Best]

Nick:
	Heya. Here's the best post I've seen on list answering
that question...

|Date: Mon, 28 Jan 2002 18:10:34 -0500
|From: Michael Milette <tng "at" cyberus.ca>
|Subject: Re: VNC with another port than 5900
|
|To calculate the port number Casper, simply use the appropriate formula
|below:
|
|To select a port number higher than 5900:
|
|         Display Number = [desired port number] - 5900
|
|To select a port number lower than 5900:
|
|         Display Number = [desired port number] - 5900 + 65536
|
|So in the case where you want to use port number 3030, you will want to
|use "Display number" 62666 on both the server and the client as
|calculated using the second formula above:
|
|         62666 = 3030 - 5900 + 65536.
|
|                                 Michael

	Hope this works for you!

-Scott

> Thanks for that information.  However, when I try to type in "-5820" in my
> display number field, it won't accept the "-".  Is this correct?  How can
> I set VNC to run on port 80 if it won't take the negative number?
>
> Thanks again,
> Nick
>
>
> Nick:
>                  Heya. Sorry for the late reply. Most firewalls that a
> company would use come "out of box" with only a handful of
> external services reachable. That is, the firewalls will allow
> anyone to connect to FTP, Telnet, HTTP, HTTPS and SMTP. That's
> about it. For example, an "ICSA approved" firewall:
>
> http://www.icsalabs.com/html/communities/firewalls/certification/criteria/criteria_3.0a.shtml
>
>                  Anyhow. As you'll noticed in the above, the actual
> *content* of the data connection is not a requirement for most
> firewall ceritifications, nor is content-based filtering a
> capability of most firewalls, either. So, I'm betting that
> the firewall at your work allows anyone to connect to any
> server that's listening on the default ports of FTP, Telnet,
> etc, etc.
>                  My suggestion, then, is to trick your workplace firewall
> by changing the mapping of your LinkSys box. So, have port-80
> (which is the default for HTTP servers) on the outside of your
> LinkSys box go to port 5900 of your home-LAN VNC machine. Then,
> from work, "telnet a.b.c.d 80" and see if it connects. If it
> does, then you can get the VNC viewer to connect as well. I'm
> pretty sure your LinkSys box lets you map port-A to port-B
> (some lower-end boxes won't).
>
>                  Good luck!
>
> -Scott
>
> > Thanks for everyone's help.  I had someone else try at a different
> company
> > to get to the home PC and they were able to get connected via the Java
> > viewer.  The ports must be blocked at my company...
> >
> > Thanks again,
> > Nick
---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------