Ajishlal Community Legend ✭✭✭✭✭
Reactions
Comments
-
@Corey716 Initial Google Cloud Platform Configuration Create virtual private gateway Go to the Hybrid Connectivity in the Google Cloud Platform Console. Create VPN Gateway. Fill the following details, while creating VPN gateway Name Network Region IP Address Create a Tunnel Name Remote peer IP Address IKE Version: IKEv2…
-
@GX3520 use the SonicWiFi mobile app and try to the device registration.
-
@pendek244 Can you brief about your switches? is it L2 /L3? is there any VLAN configured on the switches / NSa2600?
-
@xdmfanboy High Availability requires additional physical connections among the affected SonicWall firewalls.For all modes, you need connections for HA Control and HA Data. Active/Active DPI requires an additional connection. In any High Availability deployment, you must physically connect the LAN and WAN ports of all…
-
@coooolin, I would recommend SD-WAN but you would have 2 ISP line in each location for the proper solution.
-
@xdmfanboy most probably your old device have only one cable connection in between the units for the HA but when you are doing the HA in Nsa 3700, you would have to configure 2 port for the HA. One for HA control interface and second one for HA data interface. So while using the migration tool, keep in your mind above…
-
@Norsmith Yeah. you will get such information, If you use the SonicWALL Analytics;
-
@dyoderii check the ISP modem configured with any Firewall rule. Check the Modem is allowed to pass the VPN traffic / check the modem is open the IPSec protocol / service.
-
@Midnight , Check your NAT policy as well as the ACL. As well as check your switch configuration. the switport is tag with VLAN. Your clients are receiving the v10/v20 subnet IP from DHCP pool.?
-
@Talash if you dont mind share with us the configuration what you done and let us know the server side have any firewall / policy?
-
@SonicBoom , You can add VLAN subnets in existing in site to site VPN.
-
@BWC Fyi, Published one internal service and its accessible from all location except 1. When ever I am trying from that location I am getting the above drop code. Its really weird and confusing me. This published service and don't have any rule for location based / IP based.
-
The current Firmware is SonicOS Enhanced 6.5.4.10-95n & its in production environment.
-
@MustafaA Its not about the ACL. I will explain the scenario; Published one internal service and its accessible from all location except 1. Previously the same issue happen at that time configured the source WAN interface (from where we published the Service) with "Enable Asymmetric Route Support" and helped me to resolve…
-
Yes bro me also using another vendor product. recently i did a project with 80+ AP. As well as cost is another concern.