cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6412
Views
5
Helpful
19
Replies

DHCP no longer works after router was relocated

Kekun
Level 1
Level 1

Router : C891F (1 Gigabit L3 port and 8 switch ports)

It's probably easy but I don't know what's wrong. To put you in context, I configured a router out of the main LAN and everything worked except that 1 computer was stuck with an APIPA address while another plugged in the same port recieved DHCP no problem.

After work hours, I plugged the organization's unmanageable switch into the port that had been configured for that switch but Nothing (yes, the config has been saved before turning off the router). Everything gets an APIPA address. I rebooted the router and access point, no change. I rebooted the computers, no change. Rebooted the switch, no change. I set up static IPs, now I can connect to the management interface but still no internet access and anyway, I want DHCP to work, not set static IPs everywhere. I had already tried the router on the real network and it worked fine so I Wonder what's the problem.

Does it have to do with the DHCP lease time? Does it have anything to do with the client MAC address? Is the computer refused DHCP or is it just unable to communicate with the server (which worked before I moved the router)?

Is the server trying to remember computers or Something? Can I prevent this?

19 Replies 19

Hello,

try and add:

ip dhcp excluded-address 192.168.1.1

and

ip dhcp excluded-address 192.168.2.1

I re-added 192.168.1.1 and 192.168.2.1 as excluded addresses. It was copnfigured before but I removed that to see if it would make a difference. It didn't.

You have to remove the subnet prefix-length command from the DHCP pools:

ip dhcp pool ORG1
 utilization mark high 20 log
 utilization mark low 2 log
 network 192.168.1.0 255.255.255.0
 subnet prefix-length 24
 default-router 192.168.1.1
 dns-server x.x.x.x x.x.x.x x.x.x.x
!
ip dhcp pool ORG2
 utilization mark high 20 log
 utilization mark low 2 log
 network 192.168.2.0 255.255.255.0
 subnet prefix-length 24
 default-router 192.168.2.1
 dns-server x.x.x.x x.x.x.x x.x.x.x

This command is used by a subnet allocation server to allocate a subnet whose size is based upon the specified CIDR length, instead of an individual address from a DHCP server. The subnet mask specified within the network command in the DHCP pool is what assigns the subnet mask to DHCP clients.

Great solution, Kevin ! I have actually never seen that command in any DHCP pool configuration before.

Kekun
Level 1
Level 1

I feel a bit stupid now hahaha

I added this command because one of the computers had trouble and didn't notice it was what caused all the rest to go down...

With all the changes that I have made, removing this line from both pools solved the issue. Everything works now, thanks alot to both you and Georg for the help. I knew it was something stupid lol

Have a great day :)

Simon