another_user  Freshman Member

the existence of a WAN network dictates that it be 1) NAT 2) towards public IPs In my case they go to a MAN with various subnets with private IP classes (172.16.1.0/24-172.16.2.0/24....172.16.x.0/24) I can't use WAN interfaces, but if I don't use WANs failover isn't usable.

I want redundancy in case the interface (Port 5) connecting an external router (172.16.0.1) goes down, and automatically starts a connection via Port 6 with a second router (172.16.0.2).The 2 routers have fiber connections on different routes.

My mistake, it is 172.16.0.0/12 (not /16) therefore from 172.16.0.0 to 172.16.31.255, it is therefore not a WAN interface but always a LAN (LAN2), I deduce in any case that your procedure does not change and is also functional with LANs.

Many thanks Emily. A last Question, if i want use mschapv2 auth with 2019 server, SSO agent is useful or useless? I found SSO agent downloadable from another link.

Hello at zyxel support team in according to this article -> https://news.softpedia.com/news/microsoft-confirms-vpn-bug-caused-by-windows-cumulative-update-kb5009543-534686.shtml so i report an interesting tip: Microsoft says that customers who must use this VPN connection option are recommended to disable the vendor ID…

When the problem occours ALL IKE VPN's didn't connect with the same error : username and password not correct At this moment i'm writing, the VPN works, but _debug command report error:Join domain: Router> _debug domain-auth test profile-name ad_mschap username &USERNAME password &PASSWORDFailed to join domain: failed to…

Hi Stanley, i have upgraded 13 days ago to the latest firmware 4.65(AAPK.1), for all these days VPN ike works fine, but today the little bug was repurposed for the usual 30-40 minutes, then dissappears. The active directory test, in the same time of VPN error, reports status ok, like in the past. I think that the problem…

Hello Mr Stanley the issues occurred about 30 minutes ago, VPN error 691(incorrect username and password) executed command, with this result: Router> _debug domain-auth test profile-name ad_mschap username correctUser password XXXXXXXXXXXFailed to join domain: failed to connect to AD: Invalid credentials/usr/sbin/winbindd…

Thanks for the fast answer, i will upgrade soon, during a quite period :+1:

very useful, now it works! many thanks!!