About randrade86

randrade86 · 04-17-2018

We have a RV325 (192.168.63.1) router behind our TP-Link router (192.168.0.1), in a pretty simple setup. RV325 is also the DHCP server. Everything works great except that no device in 192.168.63.0/24 is accessible from outside (Internet). We forwa...

randrade86 · 12-04-2019

My unit was faulty. I bought an used Fortigate router and it worked flawlessly. We retired our Cisco RV325.

randrade86 · 05-03-2018

Thanks for your reply. That's exactly what I have tried since the beginning. I even tried to factory reset my router and the problem persists. Unfortunately, looks like my unit is faulty.

randrade86 · 04-20-2018

We disabled 192.168.63.2 firewall entirely. When we had only the TP-LINK router, it worked flawlessly. Due to business reasons, we needed to add a VPN Router with Site-to-Site capability hence we bought a RV325. VPN Site-to-Site is working great so...

randrade86 · 04-20-2018

Yes, I tried to set the firewall to the most permissive mode ever (allowing any traffic) or disable the firewall. In my KIWI SNMP log I see the RV325 ALLOWing traffic but the port remais closed. So looks like something "inside" RV325 is still block...

randrade86 · 04-20-2018

Hello, That didn't work since PAT's Service Management is separated from Port Forwarding Service Management. Here is the Service Management for PAT: And here is the Service Management for Port Forwarding. In this window, you can't forward ...

Member Since	‎04-17-2018 04:23 PM
Date Last Visited	‎12-11-2019 05:37 AM
Posts	7

User Statistics

User Activity

RV325 - Port forwarded but still closed

Re: RV325 - Port forwarded but still closed

Re: RV325 - Port forwarded but still closed

Re: RV325 - Port forwarded but still closed

Re: RV325 - Port forwarded but still closed

Re: RV325 - Port forwarded but still closed