Remote adoption process

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

Remote adoption process

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Remote adoption process
Remote adoption process
2021-09-28 16:00:22
Model: OC300  
Hardware Version: V1
Firmware Version: 1.2.2 Build 20210721 Rel.63283

I keep recieving this device does not respond to adoption requests for the remote adoption process. I use dyndns for the controller address and have the cloud checked and passwords changed. I am moving from unifi and it was always pretty simple. I wanted to use the site to site vpn set up in the controller but I am thinking it is probably best to just hard set the ipsec tunnel and use the controller for the EAP's.

 

Config is as follows

 

OC300 with an ip of 192.168.3.198

Router at main site with 192.168.3.1 with port forward rules to the OC300

 

Remote site 1 - 192.168.1.1

Remote site 2 - 192.168.34.1

 

I ahve the main site up and going, I can see the devices in the controller when i run the EAP discovery but every adopt fails. 

 

What is the quirky process needed to get this to work or should i just set ipsec tunnels and call it a day. I have wasted a good week of trying what should work. Does everything have to get adopted on the 192.168.0.1 range?

 

Thanks

IT Keefus

  0      
  0      
#1
Options
1 Reply
Re:Remote adoption process
2021-09-29 07:40:43

@KBKKeef Hi,I'm not sure if this FAQ can help you to fix the issue.

https://www.tp-link.com/us/support/faq/3087/

  0  
  0  
#2
Options

Information

Helpful: 0

Views: 292

Replies: 1

Related Articles