Re: LAN Setup

[John Bell <..hidden..>]

Michael Richardson wrote:
> > > > > > "David" == David A Bandel <..hidden..> writes:
> > > > > >             
>     David> 169.254.0.0/16 is a "zeroconf" address -- it's what Windoze
>     David> uses when it gets lost (can't figure out what it's address
>     David> should be), but there are zeroconf utilities for Linux and
>
>   
"Autoconfiguration" IP Addresses:

       169.254.0.0 - 169.254.255.255

Addresses in the range 169.254.0.0 to 169.254.255.255 are used 
automatically by some PCs and Macs when they are configured to use IP, 
do not have a static IP Address assigned, and are unable to obtain an IP 
address using DHCP.

This traffic is intended to be confined to the local network, so the 
administrator of the local network should look for misconfigured hosts. 
Some ISPs inadvertently also permit this traffic, so you may also want 
to contact your ISP. This is documented in RFC 3330 
<http://www.rfc-editor.org/rfc/rfc3330.txt>.  
http://www.iana.org/abuse/faq.html

So, to answer the original question...

A LAN address of 169.*.*.* implies that the server is set up for 
networking, using DHCP, but no DHCP server is present.

SO... 1st setup your LAN and give your server a static IP address 
(preferably within one of the ranges noted earlier e.g.192.168.0.1)
Next setup Apache. It should work "out of the box"

You can confirm that it is working by opening a browser http://127.0.0.1
Install LedgerSMB and confirm that it is working from a browser on the 
server. http://127.0.0.1/...

Go to your client machine and test that you can "see" the server (e.g. 
ping 192.168.0.x)
Open a browser and go to http://192.168.0.x and you should see the 
Apache welcome screen

You should now be able to see your LedgerSMB installation from the 
client machine.

As far as possible, install one thing at a time and test that it is 
working, before moving onto the next step.

Regards

John