Home Network Community > Wi-Fi Routers > TL-WR1043ND (as WAP) can't access login panel, or get wifi access to it :-(
< Wi-Fi Routers

TL-WR1043ND (as WAP) can't access login panel, or get wifi access to it :-(

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

TL-WR1043ND (as WAP) can't access login panel, or get wifi access to it :-(

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TL-WR1043ND (as WAP) can't access login panel, or get wifi access to it :-(
TL-WR1043ND (as WAP) can't access login panel, or get wifi access to it :-(
2016-12-11 23:28:28
Model : tl-wr1043nd

Hardware Version : WR1043ND v1 00000000

Firmware Version : 3.13.15build 140319 rel 41339n

ISP : rogers canada

I have a tl-wr1043nd running as a WAP behind a hub and a dlink dir825 router. The tplink is running 3.13.15build 140319 rel 41339n.
Regularly, a wifi "wannabe" can't login into the wifi even though other existing clients on the box have full access to the network thru it. A "wifi analyzer" sees the broadcasting ssid and strength is good. Existing devices on the network (hardwired) are unable to connect to the ip address of the tp-link. This situation happen about every 2-3 weeks. Unplugging / plugging power resets the tplink and everything is fine again with normal tplink login success along with wifi access. I have tried changing the mode to bgn mixed fixed channel along with others such as 11bg mixed auto, etc. None appear to help the condition.

From my "view", it appears somehow that the device gets in some sort of "work loop" such that it can't respond to access requests but functions ok in packet routing.
Is this a known problem? Is there any work solutions? Thanks for any guidance on how to get out of this issue permanently outside of buying another box.
  0      
 
  0      
 
#1
Options
5 Reply
Re:TL-WR1043ND (as WAP) can't access login panel, or get wifi access to it :-(
2016-12-13 08:43:05
ok... so today I noticed that the flashing status light to indicate "system status" has gone out, indicating the router has a system error :-(
existing devices both wifi connected and wired can access the internet and things look normal to them. New devices trying to connect via wifi cannot connect. Existing devices, either wired or wifi'ed cannot reach the unit via the browser address to login.... they just "hang".
Anyone seen this kind of issue before? Can anything else be done other than "regular" depowering/powering which temporarily solves the issue?
  0  
  0  
#2
Options
Re:TL-WR1043ND (as WAP) can't access login panel, or get wifi access to it :-(
2016-12-21 07:18:52
contact with tplink support. They are looking at it, first "pass" appears to indicate "design intent" but I think they need to relook at the information provided to them. Hopefully, they can come up with something better.
  0  
  0  
#3
Options
Re:TL-WR1043ND (as WAP) can't access login panel, or get wifi access to it :-(
2017-01-06 21:37:10
after working with support, they indicate that the problem is because it is old and "design intent" and not a firmware issue.... great! :-( funny though I have reloaded it with gargoyle and the box no longer hangs. can be login at all times. Funny how some other firmware appears to solve the "design intent, its old" problem. Glad I replaced it with a stable dlink router/AP. I would certainly beware wary of using tplinks in any network where you expect regular normal usage.
  0  
  0  
#4
Options
Re:TL-WR1043ND (as WAP) can't access login panel, or get wifi access to it :-(
2017-01-07 23:17:32
Hi,

I had the same issue. Disabling UPnP solved it for me. (Forwarding->UPnP).

So it's definitely a FW problem.

Firmware Version: 3.13.15 Build 140319 Rel.41339n
Hardware Version: WR1043ND v1 00000000
  0  
  0  
#5
Options
Re:TL-WR1043ND (as WAP) can't access login panel, or get wifi access to it :-(
2017-01-09 00:06:26
thanks for that. Tplink support said the same thing, I did the "upnp" disabling, but it didn't resolve the problem. So right now, its running fine on gargoyle.

The "fun part" of this whole thing is the number of posts around the same / similar issue and this part of the reply from the tplink support group which leaves one questioning either their understanding of the product or their "design intent".

Quote from email: "... It is natural to see the product will have much attrition due to the long-time use rather than bug. And so sorry nobody can fix it. The product has a limit service time."

sheesh!!!!! lucky my other network products (gateway router, ethernet switch, wireless access points / routers) don't have this type of "good design".
[SIZE=1][SIZE=2][SIZE=3]
Its sad that they think this way as opposed to actually getting down to the source of the problem.[/SIZE][/SIZE][/SIZE]
  0  
  0  
#6
Options

Information

Helpful: 0

Views: 2803

Replies: 5

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.