In message <[EMAIL PROTECTED]>, Mike
<[EMAIL PROTECTED]> writes
>Pete,
>
>I hardwired the IP of my LAMP server to 192.168.0.100 - basically a static IP 
>outside the range of the dynamic IP pool. 
>
>All the other machines on my intranet get their IP dynamically assigned by the 
>router and DHCP using a pool that starts at 192.168.0.101.
>
>The other thing I did - all my clients are Windows flavors - so I edited the 
>hosts. file on each machine and added an entry for a fake domain to call my 
>LAMP 
>server like 
>
>192.168.0.100        www.mylampserver.net
>
>Then the client machines can refer to the LAMP server as mylampserver.net
>
>regards,
>Mike

Hadn't thought of doing it that way!  But wouldn't the solution that I
ended up with - giving the computer acting as server the name SERVER,
and calling with http://server - be simpler?  

We need to stop "automatic IP" soon, so that we can check who is seated
at which machine, as part of our in-house security.

-- 
Pete Clark

Sunny Andalucia
http://www.hotcosta.com/comm_1.htm

Reply via email to