[Xitami] Web server not finding IP address

[Brian {Hamilton Kelly}]

In message <200106081426.CAA27428@pagoda.wgtn.cat-it.co.nz>
   Ewen McNeill writes:
> In message <8A6229AB5BE35447A7A838D64C1792BBB2A747@exchangeus.edocs.com> <Xitami
> @ec-computers.net>, Xitami@EC-Computers.Net, Ted Morgan writes:
> >Very recently my Xitami web server started having problems binding to my IP
> >address.  I have it configured so that it will run at startup (using Windows
> >98).  But it will only list 127.0.0.1 as the IP address of the machine.  
> 
> Which version of Xitami is it? (2.5b4, but dos console? Win32?  NT
> Service?)  And how do you have it configured to "run at startup"?  When
> a user logs in?  Or before that?
> 
> Normally Xitami will find the IP addresses that are available when it
> starts, so I'm puzzled by your situation -- possibly it is starting
> before an address has been allocated for your network card (eg, via
> DHCP)?  Or possibly something strange is going on.

FWIW, a colleague of mine tried installing Xitami on some machines in a
teaching lab last year (I don't know which version he was using).  The
machines all worked fine if one logged in to them as "admin", or with
otherwise unrestricted accounts, yet if one logged in with a very
restricted account[1], the server would only respond to the loopback
address, and not to that of the LAN[2].

I'm pleased to say that bw3224b9 does *not* suffer with this problem: it
runs with both the 127.0.0.1 and the allocated 193.63.241.* addresses
quite happily whatever the privileges of the user account.

[1] I've used the System Policy Editor[3] to create very restrictive
accounts to prevent students screwing up the configurations of these
Win95 machines; it works *really* well.  (Of course, it makes it much
easier to prevent these policies being circumvented by having a PDC on
the network too.)

[2] The LAN has fixed, pre-allocated IP addresses: no DHCP involved here.

[3] There have been no changes to the policies between last year's
failures and this year's successes: originally, I had thought that some
part of a policy prevented a server process from binding to, and/or
listening on, any IP address other than 127.0.0.1.

-- 
Brian {Hamilton Kelly}                                          bhk@dsl.co.uk
    "We have gone from a world of concentrated knowledge and wisdom to one of
    distributed ignorance.  And we know and understand less while being incr-
    easingly capable."              Prof. Peter Cochrane, formerly of BT Labs