Re: [greenstone-users] Windows XP and local address problem

From Jonathan Tremblay
DateMon, 11 Jul 2005 19:07:46 -0500
Subject Re: [greenstone-users] Windows XP and local address problem
Hi Michael,

The new application worked on all computers that we have tested. I was using option 2 (always using 127.0.0.1). It worked even on the two laptops which were unable to connect to the server with the old version. By the way both of those were having a wireless connection (unused?).

Thanks again, you're doing a wonderfull job.

Jonathan Tremblay

----- Original Message -----
From: "Michael Dewsnip" <mdewsnip@cs.waikato.ac.nz>
To: "Jonathan Tremblay" <jonathan@piccolo.net>
Subject: Re: [greenstone-users] Windows XP and local address problem
Date: Fri, 08 Jul 2005 15:55:26 +1200

>
> Hi Jonathan,
>
> > Thanks for that new version.
> >
> > My first tests on my own computer (which never got the problem) went almost
> > perfect...
> >
> > It was working, until I removed the new "address_resolution_method"
> > argument. Then the home page appeared ok, but it was impossible to load any
> > other page (there was an error message: "[...] cannot connect to
> > [MyComputerName]")
> >
> >
> I've had a quick try and can't reproduce your problem here... if you
> manage to reproduce it consistently please let me know and I'll look
> into it.
>
> Regards,
>
> Michael
>
>
>
> > ----- Original Message -----
> > From: "Michael Dewsnip" <mdewsnip@cs.waikato.ac.nz>
> > To: "Jonathan Tremblay" <jonathan@piccolo.net>, paul.yachnes@naa.org,
> > daniel.odonnell@uleth.ca
> > Subject: Re: [greenstone-users] Windows XP and local address problem
> > Date: Wed, 06 Jul 2005 15:06:04 +1200
> >
> >
> >
> >> Hi Jonathan, Paul, Daniel,
> >>
> >> OK, I've added a new option to the Local Library's gsdlsite.cfg file
> >> that will hopefully help with the problems you've been experiencing. The
> >> option is called "address_resolution_method", and valid values are:
> >>
> >> 0 -- The existing method: work out the IP address, then resolve this
> >> to a name.
> >> 1 -- As above, but leave it as an IP address -- don't resolve it to
> >> a name. This should avoid any DNS problems.
> >> 2 -- Always use "127.0.0.1".
> >>
> >> The modified version of server.exe can be downloaded from
> >> http://www.cs.waikato.ac.nz/~mdewsnip/greenstone/temp/server.exe.zip.
> >> You'll need to replace both existing copies: one in the top-level
> >> Greenstone directory, and one in binwindows. (And don't forget to
> >> re-export the collections).
> >>
> >> The first thing that needs checking is whether the two new options
> >> really work. We don't have any machines here that cause this problem so
> >> I'm hoping that you'll be able to try both new options on your
> >> problematic machines -- do they work not at all/some of the time/all of
> >> the time? If we can prove that one of the new options is consistently
> >> better than the existing method then we can make it the default for the
> >> future.
> >>
> >> As Daniel pointed out, things get a little tricky with the gsdlsite.cfg
> >> file when exporting collections to CD. To include a customised
> >> gsdlsite.cfg file on exported CD-ROMs, you need to do 2 things:
> >>
> >> 1. Include the customised gsdlsite.cfg file in the
> >> exported_collectionsgsdl folder.
> >> 2. Add "gsdlsite.cfg" into the exported_collectionsmanifest.cfg
> >> file, after "server.exe".
> >>
> >> Don't worry that the gsdlsite.cfg file may contain paths that will be
> >> invalid when installed on another machine -- the exported collection
> >> installer is smart enough to override these (and only these) when it
> >> installs.
> >>
> >> Things have been a bit of a shambles here so I haven't been able to test
> >> these as much as I would like. I trust you'll let me know if something
> >> doesn't work!
> >>
> >> Regards,
> >>
> >> Michael
> >>
> >>
> >>
> >> Michael Dewsnip wrote:
> >>
> >>
> >>
> >>> Hi Jonathan, Paul,
> >>>
> >>> Both your questions deal with the same issue so I'll answer them
> >>> together here.
> >>>
> >>> You're right that there is a problem here, although we've never
> >>> experienced it very frequently (it sounds like your mileage has varied).
> >>> I think the best way to deal with it is to have an option to the Local
> >>> Library server to use "localhost" or "127.0.0.1", instead of trying to
> >>> work out the computer's network address "intelligently".
> >>>
> >>> The disadvantage of this is that it is harder for someone else on your
> >>> network to access your Greenstone server, since they can't just use the
> >>> same URL as you. However I imagine that this feature isn't often used,
> >>> especially not for exported collections.
> >>>
> >>> Hopefully I'll have time to do implement this option soon, and I'll let
> >>> you know once I have done so.
> >>>
> >>> All the best,
> >>>
> >>> Michael
> >>>
> >>>
> >>>
> >>> Jonathan Tremblay wrote:
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>> Hi,
> >>>>
> >>>> Some of my users/testers are not able to load the first page when they
> >>>> start the local server.
> >>>>
> >>>> There's an entry in the FAQ about proxy and localhost problems:
> >>>> http://www.greenstone.org/cgi-bin/library?e=p-en-faq-utfZz-8&a=p&p=faqrun#18 They don't use any proxy server. They are using laptops under Windows XP SP2. The firewall is not the
> >>>> problem.
> >>>>
> >>>> The local address resolution doesn't seam to work. The default address
> >>>> which appears in the browser is the machine name WITH the domain name
> >>>> (ex. p225545464.aidslaw.ca) and that cannot be resolved. Either of those
> >>>> solutions will work: a) type http://127.0.0.1/gsdl (or
> >>>> http://localhost/gsdl) manually in the web browser
> >>>> b) edit the hosts file in c:windowssystem32driversetchosts to
> >>>> convert the address to 127.0.0.1
> >>>>
> >>>> I got that situation on the computers of two of my ten testers. And I
> >>>> feel like it's not only a "bad network config" that can be treated as a
> >>>> minor problem. I'm afraid that 2000 of my 10000 final users will get the
> >>>> same one! I cannot ask those people to type an address manually and I
> >>>> cannot ask them to edit the hosts file (which is not always present...
> >>>> and cannot be edited unless the user is an admin).
> >>>>
> >>>> By the way I also tried the Netscape "Restricted version"... but
> >>>> discovered that it doesn't work on (almost all) Windows XP computers...
> >>>>
> >>>> I would like to specify to the server to use 127.0.0.1 as the address...
> >>>> But it doesn't look possible. I did try to edit the url in gsdlsite...
> >>>> but that parameter is not used by the server (then, why is it there?)
> >>>>
> >>>> What else can I do? Would I be able to change the address by recompiling
> >>>> the source code? I was not planning on that...
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Jonathan Tremblay
> >>>>
> >>>> Another link about the same problem:
> >>>> http://puka.cs.waikato.ac.nz/cgi-bin/library?e=q-000-00---0gsarch--00-0-0--0prompt-10---4----dtx--0-1l--1-en-50---20-about-127+local--00031-001-0-0utfZz-8-00&a=d&c=gsarch&cl=search&d=20040210190638.GB1397-wesson.cs.waikato.ac.nz
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> greenstone-users mailing list
> >>>> greenstone-users@list.scms.waikato.ac.nz
> >>>> https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-users
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>> _______________________________________________
> >>> greenstone-users mailing list
> >>> greenstone-users@list.scms.waikato.ac.nz
> >>> https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-users
> >>>
> >>>
> >>>
> >>>
> >>>
> >
> >
> >
> >