TKWITS Community Legend ✭✭✭✭✭
Reactions
Comments
-
Are both the server and switch set to Dynamic LACP?
-
What is listening on TCP port 853 on the Sonicwall? Nothing, which is why it is dropped.
-
I would recommend against bridging interfaces especially with wireless involved. Sonicwall firewalls are a firewall first. Bridging / switching should be left to dedicated devices (it adds unneeded complexity to already complex firewall configs). I also dont use wireless models / Sonicpoints / Sonicwaves for the same…
-
If your support is expired you can still perform firmware upgrades. I would recommend step-upgrading based on "general releases" and release dates to the subversion you want (e.g. going from 6.2.5.x released 11/2019 to 6.5.3 released 02/2020), then you can go to the latest version. Again, as long as you can download the…
-
Office 365, but not for OTP as we prefer TOTP, for sending emails from the firewalls.
-
Is the remote side aware of the SSLVPN Client subnet? Run a packet capture to see where the traffic is ending up...
-
SD-WAN is not strictly for Sonicwall VPN connectivity. The link ARKWRIGHT provided actually highlights all of its features which shows it is not limited to 'substituting MPLS connectivity'... the top two features listed are Application-aware routing and Dynamic path selection based on Latency, jitter, and/or packet loss.…
-
Maybe @jgrimes has some input?
-
Contact support, or connect to the console port of the AP and see what you can get out of it. I do not know if it dumps to console or not. This might help: Disclaimer: I don't use SonicPoints.
-
Have you tried rolling back to previous firmware?
-
Documentation is all over the place, but I've always gone by the rule that 3rd Party Certs are required for VPN tunnels. FIPS is generally outdated anyway, but obviously serves a purpose. From the U.S. government:
-
To expand what JGRIMES said: What you are seeing is what the IPS engine is reporting as evidenced by the 'description'. Technically, an echo-reply is not an 'attack', the IPS engine is just identifying it as such. You can either configure the Sonicwall IPS feature to not log echo-reply's as attacks, or tell the SIEM to…
-
@jgrimes
-
Enable SSH on an internal interface and when things start getting weird see if you can still get in that way. Not surprised support hasn't helped, did they even send you this? Connect a console cable and gather the output. Unfortunately it is now up to you to do the in-depth troubleshooting.
-
Once again, things like this are why I recommend to NOT use the migration tools.