TKWITS Community Legend ✭✭✭✭✭
Reactions
Comments
-
Larry is right on what support recommends, but that's not what their marketing dept. says. 'You choose which firmware is right for you...'
-
See the discussion here and come back with questions. I dont think 'TCP sequence randomization' has anything to do with your issue. https://community.sonicwall.com/technology-and-support/discussion/comment/18299
-
Did you read up about this 'attack'? Most likely nothing serious, and possibly routine 'reconnaissance' of an automated type (think Shodan or webcrawlers). A few of these packets are not unusual to see every other year or so in my opinion / from experience.
-
Try using the individual address objects for X0 and X3 subnets in the SSLVPN Client routes. I have seen where groups aren't dealt with properly.
-
To understand what it is that is happening, read up on TCP handshakes.
-
Per Microsoft's own documentation, you need to allow any Teams traffic through your equipment unrestricted.
-
Reboot
-
Do you have consistent downloads from other services? https://help.wetransfer.com/hc/en-us/articles/208163506-The-download-speed-is-slow
-
What firmware are you running? Do you have bandwidth management applied? Have you tried changing the Sonicwall to SPI instead of DPI?
-
I know its not ideal but try using the Global option on the access rule rather than Custom. See if that actually applies the restrictions. I never use the Custom option. What firmware version are you running? Always provide that info in your posts.
-
No idea, haven't used NSM in almost a year.
-
There have been discussion here about NSM before and many of us agree its not worth it for small to medium business customers. Think though, if you have a contract to manage all the firewalls for all McDonalds locations in your state...
-
Example FQDN: vpn.whatever.com Internal DNS server would require whatever.com as a controlled zone, and a 'vpn' A record to point to the internal IP address of the interface on the Sonicwall that would be connected to (e.g. LAN 192.168.200.1). External DNS server that controls the public whatever.com zone requires a 'vpn'…