I have the same issue as the OP.
TL-WDR4300 firmware 3.13.33 Nuild 130617 rel.46239n, release date 17.06.2013 - which still is the most recent as per 09.07.2014

Anyone have a solution?

You can open Firefox, enter "about:config" and search "network.http.sendRefererHeader", change value from 0 to 2. Done :cool:
I have found it from: http://punto50.blogspot.com/2014/03/error-tp-link-you-have-no-authority-to.html

Don't know if it helps anyone but i get the error only when using the dns name. I can access the router without problems when using the wan ip.

Gr, Kim

KimP wrote

Don't know if it helps anyone but i get the error only when using the dns name. I can access the router without problems when using the wan ip.

Gr, Kim

Is working for me, too. I have a TL-WR740N / TL-WR740ND router. I ping the dns name to find the IP address, than I connect directly to IP:port and the router grant me access.

I have the same problem after the update. I have an ISP DDNS and would like to access my router from random public IP.
The same frustrating error: "Yo have no authority to access this router!".

Anyone from TP-Link could help us?

Hello everyone!

Try to use ONLY the public IP instead of DDNS URL.

So use only http://[PUBLIC_IP_ADDRESS]:[PORT]

Example: http://8.8.8.8:8080.

Trust me, it will work.

It sounds like TP-Link has released a new firmware that will not allow people to access the web configuration page of the device if the computer has a different subnet IP.
You just get the message 'You have no authority to Access this router".

I just purchased a bunch of these and started by deploying two of them.

to get around the problem of using the default login and getting to the page 'You have no authority to access this router', you must use a computer that is on the same subnet as the WAP.

for example:
My server is on the IP address: 192.168.0.XXX

the DHCP range is 192.168.1.2-192.168.1.254 (DHCP computers and devices are on a different subnet than the server).

the two WAPs came up automatically on 192.168.1.8 and 192.168.1.9

I was NOT able to access them from the server (on the 192.168.0.xxx subnet), but WAS able to access them from ANY other computer on DHCP (on the 192.168.1.xxx subnet).

Once I accessed them from a computer, I was able to make the necessary changes to the WAP and get it on the 192.168.0.xxx subnet (and give it the Static IP address that I wanted).

I was then able to access the WAP from the server, but not from any of the workstations.

**NOTE: On the Network->LAN configuration page, there is an 'Allow remote access' checkbox. This checkbox should be the setting that we need to configure the device from other subnets, but it has no effect (whether checked or unchecked).

Hope this helps somebody.

GOOD NEWS!
TP-LINK has resolved this issue in the latest firmware of TL-MR3220_V2, here is the new official firmware.
www.tp-link.com/en/support/download/?model=TL-MR3220&version=V2#tbl_j

has resolved this issue by disable firewall

Deactivating firewall (which is not an OK option for me, really, duh) and/or connecting to IP address didn't help me, still getting:

You have no authority to access this router!

Please, release a fix for this problem with Remote Administration. I can't roll back to firmware older than TL-WR740N_V4_140520, because of this fix, which helped me a lot:

[*]Improved wireless performance and fix some minor problem.