Comments
-
Device VPN is real always-on. It is connected even window user does not login to windows after cold boot. Network logon I don't think its always-on, they are different stuffs.
-
Those websites need public A record, not cname or alias. With correct A record, CT will add the public IP to client route table and route to SMA.
-
You can uncheck these, its enabled by default.
-
Issue already fixed.
-
DNS (Name Service) is a group which include DNS (Name Service) TCP AND DNS (Name Service) UDP. In most cases, allowing DNS (Name Service) UDP would be good enough. Majority still using UDP for DNS. DNS (Name Service) UDP = UDP Port 53 DNS (Name Service) TCP = TCP Port 53 DNS (Name Service) = TCP 53+UDP53
-
Yes, it already dead for few days. All firewalls got this but no one gonna fix it. Its sonicwall backend issue and wont affect devices operation. Just ignore it and hope sonicwall backend will fix it within 1-2 months.
-
@BWC If you plugin console & boot compare 3700 & 4700. You will find different processes ran during boot up. High end products definitely have some "on top design" over SMB products.
-
It seems only available for high end models. (Start from NSa4700) The core design is a bit differences between high end & low end products. Like the previous SM9800 with multi chassis. Maybe the the high end product is running like Linux kernel > docker container > SonicOS? So you can restart docker image without restart…
-
the file should be encrypted by SonicWALL Dev. Don't think we can extract it without SonicWALL Tech.
-
@BWC Yes, you are right. SMA 12.4.2 connect tunnel works with MacOS(even M1).
-
Upgraded to 12.4.2 for testing, the new features are great. But I am not sure about the stability as I am not heavily use it.
-
NSa2700 should have secondary storage built-in. Remember to enable it. By default, logs are not store to secondary storage.
-
you mean this page? SMA need to download them from sonicwall cloud first. so maybe wait 1-2days after update.
-
Not sure about your case but it seems working on test. 192.168.50.40-42 to 10.10.99.40-42. As it has identical range, it should map 1 by 1.
-
Actually, we dont know that you are trying to achieve. the document, expect the wording " OBJECT | Match Objects " (should be address objects). Others should be correct and it has screenshot.