Michael_Bischof SonicWall Employee
Comments
-
@andreseriverab Can you please provide some more details, e.g. -App version -Firewall firmware version -Network infrastructure -Project target -etc..
-
Version 10.2.322 was recently released and should work for Win11
-
The drop code information can change with every new firmware version and is meant to be for engineering. For now, we do not plan to release information detailed to drop codes. The important information in an packet drop found in the packet capture points to the engine rather than the reason as it is more important to know…
-
Looks like you found a bug. Please forward this to our team using mysonicwall.com and open a ticket so our engineers can take care of this... Smart-Ass ;)
-
You need to add network interfaces to your virtual firewall. Have a look at page 21: https://www.sonicwall.com/techdocs/pdf/nsv-7-vmware-getting-started-guide.pdf
-
This could be related to the TLS version your SMTP server is forced to use and by the current NSM version you are using. Please open a support ticket on mysonicwall.com and let our team have a look into this.
-
Without DPI-SSL, CFS (Content Filter Service) cannot look into sub-domains, e.g. sonicwall.com/news Using DPI-SSL will also help you display the sonicwall CFS block page on https sites and make security services on the firewall way more efficient, but at the same time it will impact the firewall performance and throughput.
-
@Larry Depending on the browser-version and browser-addons the 20sec loop may go forever. Best practice is still to ping the firewall IP and wait for an reply.
-
@GrahamBarnes Please open a support ticket on mysonicwall.com and note in the ticket to have it assigned to Michael Bischof, add the URL to this community post in the support ticket and I will dig into this and let you know what we can do.
-
A firmware update can take around 5 to 10 minutes, depending on the model and if the firmware update is done on an HA pair. On Gen7 firewalls, it can sometimes look it's still rebooting even if the reboot has finished because of the browser still counting down. I would suggest running a continuous ping to the firewall IP…
-
These seem to be FQDN address objects that cannot be resolved by the firewall while using the current DNS servers you configured on the firewall. The reason for that could be that the DNS servers which are used do not know these domains, that these domains do not exist any longer, or that their domain names have changed.…
-
Here is an KB article for Gen6 firewalls that describes how to modify the firewall login page: And here is an KB article for the SSL-VPN Virtual Office login page customization: For Gen7 firewalls, only the "Pre-Login policy banner" is customizable for now.
-
In that case, it is the best you open a support ticket, so our team can investigate on this behaviour.
-
Since the firewall is blocking the attack, there should be nothing to worry about. Still, your GEO-IP filter should drop the incoming connection even before the attack is happening. Please make sure you configured your GEO-IP filter correctly: