Ajishlal Community Legend ✭✭✭✭✭
Reactions
Comments
-
@Aldo Are you tried with distinguished name? as same like as below screenshot?
-
@sdeyoung You cannot import/migrate the configuration from 215 to 370. For more info, please see the below support matrix;
-
@Solidata may be a stupid question, Did you enabled the CFS Policy and source and destination is LAN to WAN?? If its enabled, try to create/Add new CFS Profile & CFS Action and add new policy and attach it and try. (Disable the default policy, Profile & Action).
-
@ThK Set a higher UDP Flood Attack Threshold (UDP Packets / Sec). The default value is 1000. Based on your environment you can increase this to 5000 or 10,000 and test what works for your setup. Follow below KB
-
@Chamil The latest general release is stable SonicOS 6.5.4.9 (6.5.4.9-93n).
-
@Simon_Weel add the wildcard domain name. *.sonos.com, *.radiotime.com
-
@reynold85 Make sure you blocked the Hacking/Proxy Avoidance Systems category in CFS policy.
-
@Blacksuit As I understood that, you have 2 domain users and they are in different VLAN and you want to bypass their internet traffic through the dedicated firewall for each domain. If this is the scenario, You have to do some configuration in your Core Switch. First you have to create a default route in the core switch…
-
@vhduran For best practice always segregate the Wireless managment subnet and users SSID subnet separately. Most of the Sonicwave hanging issue I noticed due to the IP conflict with the clients.
-
so you mean NSM is the culprit :) Good luck
-
Is this configuration correct?, Or do I have to create a "Address Group" including this "X0 Subnet" 172.21.18.0/24 and the virtual "New Subnet" 172.23.128.0/28? --> X0 Subnet is fine. 1.5) I hope the above solution will help you to resolve your pblm. NB: The challenges is I mentioned above, as per the virtual subnet you…
-
Check the object is added / used in VPN policy or check unused ACL rules. (VPN->LAN - LAN->VPN)
-
@sluque Yes it is possible. Before we start make sure the below option is available in your existing VPN policy. If its not available required to upgrade the firmware. For your above scenario, we required to MAP your X0 subnet to new subnet 172.23.128.80/28. Step 1: SITE A Configuration (NSA 3500) Need to create a address…
-
@MLeger Increase the both end life time 28800 to 86400 and observe the behavior.
-
Hi @Larry this could be happen if the interface duplex is not matching with the other end device. Or it can be a cable issue. I faced the same issue due to the duplex mode. Once I changed Firewall interface link speed to 100Mbps full duplex the issue has been resolved.