From: "Andrew Mahan" <mahanam@comcast.net>
To: <gopher@complete.org>
Subject: [gopher] Re: NT Server?
Date: Wed, 2 Jun 2004 02:29:57 -0700
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
In-Reply-To: <200406020919.CAA16626@floodgap.com>
Thread-Index: AcRIgMdNYTIvn6ArR0uU4lgk0a37jQAAzfEQ
Message-Id: <20040602093002.8607C4F@glockenspiel.complete.org>
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

So basically I am hardcoding each selector to point to the public ip on my
router, and forwarding tcp port 70 to my server?

-----Original Message-----
From: gopher-bounce@complete.org [mailto:gopher-bounce@complete.org] On
Behalf Of Cameron Kaiser
Sent: Wednesday, June 02, 2004 2:20 AM
To: gopher@complete.org
Subject: [gopher] Re: NT Server?

> I am currently trying to run "Gophers" v0.5 on W2k Server.  Since I am
> behind a firewall my machine has a NATed ip address (192.x.x.x).  When I
try
> to connect from offsite, I can view the selectors but clicking on them
tries
> to access the resource via the private ip address.  Needless to say, this
> doesn't work.  Any ideas?

This is likely going to be a problem for almost any gopher server in this
situation, alas. If you have access to the source, a kludgey but workable
solution is just to hardcode the proper address in it, if your box has an
externally accessible IP.

-- 
---------------------------------- personal: http://www.armory.com/~spectre/
--
 Cameron Kaiser, Floodgap Systems Ltd * So. Calif., USA *
ckaiser@floodgap.com
-- Please dispose of this message in the usual manner. -- Mission:
Impossible -