Ajishlal Community Legend ✭✭✭✭✭
Reactions
Comments
-
Hi @Saravanan Could you please check with the back end team because i have a requirement A/A DPI with sand-boxing implementation. In production environment it's highly required that feature. I hope back end team knows about it.
-
Hi @Arkwright It could be due to false positive alert. Then you have to inform GAV team. As per the SonicWALL signatures, Agent.fl is Trojen virus.
-
Hi @MartinMP Check your ISP modem/router to enable the port forwarding to the SSLVPN port.
-
Hi @MartinMP Check SSLVPN Access enabled in WAN Zone settings.
-
@BWC, For me it's usual behaviour from support, without confirming with the customer they are closing the tickets.
-
Hi @SEBASTIAN Yes. SonicWALL Analytics Management Console provides options for viewing and changing system and network settings, running diagnostics, rebooting the system, and other functions. With ESXi, the On-Premises Analytics boots directly to Management Console. If it's deployed in Esxi please follow below…
-
Hi @Medusanyc The Schannel error due to windows Server update not related with SonicWALL. Cipher suite supported in SonicWALL:
-
Hi @djhurt1 I do have also similar network & configuration as same as below; In L3 switch " Default Routing to the Firewall X0 IP" For example: "ip route 0.0.0.0 0.0.0.0 10.10.55.1" All VLAN's are created in Core switch & not created any VLAN interface in Sonicwall. Sonicwall X0 interface (LAN) configured with…
-
Hi @César_S Try to use the initial release Firmware SonicOS 7.0.0-R906 and observe the SSL VPN issue.
-
Hi @3Wizard This is most likely due to the ISP infra not being to able to handle the load and they wont admit that and instead they will blame on your router/modem or some splitter and replace those, which will not fix the issue.
-
Hi @mastahyo, Enable VPN PASSTHROUGH in your new router.
-
Hi @PhilDurocher Check the WAN interface MTU value as per the ISP. Check the interface duplex mode instead of the Auto Negotiate Check the connected cable / try to change the cable. For testing the PPPoE, Configure the PPPoE connection in a Windows machine and check its frequntly dropping or not.
-
Hi @itworks4me2 For resolving the above mentioned issue, You would have to tag the Firewall VLAN ID (vlan, Vlan99 & vlan301) in CISCO switch appropriate ports then only it will work as per your design. All ports on CISCO switch are in VLAN1, which is default (untagged) and its called native VLAN.