NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
BR200 not "currently" working with existing OSX Server VPN
Hello America, I hope you are all well. After 9 years of using an Apple Airport Extreme as a router in addition to 3 other Extremes being used as access points, we decided to upgrade our router t...
Hello,
The port forwarding rules appear to be correc as the traffic would hit the IP ending in .225.
IPSEC is it's own VPN however the BR200 only does site to site IPSEC and you cannot use it as a client to site solution. What resources are being accessed on the Mac server that is needing to be accessed remotely? Do you know if you are able to access the resouces locally?
Hello,
Is the Apple Airport Extreme still functioning as a router?
IE: Devices still connecting to the Airport, and the Airport routes the traffic out to the BR200? or is the Airport only functioning as a VPN to the devices that are behind the VPN?
Do you have a screenshot of the firewall rules and how it is setup that you can send me?
Thanks for the reply,
The BR200 router replaced our trusty Apple Extreme. We turned the old Extreme into an wireless access point set to bridge mode, so it was retired as a router. But the old Extreme as a router was set to pass through VPN's 3 port's with IPsec enabled on it, as a one-click button option, and VPN always worked.
We set up the BR200 for DHCP with many DHCP reservations and it fired right up, and offered the correct IP addresses to all of our devices. We then created port forwarding for AFP 548 and VNC 5900, which instantly worked over the internet. Then we turned our attention to VPN using OSX Server which was already on.
I attached our Port Forwarding rules. In the case of ports 500, 1701, and 4500 needed for VPN. The BR200 presented errors when "editing" the VPN rule with all 3 ports separated by comma's, like I always used to do. So I separated the rules for simplicity and if anything to name them properly. VPN on OSX Server logs shows it is in listening mode. Public and private port scans shows these ports not open.
Wondering if IPsec is the issue, not that I understand what that is? Or is this a DNS issue which we do not quite understand either, but we have a Netgear DNS account if we need it.
Thanks again for any troubleshooting ideas, really appreciate it....
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
