|OMG... you're right, it was a TCP-IP setting :-/
I didn't realize that on XP (and probably on 2000 and NT as well)
computer name and host name are the same, so Greenstone connects to
localhost which is resolved to the computer name. Normally this works
just fine, the only problem was that on this particular PC, a DNS suffix
(domain name) had been entered in the TCP/IP properties (Properties,
Advanced, DNS tab) so "localhost" was resolved to <host name>.<domain
name> instead of just <host name>. Removing the DNS suffix solved the
problem. Thanks for the suggestion.
>>> "John R. McPherson" <email@example.com> 28-10-2003 23:01:35
Rene Schrama wrote:
> Hi all,
> I exported a collection to CD-ROM (on Windows XP) but after
> installation the homepage wouldn't display. I checked for proxies
> found none. Then I accidentally discovered that Greenstone was trying
> connect to <computer name> instead of localhost. The computer name
> JP12 but the host name of the user's PC was JP012. I changed it to
> the host name (JP012) and voila, problem solved. But if this happens
> after distribution I have no control over it, so it would be nice to
> able to connect to 127.0.0.1 and avoid the situation altogether. The
> problem is: how do I tell server.exe to connect to 127.0.0.1 (or
> localhost or whatever)??
The windows server uses standard functions in the win32 libraries to
resolve the machine's host name. If this gets the wrong name, then it
is almost certainly a windows client network settings issue.
I think the reasons that "localhost" wasn't used is because:
1) often stand-alone machines can't resolve the name "localhost" to an
2) in a network environment, that url won't work for any machine other
than the one that the greenstone server is running on.
I don't think there is a setting anywhere to hard-code a server name