Micha <[EMAIL PROTECTED]> writes:
> | The only thing that I can think of is that there is a networking
> | problem of some sort.
>
> Yes that's why i care so much, i don't like to have something
> unexplainable running here.
>
> | This could be caused by not having 'woody.lan1' in the hosts file
> | on the WWWOFFLE server or by the DNS configuration.
>
> It is. However, 192.168.1.2 is the outbound gateway interface,
> i'm not sure how it works, but I don't think traffic targeted for that
> interface itself would never be passed to the router gateway ?
> That's however the only source of weirdness *i* can think of, at the
> moment. Triggered by some unexpected software feature ... ?
>
> | If 'woody' works on all of the machines then it is best to use this as
> | the first entry in the LocalHost section.
>
> Yes, i do.
>
> On remote machines, 'woody' equals 'woody.lan1' and is naturally
> defined as '192.168.1.2' where on the server box 'woody' is 127.0.0.1.
> That's how it obviously works best.
Do you really mean that on the server machine woody.lan1 is
192.168.1.2 but woody is 127.0.0.1? This isn't the right way to do
things. The address 127.0.0.1 should be called localhost and the real
name of the machine (woody or woody.lan1) should be a different
address. If your domainname is lan1 then the name woody actually
means woody.lan1, it is just a shortened version of it.
--
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop [EMAIL PROTECTED]
http://www.gedanken.demon.co.uk/
WWWOFFLE users page:
http://www.gedanken.demon.co.uk/wwwoffle/version-2.9/user.html
