New Archer VR2800 bound to another TP-Link ID

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

New Archer VR2800 bound to another TP-Link ID

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
New Archer VR2800 bound to another TP-Link ID
New Archer VR2800 bound to another TP-Link ID
2022-10-22 05:36:46 - last edited 2022-10-24 04:02:14
Model: Archer VR2800  
Hardware Version: V1
Firmware Version: 0.7.0 0.9.1 v006c.0 Build 210313

Hi,

 

I have just purchased a new Archer VR2800 from Amazon that arrived sealed.

 

I am attempting to login with my newly created TP-Link ID but keep getting a notification that the router is bound to another TP-Link ID. I don't believe the item was second hand at all and am a little confused how it could be registered against someone else's ID.

 

I have tried a factory restart three time but am still keep getting the same notification. Is there anyway I can have the router removed from whatever other previous account it appears to be attached to?

 

Cheers

  0      
  0      
#1
Options
1 Accepted Solution
Re:New Archer VR2800 bound to another TP-Link ID-Solution
2022-10-22 10:23:40 - last edited 2022-10-24 04:00:56

  @Jolza 

 

Try if this thread's suggestions will help you to resolve the issue.

If this was helpful click once on the arrow pointing upward. If this solves your issue, click once the star to mark it as a "Recommended Solution".
Recommended Solution
  0  
  0  
#2
Options
2 Reply
Re:New Archer VR2800 bound to another TP-Link ID-Solution
2022-10-22 10:23:40 - last edited 2022-10-24 04:00:56

  @Jolza 

 

Try if this thread's suggestions will help you to resolve the issue.

If this was helpful click once on the arrow pointing upward. If this solves your issue, click once the star to mark it as a "Recommended Solution".
Recommended Solution
  0  
  0  
#2
Options
Re:New Archer VR2800 bound to another TP-Link ID
2022-10-24 04:00:42

  @terziyski 

 

Thanks for the reply.

 

The first thread covered a slightly different situation, but a link within it definitely led me to the right place to get things fixed.

 

Cheers

  0  
  0  
#3
Options