a1601  Freshman Member

I don't have access to that user's computer. I tested it on another computer - in my opinion blocking works: although the program starts and displays a list of messages but cannot send and receive messages. And impossible to connect another user profile. As I understand there is no access to the server. But the user…

Sorry again, I misled you. I found my mistake in the settings, everything works as it should now. Thanks for the help!

Sorry, today my tests are incorrect, because in reality there are problems with the provider for WAN2. I'll check again later.

Ping check for any IP (8.8.8.8, 8.8.4.4 and other) for policies LAN2-WAN2 is fail. Settings: Result (WAN1 and WAN2 works fine, LAN2 going out WAN1):

Yes, everything is described correctly, that’s exactly what I want to do. But for some reason it doesn’t work and I don’t understand why.

But when both WAN1 and WAN2 work and Enable Connectivity Check for policie 5 - it policie is disabled and both networks routed through WAN1.. (need routed LAN2 through WAN2). Connectivity Check disabeled - it works. Pinging another IP for check (8.8.4.4) - it didn't help.

Yes, it works! I created for the device two new rules for WAN1 and WAN2 interfaces, similar to the rules for managing a local networks. For these rules, I created the special service group, to which added NTP, HTTP, HTTPS and DNS (do need to add any other services?). NTP and GeoIP are successfully updated now. Many thanks…

I seem to understand a little. The device has configured WAN reservation through rules, traffic from subnets is normally regulated by them. But the traffic from the device itself does not fall into the existing rules. And the device "does not know" through which interface to send requests. How to configure it correctly…

No. use "User Configured Trunk" (with two members: wan1 and wan2). For testing switch to System_default. Created this rule. When in the next hop set WAN1 - NTP check succeeds.

Hi, No. Still the same error as before.

For extrernal IP - Timeout error. Internal IP (local NTP server) - sucsessful.

If for pinging from the device manually select the "correct" (active) interface WAN1 (two WAN are configured, the second is a backup), then pings from the device is successful. By default (without manual selection) ping goes through an inactive interface. I tried to change DNS settings "Qurey via" from "auto" to the active…

It did not help. Also fails to connect to the ntp server 0.pool.ntp.org (and 2.pool.ntp.org). Access settings, rules, etc. have not changed since the last successful update. I see some internal error in the logs. Ping cdn.cloud.zyxel.com from the local network - sucsessful, but fails from the device.

Try this:

Claudio, this is found from Internet (USG100-PLUS_3.30(AACV.6)C0.zip):