ER605 Port Forwarding will not work under Omada Software Controller
ER605 Port Forwarding will not work under Omada Software Controller
This is a continuation of my previous thread, as seen here:
https://community.tp-link.com/en/business/forum/topic/622434?replyId=1254500
Some personal issues that meant I had just lived with this not working, but I am now back to trying to solve the issue.
The Router works perfectly in standalone mode only.
As soon as it is adopted, I am unable to open any ports.
I have confirmed the server in question does not change IPs when the router is adopted, the server has been manually configured to take the ip 192.168.0.30 and not to use DHCP.
I have since updated my controller to the latest software (v5.13.30.8) with no change in the situation.
Multiple factory resets of the router have been tried.
I have tried opening ports to other machines on the network, which again works perfectly in standalone mode but fails utterly post adoption.
I have also noted that when adopted despite configuring it the router also fails to update its No-ip DDNS, while this works perfectly in standalone. From this I suspect that the controller is somehow failing communicate the settings to the router, but that's just a conjecture.
All the issues are reproducable 100% of the time on my network, I can restore everything to full functionality simply by having the router in standalone mode and it will all fail every time as soon as the router is adopted. Happy to provide any screenshots or logs that could help diagnose these issues.
Please help.
All the best,
Tom
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Tyra oh jeez!! Thanks for the heads up... 
- Copy Link
- Report Inappropriate Content
Hi @michae1m
Thanks for posting in our business forum.
michae1m wrote
@Tyra I have done the same, which seems to have resolved the port mapping issue. Time will show if it also has resolved the problem I had with the er605 periodically getting stuck in a pending state.
Do you run a V1 ER605? If so, that's normal as the overall hardware is not as good as V2. That's also one of the reasons that V1 was discontinued and stopped adding new features. It would lag a little bit when syncing the configs from the controller.
- Copy Link
- Report Inappropriate Content
yes it is v1 hardware - unfortunately I didn't know there was a difference to look for when I bought it and online it is often very difficult or impossible to tell which a retailer is selling.
- Copy Link
- Report Inappropriate Content
I have same issues.
ER605
Controller oc200
After a fresh install cannot configure the port forwarding. I do it in the Omada after adopting it succesfully the gateway but still I cannot have access towards the server. Configuration seems ok on Controller side but not performing on gateway side. I tried the simplest approach with DMZ also, not works. The only thing I must do is to configure on another network 192.168.xxx.1 instead to default 192.168.0.1.
Stand alone configuration on ER605 with port forwarding and ACL is ok and works, by adding An virtual server and filtering the client access only for some ip range.
I tried multiple times. more badly the menus are different on Omada controller related to gateway than on gateway itself a bit confusing.
- Copy Link
- Report Inappropriate Content
Finally and for the record. I reset all devices again, started from scratch with default IP and then switched the IP to match with my network. This was messier. Also upgraded the Gateway to 2.2.6 and seems working now.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1035
Replies: 15
Voters 0
No one has voted for it yet.