I appreciate the help with my airport base station issues as of late.
Turns out it wasn't the base stations, as I began to notice that
computers
connected via ethernet were not getting IP addresses via DHCP. One
thing
is that I wasn't giving out enough addresses, my how my school has
grown!
I had a networking consultant come in and we increased the range of
addresses in DHCP (running on our OSX server that also does MCX). We
thought that might solve the problem, but it hasn't. Apparently
something
must be wrong with my server, as it will not hand out any more IP
addresses. Has anyone seen this before? New clients on the
network just
can't get an IP address through DHCP. Luckily I have a firewall
that used
to do DHCP, so I was able to turn that service on again and we're
back up.
How can I trouble shoot DHCP on the server? Are there any files I
can
trash to "reset" things? We tried deleting the DHCP config and
starting
over. Thanks.
Take at a look at the man pages for bootpd. It looks like dhcp
server configuration is stored in NetInfo. Perhaps you have to edit
that?
How about this for a scenario? You have 2 ethernet adapters but only
one is connected and dhcp service is listening to the wrong adapter.
Ddhcp service depends on xinetd, are contents of /etc/xinetd/bootps
correct? Mine (panther) looks like this:
service bootps
{
disable = no
socket_type = dgram
wait = yes
user = root
server = /usr/libexec/bootpd
groups = yes
flags = REUSE
server_args = -v -D
}
Also, according to the man pages, errors in configuration are logged
to /var/log/system.log ---anything show up there?
