OK. Well, you may just want to investigate and see if there's a way to just
"punch a hole" in TPF for (Win)VNC, which runs over port 5800 and 5900.
Looks like with TPF it's going to be called a "rule".
According to TPF's FAQ (http://clix.to/tpffaq), you need to enable the
"Running on a Gateway" option. Located, supposedly, in
Administration|Advanced button|The second page - Miscellaneous. Not
familiar with that since I use the ICS in Windows XP, not 98. I have just
loaded up TPF and I'm gonna take a look and see if I can configure something
that will work.
Chad Pommiss <[EMAIL PROTECTED]>
LAN Administrator - SEARS Home Improvement Products
407.767.0990 x107 | Fax: 407.551.3100
-----Original Message-----
From: Jeff Tapley [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 02, 2001 1:01 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: "Failed to Connect to Server"
Yes, for internal network at home I am using 192.168.x.x
I am unable to "connect" or "get in" to computer 2 from outside. I can
connect using the public or private IP, or computer name from internally,
but not from outside.
I spoke to someone else about this and they said I need to forward the ports
in my firewall, but I am not seeing any clear information about how to do
this in the documentation. I am using the latest version of Tiny Personal
Firewall. If anyone knows how to forward ports using this software, I'd
appreciate the info. I'm also not sure on which IP to forward ports... I'd
presume the public IP since that is the one I'm attempting to connect to...
Thanks for the response.
----- Original Message -----
From: "Chad Pommiss" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, July 02, 2001 8:48 AM
Subject: Re: "Failed to Connect to Server"
> Let me make sure I got this straight, and to sum it up for anybody else
who
> may have something to contribute to this one. Computer 1 is a "server"
per
> se, in that it's connected to the Internet, waiting for a connection,
> probably serving some other purpose. This computer is at a separate
> location from everything else.
>
> Computer 2 is your "server", presumably at home, and serves the purpose of
> providing a shared internet connection to Computer 3 and any other clients
> that may connect to your home network.
>
> Both "servers" have static, public IP's. The first question I have is
what
> IP scheme are you using for your internal private network at the house?
> 192.168.x.x? You say you can connect to VNC via the PUBLIC IP of Computer
> 2? But not the private IP? Also, are you running a DHCP server on
Computer
> 2?
>
> I run ICS on a XP server at the house. It's dual-homed like your Computer
2
> (one IP on the Internet, one IP on the LAN). I'm able to connect to it
> anywhere just fine, and when I hover over VNC I too see both IP's. I
> suspect that there is something with your firewall software that is
staying
> loaded even after you turn it off. VNC is real lightweight and real cut
and
> dry, which is what makes it so great. So, that being said, it more or
less
> either loads or it doesn't load. If it's running and you cannot connect
to
> it, either your DSL provider is blocking inbound traffic on all other
ports
> other than the usual stuff, or something is running that is blocking you
> from accessing VNC's port.
>
> Chad Pommiss <[EMAIL PROTECTED]>
> LAN Administrator - SEARS Home Improvement Products
> 407.767.0990 x107 | Fax: 407.551.3100
>
> -----Original Message-----
> Date: Fri, 29 Jun 2001 11:09:12 -0700
> From: "Jeff Tapley" <[EMAIL PROTECTED]>
> Subject: "Failed to Connect to Server"
>
> Hi- I'm new to the list and new to VNC. Not "REAL" technical minded but
I'm
> having a problem using VNC. Any advice at all would be greatly
appreciated.
> I
> am attempting to use VNC on 3 seperate computers. Details of the
> configurations follow:
>
> 1. Computer 1 is a Win2K Server w/ a DSL connection , static IP address,
> through a DSL router, running VNC Server. (seperate location from Compters
2
> and 3)
>
> 2. Compter 2 is a WinME computer w/ a DSL connection, static IP address,
> also
> connected to an internal network running ICS (via 2 NIC's), also running
VNC
> Server, as well as Tiny Personal Firewall
>
> 3. Computer 3 is a WinME computer attached to Computer #2 via home
> networking
> wizard & sharing the internet connection with #2. No firewall on this
> machine.
> Not running VNC Server, but has the viewer installed.
>
> My problem is this...
>
> I am able to connect to Computer 1 from both Computers 2 and 3. I am also
> able
> to connect to Computer 2 from Computer 3 using only the static IP (the one
> connected to the internet) as the host address. I am, however, unable to
> connect to Computer 2 from Computer 1. I have made attempts with the
> firewall
> turned off and on, and have given access priviledges to VNC in TPF's
> configuration. Either way, I get the same "Failed to Connect to Server"
> message when I attempt to logon.
>
> My thought is that perhaps it "might" have something to do with Home
> Networking/ ICS as Computer 2 shows both IP addresses when hovering over
the
> VNC Server icon. It shows the addresses with the internal IP first and
> seperated by a comma. I have attempted several combinations of logging on
> swapping the order of the IP's, using only the static IP, using colon
> instead
> of comma, space after comma, no space after comma, etc to no avail. Is it
> likely that this is indeed the problem and does someone know a workaround?
> i.e. unregistering the internal IP from VNC in the registry or something
> like
> that.
>
> Or are there other things I should be looking at? I'm stumped.
>
> Again, any feedback/ advice at all would be GREATLY appreciated. I think
> it's
> a great technology- just wish I could get it to work on both ends, and I'm
> sure it must be something I'm doing/ not doing.
>
> Thanks in advance.
> Jeff Tapley
> [EMAIL PROTECTED]
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
