DHCP IP Address Conflicts on Reboot

DHCP IP Address Conflicts on Reboot

13 Reply
Re:DHCP IP Address Conflicts on Reboot
Wednesday - last edited Wednesday

  @CoffeeAndTech 

 

 

 

 

  0  
  0  
#14
Options
Re:DHCP IP Address Conflicts on Reboot
Wednesday

Hi @CoffeeAndTech 

Thanks for posting in our business forum.

CoffeeAndTech wrote

  @Clive_A 

 

These warnings are coming wireless devices. Here are two examples:

 

1) Conflict between a Macbook Air (connected to EAP_1) and an iPad (connected to EAP_2)

2) Conflict between an iPhone (connected to EAP_3) and an unknown MAC ID (suspect an iPhone) (connected to EAP_2).

 

What is interesting is that they are on different TP-Link EAPs (EAP650s). 

 

 

I tried setting my lease to 2 hours and then also to 7 days. Either option didn't seem to make an impact on the problem.

That does not make too much difference to me. These pictures are generic config. I don't find anything wrong with them.

 

I want to know if you simplify your network, will this error disappear? Remove other devices and keep the AP and the router, and monitor if this persists.

A diagram of your network is required.

A screenshot of your DHCP reservation page.

Does it only happen to certain devices? Or everything is randomly getting the same IP?

What's the network config like on affected devices? I want to learn about it.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  1  
  1  
#15
Options
Re:DHCP IP Address Conflicts on Reboot-Solution
Thursday - last edited Yesterday

  @Clive_A 

 

After a lot of reasearch, I determined this was a result of a few smart TVs that were holding on to their IP leases and not requesting a new IP from the server even after their lease was up. No problem with the router or setup. I forced an IP renewal on these TVs and it solved the problem. Thank you for all your help!

Recommended Solution
  0  
  0  
#16
Options