DHCP Not working

solarem5000

Hello everyone,

Hope can get help with my issue, after looking at posts couldn't find a solution to my issue.

My pfSense router is no assigning IP address to connected hosts, it was working fine and suddenly all the host that didn't have a static IP can't access the web. The only way to access the internet is by configuring a static IP on the host.

Software version 2.3.2-RELEASE-p1
WAN = DHCP
LAN = Static
DHCP server confiregured
IP range 10.0.xx.x to 10.0.xx.xxx

I have a few host running Linux, Mac OS X, and Windows, and they all have the same issue. I have checked all the configurations related to DHCP and DNS, but nothing seems to correct the issue. DHCP is enabled and the IP range is set as it was before it stopped working. DNS forwarder is now enabled, but still no success.

When checking the issue in a windows host, the issue stated is "Windows can't communicate with device/resource (Primary DNS)" but if I configure a static IP in the host or any host I get network access.

if you have any helpful information or links that can help resolve my issue I will really appreciate it.

Thank you.

Derelict

A common cause for DHCP Servers that stop serving addresses is a full disk.

solarem5000

Hello,

Thanks for the quick reply, but that is not the issue. The disk is only 4% used, and memory is at 5% there is plenty or room there as far as I can tell.

johnpoz

" IP range 10.0.xx.x to 10.0.xx.xxx"

For gosh sake dude really.. Its rfc1918 space why are you wasting your time and ours when we need info to help you by trying to obfuscate this.. Its like I can not tell you I live on the planet earth because you might find where I live ;)

""Windows can't communicate with device/resource (Primary DNS)" "

So is it your handing out dns via dhcp that is no longer working? This seems more likely then dhcp not working. What do you see in the dhcp server log? Did you sniff on pfsense interface that dhcp server is listening on - do you see discover packets, and the dhcp server just ignores them? Dhcp server is actually running? Did you try restarting it - again what is in the logs??

If windows can talk talk to a dhcp server, it would give itself a APIPA address, ie something that starts with 169.254.x.x, so what does ipconfig /all show you on these windows machines that stop working?