EAP 225 cannot be adopted after firmware update
EAP 225 cannot be adopted after firmware update
My EAP 225 cannot be adopted after updating from 5.0.5 to 5.0.7
All previous firmware upgrades of my EAP225(EU)v3.0 have been successful.
EAP is accessible.
I have opened the ports 28910-28914 as per latest instructions.
Hard resetting the EAP 225 (running firmware 5.0.7) and making all configurations again, did not help, too.
I have reverted to the previous EAP225 firmware (5.0.5), then EAP225 (running the old firmware 5.0.5) is successfully adopted again.
Seems that reverting to the old firmware is the only solution for me until now...
I suppose we should wait for the next firmware update to solve the problem ?
I hoped that latest firmware upgrade of the OC200 controller would solve the problem.
But unfortunately, nothing worked.
PS : Exactly the same problem occurs with EAP245(EU)v3.0 in my office. I am going to visit the forum for EAP245, too.
IMPORTANT : Both EAP225 and EAP245 communicate with the OC200 controller via the internet, as OC200 is in headquarters far away from here. Not a single problem has been ever occurred in firmware upgrades until this one.
Thanks a lot in advance.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
there is almost 100% firewall issue, double check that TCP 29814 is open. you can use telnet from remote network to test,
run cmd in windows or other telnet application, mybe you ned to add telnet services in add remove windows function.
telnet xxx.xxx.xxx.xxx 29814 if it answers it is open otherwise the gate is closed.
- Copy Link
- Report Inappropriate Content
@shberge thanks a lot for your answer ... probably it is closed, I get this reply
Connecting To .... Could not open connection to the host, on port 29814: Connect failed
Is there a port forwarding issue ? How can I fix the firewall ? And how adoption is possible using the previous firmware ?
Thanks again.
- Copy Link
- Report Inappropriate Content
You open the ports in the same way as you have done on the other ports, if you have an omda router it is quite simple, but these are different ways to do this on the different types of firewalls, what type of firewall do you have.?
And adopt port is changed in new firmware on device to work against omada 5.x software.
- Copy Link
- Report Inappropriate Content
@shberge Ports 29810-29814 were open fron the beginning, I have been aware of that. I am using TP-LINK OMADA ER-605 routers on both sites (headquarters and branch), each of them behind a ZTE-branded VDSL modem-router (provided by my ISP, otherwise I cannot connect to internet).
I have never made port forwarding in ER-605 router.
I have only made it on ZTE one and it works perfectly with the previous firmware.
I don't know what kind of firewall are on ZTE, it just has 3 settings (High - Medium - Low level of protection). Regardless the firewall setting, telnet command has always negative result, but (using the old firmware) EAP225 works perfectly and gets adopted by OC-200 in our headquarters.
Please note that all are functioning properly as long as old firmware is running on EAP225. That keeps me thinking that it is not a matter of port forwaring and/or firewall, but another kind of issue.
I would appreciate any further help, best regards.
- Copy Link
- Report Inappropriate Content
On ER605 its port forwar prety simple
Create portforward like this.
And ZTE can i dont help you with, I do not know these forewall.
Anf how you have get it to work before without port forward in you ER605 is a mystery.
- Copy Link
- Report Inappropriate Content
@shberge Thanks a lot for your efforts. But following the above orders was a complete disaster. All devices in branch office have been disappeared. Even after restoring old firmware 5.0.5 on EAP225. Even ER-605 router/gateway of branch office has been lost.
OC-200 (in headquarters) cannot discover anything.
Please note, that (unlike what I have mentioned above) router ER-605 had been configured indeed with port forwarding, but only 29810-29813. Probably I was not remembering it.
Unfortunately, although (I am using auto-backup on OC-200) I reverted to all previous settings, nothing is now fixed.
I am trying to find out what's wrong now.
Please note that on "controller URL" setting on all devices (before adopting them by OC-200) I always have been inserting my DDNS address (I have no static IP from my ISP). The whole problem could have been caused by DDNS address not being updated promptly (so not a single device could reach destination in HQ by using a DDNS address).
But I have double-checked with "no-ip" (my DDNS provider) that IP address is accurate and updated.
Ι would appreciate any kind of help.
Thanks.
- Copy Link
- Report Inappropriate Content
ddns and no ip is usual not a problem.
send som screenshot of your port forwarding configuration, what you dealing with no is usual not a problem when all the port is forwarded to correct device.
and I hope not you use 192.168.30.7 as destionation, use you controller ip in destination field.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@shberge ΟC-200 is 192.168.0.190 [reserved by DHCP and permanently there].
this is the configuration in our HQ
Thanks a lot for your efforts
- Copy Link
- Report Inappropriate Content
@shberge when I am sending ping from PC of branch to HQ IP address has no answer. Is this normal ? I have no other idea to test the connection, it seems lost.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 1953
Replies: 14
Voters 0
No one has voted for it yet.