ALso check disk space.  I'm not sure its a direct relation but when you run
out of disk space bad things happen.



On Mon, Sep 27, 2010 at 2:37 PM, Aaron Hackney <aa...@aaronhackney.com>wrote:

> Also, take a peek at the log files. If it's a problem with the
> daemon/permission issues/out of IP Addresses, then your answer will be
> there.
>
> Id's till be curious to see if the DHCP discovery messages are getting
> to the server and what the server is doing in response.....
>
>
> On Mon, Sep 27, 2010 at 1:53 PM, K Lesko <kle...@gmail.com> wrote:
> > Opps read your post over again and it looks like you addressed the range
> > issue.  Are you restarting the DHCP service after you make changes to the
> > config file?
> >
> > On Mon, Sep 27, 2010 at 1:26 PM, K Lesko <kle...@gmail.com> wrote:
> >>
> >> Have you checked to see if any other processes may have crashed on the
> >> box?
> >> From terminal run:
> >>   ps aux|grep defunct
> >> to see any processes that may have crashed.
> >> If nothing shows up as defunct and your logs aren't showing errors I
> think
> >> Eric may have the right ideal about a bad NIC.
> >> I am definitely no expert but on your DHCP.CONF file you have:
> >> subnet 10.0.0.0 netmask 255.255.0.0 #GREEN
> >> {
> >>        range 10.0.2.50 10.0.2.255;
> >>        option subnet-mask 255.255.0.0;
> >> Does this range declaration limit the dynamic IPs to those between the
> >> 10.0.2.50 and 10.0.2.255?  So are you sure you have any IPs left to hand
> >> out?
> >> Hopefully someone more qualified can chime in on this . . .
> >>
> >>
> >>
> >> On Mon, Sep 27, 2010 at 12:56 PM, Abe Loveless <
> li...@lovelesscentral.org>
> >> wrote:
> >>>
> >>> ??  You're not going to want a router managing dhcp are you?
> >>>
> >>> What do the system stats show you on the status pages, etc?  I've
> always
> >>> heard that too large of a DHCP Range can really suck the memory out of
> a
> >>> box.  Also, did you verify that you have plenty of disk space free?
> That
> >>> should also be available on one of the status screens.
> >>>
> >>> Is your content filter also on this machine?  Any problems with that?
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On 9/27/2010 12:47 PM, Charlie Niehaus wrote:
> >>>>
> >>>> Thanks Abe.  Now just tell me why the boxes can not assign the IP?
> >>>>
> >>>> Might be a moot point - looking to replace it with a router.
> >>>>
> >>>>
> >>>> -----Original Message-----
> >>>> From: tech-geeks-boun...@tech-geeks.org
> >>>> [mailto:tech-geeks-boun...@tech-geeks.org] On Behalf Of Abe Loveless
> >>>> Sent: Monday, September 27, 2010 11:51 AM
> >>>> To: Tech-Geeks Mailing List
> >>>> Subject: Re: [tech-geeks] IPCop - DHCP not responding.
> >>>>
> >>>>
> >>>>
> >>>> On 9/26/2010 11:59 PM, Charlie Niehaus wrote:
> >>>>>
> >>>>> The range of IP's is OK: I noticed that when I ran the Rogue DHCP
> >>>>> checker
> >>>>> program it ALWAYS picked up the HIGHEST IP in the range - even if I
> >>>>> change
> >>>>> the range and gave it MORE Ip's to hand out.
> >>>>
> >>>> It always does that.  IPCop starts handing out the at the top.  The
> SME
> >>>> Server's used to start at the bottom.
> >>>> | Subscription info at http://www.tech-geeks.org |
> >>>>
> >>>> | Subscription info at http://www.tech-geeks.org |
> >>>>
> >>>>
> >>> | Subscription info at http://www.tech-geeks.org |
> >>
> >
> >
> > | Subscription info at http://www.tech-geeks.org |
> >
>
>
>
> --
> "Don't ask yourself what the world needs. Ask yourself what makes you
> come alive and then go do that. Because what the world needs is people
> who have come alive." -Dr. Howard Thurman
>
> ******************************
> Aaron Keith Hackney
> aa...@aaronkeithstudios.com
> Cell 210.325.2196
> ******************************
> | Subscription info at http://www.tech-geeks.org |
>
| Subscription info at http://www.tech-geeks.org |

Reply via email to