Comments
-
Hi @DJHURT1, The junk box would be accessed on a different port such as 10443. You should be able to check this in the Junk Box Summary page in the Anti-Spam section of the SonicWall GUI.
-
Hi @RAGE, Sorry to hear that the speed goes worst when you run the firewall on 5.9.x.x firmware version. Regarding the license sync, yes there are some changes done on the licensing server where firmware versions 5.9.x.x should be able to communicate and 5.8 cannot be due to vulnerabilities found on 5.8 versions. I would…
-
Hi @RAGE, Thanks for trying out the suggestions. May be we have to factory reset the firewall to defaults and perform the speed test with default config present in it. Please take further help on this from our support team.
-
Hi @gmenon, Thank you for visiting SonicWall Community. Yes, settings migration from one firewall model to another firewall model should be supported. To verify the settings import between the firewall models, please check the below KB article to confirm the support.…
-
Hi @Ehsan, Thank you for visiting SonicWall Community. This error is by design as defined by below KB article. https://www.sonicwall.com/support/knowledge-base/error-index-of-the-interface-dhcp-server-enabled-on-secondary-bridged-interface-not-supported/170505364392685/ You may try using portshield or native bridge support…
-
Hi @RAGE, Thank you for visiting SonicWall Community. This seems to be odd. Lets verify what could have caused the issue to occur all of a sudden. Did you connect just a single PC to the SonicWall with every other devices on other interfaces either disconnected to turned off? Since you say Core Monitor is about 83%, we…
-
Hi @JASONMEYER, Thank you for visiting SonicWall Community. If you are replacing the existing ISP on the firewall with new one, once you configured the new ISP the default routes, NAT policies, address objects for the interface IP address gets created automatically. You only need to create address objects, routes or NAT…
-
Hi @DSI_MYAUCHAN, Thank you for visiting SonicWall Community. Since you have performed a NAT over a VPN tunnel, the firewall will consume the packets from IP address 10.45.36.170 and will perform NAT operation to change the IP address to 10.114.3.36 and forwards the same packets over the VPN tunnel to destined IP…
-
Hi @DJHURT1, I guess, the packet is dropped by the SonicWall because of access rule not allowed. You can check for the Src MAC address in the ARP section on the SonicWall to find out which device it belongs to. The MAC address keep changes every hop, so we may not see the right MAC address if there are hops in between.…
-
Hi @CROSSETTI, Thank you for choosing SonicWall Community. Is this issue only specific to windows 10 machine users and HTML5 RDP service? Could you please share the screenshot of the exact error?
-
Hi @mrshahin, Thank you for visiting SonicWall Community. You are facing similar issue as defined in the below KB and the only difference is below KB represents GVC whereas yours is Site to Site VPN. Still you can follow the steps listed in the below KB article but try the steps on your respective Site to Site VPN policy…
-
Hi @Yuber_Sierra, Adding a screenshot for your reference. https://<management_ip>/sonicui/7/m/Mgmt/settings/diag
-
@CLIENT - Please leave the value for TCP timeout to the default 15 mins. You can only change this value after a recommendation from our support team for any scenario. Changing this value may result in WAN to LAN connections opened on the firewall for more than 15 minutes.
-
Hi @CLIENT, Yes, you have found the right article. You should be looking for any reasonable drop packets with reasons as access rule, content filter, etc,., otherwise we are good. Possibly, if you need more help on this part, I would suggest to take help from our support team.
-
Hi @CLIENT, Thanks for explaining. Please try doing packet capture on the SonicWall to understand the reason for the packet drop.