DHCP not working
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.DHCP not working
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello,
The Problem: all devices except one are failing to obtain an IP address automatically. Currently they are being connected using static IP addresses. No changes were made to the router setup prior to this issue, however, couple of days ago there was a thunderstorm that fried the network switch which provided the connection to my router. I also had another cheap router connected to this router as wired range extender. This second router is also dead since the thunderstorm which was not due to the electrical short circuit for sure. Before all this, everything was working properly.
Is there anything I can try to make DHCP work before resetting the router?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I suggest you reset the router and try it out. At least you can simply learn that the problem is a software thing. 19216811-login
- Copy Link
- Report Inappropriate Content
Hi,
Sorry to respond late.
First, you can try to disable the DHCP server and re-enable it.
Besides, you can forget the network(delete the profile) and reconnect to the TP-Link wifi to test whether it can obtain IP address automatically.
https://www.tp-link.com/en/search/?q=profile&t=FAQ&p=1
If still the same, it is suggested to hard reset the router to give it a shot.
Good day.
megabolod wrote
Hello,
The Problem: all devices except one are failing to obtain an IP address automatically. Currently they are being connected using static IP addresses. No changes were made to the router setup prior to this issue, however, couple of days ago there was a thunderstorm that fried the network switch which provided the connection to my router. I also had another cheap router connected to this router as wired range extender. This second router is also dead since the thunderstorm which was not due to the electrical short circuit for sure. Before all this, everything was working properly.
Is there anything I can try to make DHCP work before resetting the router?
- Copy Link
- Report Inappropriate Content
Update ( I know it's been a while!):
I tried hard resetting, no change. Except 2 devices (so far), others failed to obtain an IP automatically. The devices ( an Android and another windows laptop) that can connect automatically often fail to do that, particularly the Android phone after a reboot. Anything else I can try?
- Copy Link
- Report Inappropriate Content
megabolod wrote
Update ( I know it's been a while!):
I tried hard resetting, no change. Except 2 devices (so far), others failed to obtain an IP automatically. The devices ( an Android and another windows laptop) that can connect automatically often fail to do that, particularly the Android phone after a reboot. Anything else I can try?
Ensure the current firmware is the latest one, otherwise, upgrade it first.
Still the same, contact TP-Link tech support to check the warranty.
- Copy Link
- Report Inappropriate Content
did you ever get this sorted? I was google for answers as I have run into the same issue now and TP-Link support claim they have never heard of such a thing. My network is crippled and I pulling my hair out.
if I manually assign IP address to all the devices I can. Many IoTs have to find their own. (But oddly connect where as laptops. iPads. Phones etc. Don't) I can get it to work but the connection is slow.
- Copy Link
- Report Inappropriate Content
@megabolod Hi, today I got the same problem.. still persisting. Tried to restart the router, restart the DHCP, forget the network in the devices.. nothing worked! I use the Archer C60 firmware 1.0.2
- Copy Link
- Report Inappropriate Content
Hi, I solved the issue,
I thought the problem was the number of IP reservation but .. I was wrong.
In my case the DHCP stopped working when I added the 16th static IP record on the router. I got crazy, but removing the 16th device the DCHP started working normally. Probably I typed wrongly the IP? I don't know, but the fact is that i fixed like this:
1) removed the 16th IP reservation
2) I made a back up of the settings
3) I made a factory reset
4) I reloaded the back-up
This fixed the problem.
I then added 2 more IP reservation and was working fine...
Best regards
- Copy Link
- Report Inappropriate Content
@Abaresaru never got a helpful reply from TP-link at all. It never got resolved. But it's been much more stable since the last firmware update. And as a user below noticed and I can only confirm anecdotally. But my registered addresses were down to 12. I don't want to add more back in again to test the theory as I can bear Alexa moaning at all of my IoTs again!
- Copy Link
- Report Inappropriate Content
I can only confirm anecdotally. But my registered addresses were down to 12. I don't want to add more back in again to test the theory as I can bear Alexa moaning at all of my IoTs again! But it maybe you are on to something here!!
- Copy Link
- Report Inappropriate Content
Can you please confirm if you are both configuring the Address Reservation under Advanced >> Network >> DHCP Server? Was there any error message when you add more than 16?
What if you leave all the devices obtaining the IP address from the router automatically, will they work fine?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 22174
Replies: 15
Voters 1
