Topic: DHCP seems to not be working

[Dr_pepper_X]

Here is a short jist of my problem.  I accidently unplugged the network cable to my server while moving somethings.  When I plugged back in the cable to the server my knee hit the power button and shut off the server.  I re-powered back on the server and then watched all the services start and everything appeared to come up.  But since then my other networked computers are unable to get an Ip address and can not talk on the network.  I have checked the am and made sure that dhcp was enabled, I also DLed the blade for the 5.1.2 and rebooted several times and the service said it has started but I am still unable to get IP addresses.  Any suggestions???  Is there a way to run a scandisk type utility to check and make sure nothing has become corrupt?  

Thanks,

Dr_pepper_x

[Steven Thomson]

On your windows machines you would have to log out and then back in if they lose the network....or you can run winipcfg from the Start->Run. Release all and renew all. before/during doing this tail the message log from a console (or from a windows ssh client) to see if they are talking to your server....ie.
tail -f /var/log/messages
you should see the windows nics asking for a dhcp address.
Other than that I'm not sure....check to see that your hub is working.

Hope this helps

[Dan G.]

Most often, I see DHCP failures related to issues with LAN switches --- particularly if they are running any kind of spanning tree calculation when they first sense the DHCP request  --- on some equipment, the spanning tree calculation takes longer than the DCHP reply timeout.  I recently solved an old nagging problem for a client by disabling spanning tree in an ancient Cisco Catalyst.

Try a laptop on a crossover cable, directly connected to the LAN-side NIC of the SME server.  If that client receives an address, you will know your problem is outside the server, and somewhere on your LAN.

Dan

[Randall]

We run a small Lan >500 machines.  To get everything back on line quickly, we bring the local LAN down, Servers, Switches, workstations etc. but NOT the Routers.  We only bring those down if something really bad happens like a UPS failure, Lightning, Pigeons gittin' in thru the A/C ducts and crappin' all over the Routers.  The usual stuff.Dr_pepper_X wrote:
>
> Here is a short jist of my problem.  I accidently unplugged
> the network cable to my server while moving somethings.  When
> I plugged back in the cable to the server my knee hit the
> power button and shut off the server.  I re-powered back on
> the server and then watched all the services start and
> everything appeared to come up.  But since then my other
> networked computers are unable to get an Ip address and can
> not talk on the network.  I have checked the am and made sure
> that dhcp was enabled, I also DLed the blade for the 5.1.2
> and rebooted several times and the service said it has
> started but I am still unable to get IP addresses.  Any
> suggestions???  Is there a way to run a scandisk type utility
> to check and make sure nothing has become corrupt?
>
> Thanks,
>
> Dr_pepper_x