to all those who responded - thanks.
i finally got it to work and discovered something interesting about
zonealarm (which i hadn't seen before) in the process...
to recap:
1. i had no problems with vnc internally
2. i never could get it to work externally.
when testing externally, i would always turn off zonealarm and then try
to connect (or be connected to). it turns out that my ZA was not
configured to allow 'internet connect' under vnc server. i never
bothered to change that setting because i would always turn ZA off
before playing with VNC.
it turns out that it *seems* like the ZA settings are *sticky* - meaning
that once u turn it off, some of the settings remain. i discovered this
when i got vnc to work after i changed ZA NOT to load at startup. once
that discovery was made, i changed ZA to allow 'internet connect' and
load at startup and the thing swims....
i don't know if this is a bug, or a feature...i'll sniff around in the
doc and potentially post the question on gibson's board...
----- Original Message -----
From: "ROTTENBERG,HAL (HP-USA,ex1)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, December 15, 2000 1:09 PM
Subject: RE: vnc in w2000 behind router and zonealarm
> David,
>
>
> Here's what you do:
>
> 1) Forward VNC ports that hit your router to your internal LAN.
> 2) Find IP address of your router.
> 3) Connect using VNC to your router.
>
> Does your router support port forwarding? For instance you might be
able to
> tell it to forward all requests to port 5900 to port 5900 on
192.168.0.3.
> Then if you wanted to manage one of your other computers, you'd have
to
> forward port 5901 to port 5900 on 192.168.0.4, etc. If it does not,
then it
> gets more complicated. If your router will allow a PC to be "outside
the
> firewall" and act as a server, then you can use port mapping
standalone
> software on your Win2k box to do the same thing. Not the ideal
situation if
> you can avoid it.
>
> Then part two, you MUST know the ip address of your router, which is
> probably DHCP. So from work you would connect to x.x.x.x port 5900
(display
> 0) to control machine1, port 5901 (display 1) to control machine2,
etc.
>
> The hard part with a home lan can be knowing what your DHCP ip address
is.
> I recommend using one of the dynamic DNS services. There are many
free and
> low$ services out there. The way it works is you run a small client
on one
> of your PC's and tell it to check the IP address every so often and
poke
> that to the dynamic DNS server where you'll have a DNS name, like
> rothman.dyndns.net
>
> Here's a good link to get you started.
>
> http://noeld.com/download.htm#DynSite
> http://noeld.com/download.htm#Supported
>
> Hal Rottenberg | Hewlett-Packard
> Technical Support Engineer | Phone: +1-404-774-4041
> Internet Security Division | Email: [EMAIL PROTECTED]
>
> Web: http://www.hp.com/security
>
>
> -----Original Message-----
> From: David Rothman [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 15, 2000 10:52
> To: [EMAIL PROTECTED]
> Subject: Re: vnc in w2000 behind router and zonealarm
>
>
> im not sure that i follow u.
>
> locally, vnc works fine for me. all the machines are set to a local
> zone and we can all view each other - no problem.
>
> my question is how do i do this over the net? if my basement machine
is
> 192.168.0.3 (local ip address), how do i get to it. attaching to my
> cable modem's ip doesn't move me over to a specific machine in the
> lan...
>
> ----- Original Message -----
> From: "Gene Giannamore" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, December 14, 2000 2:19 PM
> Subject: RE: vnc in w2000 behind router and zonealarm
>
>
> > well the only way I have been able to allow other computers access
to
> a
> > computer running the free zonealarm is to add them (IP address) to
> local
> > zone. then the settings for local zone are used rather than the
> internet
> > zone.
> >
> > -----Original Message-----
> > From: David Rothman [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, December 14, 2000 5:35 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: vnc in w2000 behind router and zonealarm
> >
> >
> > i've tried several searches of vnc and router and
zonealarm....nothing
> > especially useful came up....
> >
> >
> > ----- Original Message -----
> > From: <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, December 14, 2000 8:05 AM
> > Subject: Re: vnc in w2000 behind router and zonealarm
> >
> >
> > > While you're waiting for somebody more knowledgeable to give a
more
> > specific answer, try entering something like
> > >
> > > configure near port* and zonealarm
> > >
> > > into alta-vista's advanced search.
> > >
> > >
> > >
> > > Date: 14.12.2000 13:48
> > > To: [EMAIL PROTECTED]
> > >
> > >
> > >
> > >
> > > Reply to: [EMAIL PROTECTED]
> > >
> > > Subject: vnc in w2000 behind router and zonealarm
> > > Message text:
> > >
> > >
> > >
> > > im sure this has been discussed to death, but i havent found an
> > explicit
> > > reference in a quick scan...
> > >
> > > i want to access my machines remotely over the net. they all run
> > w2000
> > > or w98se. they all use a netgear rt311 router to share a cable
> modem
> > > and they all run zonealarm.
> > >
> > > i know that i have to open 58xx or 59xx in the router setup and
may
> > also
> > > have to enable ZA to accept certain incoming requests.
> > >
> > > can someone please direct me to a thread to search for in deja or
an
> > > online reference as to how to do this?
> >
>
> ---------------------------------------------------------------------
> > > To unsubscribe, send a message with the line: unsubscribe vnc-list
> > > to [EMAIL PROTECTED]
> > > See also: http://www.uk.research.att.com/vnc/intouch.html
> >
>
> ---------------------------------------------------------------------
> >
>
> ---------------------------------------------------------------------
> > > To unsubscribe, send a message with the line: unsubscribe vnc-list
> > > to [EMAIL PROTECTED]
> > > See also: http://www.uk.research.att.com/vnc/intouch.html
> >
>
> ---------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> > To unsubscribe, send a message with the line: unsubscribe vnc-list
> > to [EMAIL PROTECTED]
> > See also: http://www.uk.research.att.com/vnc/intouch.html
>
> ---------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> > To unsubscribe, send a message with the line: unsubscribe vnc-list
> > to [EMAIL PROTECTED]
> > See also: http://www.uk.research.att.com/vnc/intouch.html
>
> ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
