| > Now i tried another thing, 'woody.lan1`as first entry. | > This worked well from other hosts (with host alias definitions). | | Is the hostname woody.lan1 valid from the machine itself? If you run | 'ping woody.lan1' on the WWWOFFLE server machine do you get a reply?
y o ocurse PING woody.lan1 (192.168.1.2): 56 data bytes 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.2 ms | | 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. ° /\/
