Archer VR2800 - 2GHz Wi-Fi frequently cannot obtain IP address
Archer VR2800 - 2GHz Wi-Fi frequently cannot obtain IP address
I've had the router for 3 years without any problems. However, in the past few days I've had an issue where any device attempting to connect to the 2GHz Wi-Fi connection cannot get an internet connection as it's failed to obtain an IP address. This doesn't affect the 5GHz connection nor have I had any issues with my PC over LAN. Both the 2Ghz and 5GHz channels are set to Auto. There are ~3 devices (usually 1) connected to the 5GHz and 7 devices on the 2GHz connection.
I am running the latest firmware which is 0.3.0 0.9.1 v006c.0 Build 170809 Rel.42095n. According to the site the latest is Archer_VR2800V1_0.3.0_0.9.1_up_boot(170809)_2017-08-09_11.47.53.
Attempted fixes
1) Reboot the router. However, this only works temporarily. It would only occur once a day now it's once every 2 hours or so.
2) Factory reset
There is another router downstairs on a separate line but never had this issue before. The property is end of terrace so there's only 1 attached neighbour and there should be minimal Wi-Fi/signal interference. It has been suggested that I should change the 2GHz channel manually as it's on Auto.. Would that make a difference with issuing IPs?
Thanks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, you can try to change the 2.4G wifi name, channel and channel width(20Mhz). If the issue still there, you may need to contact the tech support to check the warranty.
https://www.tp-link.com/en/support/contact-technical-support/#Hotline-Support
Good day.
- Copy Link
- Report Inappropriate Content
Stella.Q wrote
Hi, you can try to change the 2.4G wifi name, channel and channel width(20Mhz). If the issue still there, you may need to contact the tech support to check the warranty.
https://www.tp-link.com/en/support/contact-technical-support/#Hotline-Support
Good day.
Hello Stella,
Thank you for the response. I've changed the 2.4GHz SSID, channel (1) and channel width (20MHz) as you've suggested. I'll update you with the findings. I have already raised a ticket (#384527) as the router's within the 3-year warranty.
Many thanks.
- Copy Link
- Report Inappropriate Content
@Mach2Infinity I've encountered exactly the same problem today. I did try to change the channel (13) and channel width (40) but it made no difference. I'll try again changing the name as well. Thanks for raising a ticket, hopefully something comes out of that.
- Copy Link
- Report Inappropriate Content
Hi,
Please change the channel to 1,6 or 11, channel width to 20MHz. Do you still have an issue connecting to the 2.4G wifi? Does it happen on all devices all just some devices?
How about the 5G wifi and the LAN connection?
What's the hardware version and firmware version of the router? How long have you used it?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Mach2Infinity wrote
Stella.Q wrote
Hi, you can try to change the 2.4G wifi name, channel and channel width(20Mhz). If the issue still there, you may need to contact the tech support to check the warranty.
https://www.tp-link.com/en/support/contact-technical-support/#Hotline-Support
Good day.
Hello Stella,
Thank you for the response. I've changed the 2.4GHz SSID, channel (1) and channel width (20MHz) as you've suggested. I'll update you with the findings. I have already raised a ticket (#384527) as the router's within the 3-year warranty.
Many thanks.
@Stella.Q Hi Stella. The issue has now been resolved. When I applied the settings you recommended, I also disconnected the Netgear range extender as I realised I should've done this first. When I factory reset the extender, I still wasn't able to connect to it with the same error "cannot obtain IP address". Whilst I can't be 100% (and I'd rather not revert the SSID due to having to set up all over again) I'm pretty sure the fault was with the (old) Netgear extender.
On a sidenote, I've replaced the Netgear extender with a TP-Link model (TL-WA850RE) and noticed earlier I had trouble connecting to it. Once I changed the 2GHz channel on the router back from auto to 1 again it seemed fine. I've since upgraded its firmware so hopefully no more issues.
Thanks for all your help.
- Copy Link
- Report Inappropriate Content
HakanB wrote
Stella, thank you for you reply. I'm away from home until tomorrow pm (UK time) so will try suggested settings then. The problem was happening for all devices on 2.4G, 5G and LAN were both ok. I need to get back home to get you the hardware/firmware version. The router was bought in August 2017.
@HakanB sorry to hear you're having issues mate. The suggested settings by Stella should work unless your router has developed some kind of fault or there's some sort of interference/obstacle blocking the signal. If you have an Android phone/tablet I'd recommend downloading NetSpot - WiFi Analyzer or WiFi Analyzer to see what channels nearby Wi-Fi routers/APs are using. Problem is most routers are set to Auto so they'll switch channels but at least you can choose the least used one. Let us know if those new settings fixed the issue?
- Copy Link
- Report Inappropriate Content
You are welcome, you can try first and let us know if there is any update.
- Copy Link
- Report Inappropriate Content
Thanks for your valued reply, glad to hear that it was resolved.
If need more help in the future, do not hesitate to contact us.
Have a nice day.
- Copy Link
- Report Inappropriate Content
I have tried your recommended settings and no luck. The hardware/firmware versions I'm using are "Archer VR2800 v1 00000000"/"0.2.0 0.9.1 v006c.0 Build 170110 Rel.33619n". I should probably have upgraded the firmware before replying but as we are ok using 5GHz I don't want to risk anything atm (me and my wofe both working from home 100% due to corona virus), I'll hold off doing that until we know more about returning to work.
Thank you for taking your time, I'll get back to this thread asap.
Hakan
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2875
Replies: 12
Voters 0
No one has voted for it yet.