[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] RE: DHCP not working with 4.2.2.EL

Hi Ted,

It sounds like the dhcp service is no longer running after the upgrade.

First check to see if it will start:
/etc/init.d/dhcpd restart  This should give a "failed" on the stop part
and an "OK" on the start.

If the clients boot OK now, just make sure it will start after a reboot:
/sbin/chkconfig --list dhcpd

you should see something like:
dhcpd           0:off   1:off   2:on    3:on    4:on    5:on    6:off

if you see:
dhcpd           0:off   1:off   2:off   3:off   4:off   5:off   6:off

or an off next to 3: or 5: just run:
/sbin/chkconfig dhcpd on

If the clients won't start after you make sure the dhcpd is running
check the firewall. An insecure but simple test is to turn off the

/etc/init.d/iptables stop

Then retry the clients. If they start, the upgrade twiddled with the
firewall settings. You will need to allow incoming connections from the
port running dhcpd (eth0 ?). You can use the gui in webmin to fix this
or just edit the file /etc/sysconfig/iptables and restart the firewall.

You will need to be careful and make a copy of this file first. Unless
you are on the console or have a script to reset the firewall back if
you don't do something after a certain time, you can lock yourself out
of the system if you do this remotely and make a mistake (gee! - first
hand experience :) It's one thing when the box is down the hall. It's
something else entirely when it's many hundreds of miles away in a colo
center :)

On Wed, 2006-09-27 at 13:44 -1000, Ted Kanemori wrote:
> I just loaded K12LTSP 4.2.2EL on a new system that’s hooked to a
> couple of thin clients.
> When I booted the thin clients, everything works fine.
>             I loaded adobe, java and all the additional software.
>             When I booted the thin clients, everything worked fine.
>             I did a “yum upgrade” and 8 programs were installed and
> another 185 upgraded.
>             Now, when I boot the thin clients, I get a message that:
>             “no dhcp or dhcpproxy server offers received”.
>             The thin clients do not boot up.
>             Is there another step that I’m missing?
>             Should I “not” have done the yum upgrade?
> _______________________________________________
> K12OSN mailing list
> K12OSN redhat com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
James P. Kinney III          
CEO & Director of Engineering 
Local Net Solutions,LLC        

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
<jkinney localnetsolutions com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]