Things are working ... but

[Harry Putnam <reader@newsguy.com>]

Resolved the problem posted in previous messages under "Getting
searches to work" thread.  I had been experimenting with different
DocumentRoots and was working on the wrong "index.shtml" hence the
path was wrong.

Now that searching is working I have whole new problem.  Here is the
sequence of events I'm seeing:

Insert search string in form box... press search

Search happens and a listing of the documents containing hits along
with a readout of the hit appears on a fresh page.  Clicking on any
link to a document gives this (Netscape) message:

"Netscape's network connection was refused by the server 209.144.125.
The server may not be accepting connections or may be busy.
Try connecting again later"

I'm running a dialup machine on ppp and have an eth0 interface up too.

The address above that is being inserted by webglimpse script (I
guess) is not my current dialup IP or the remote IP or my eth0
address.

I've given netscape an adddress of this form:

netscape http://<MY.ETH0.ADDRESS>

The index.shtml in DocumentRoot contains the wbglimpse startup stuff.

I've also tried http://MY.CURRENT.IP

Both ways connect to the proper DocumentRoot.  Webglimpse is working
and performs a search, but any attempt to follow the links that are
listed will generate an Identical netscape message containing the
address referred to above.

This has survived several httpd restarts and even a full reboot.

Where the heck is webglimpse getting that address? It doesn't appear
in any of the httpd server vars, listed with the "printenv" SSI