Comments
-
If you are trying to use one tunnel between one location on say sideA and multiple locations on sideB, that is never going to work. A VPN tunnel is point to point. If you are trying to create a VPN tunnel between pointA and pointB and say pointA has multiple WAN connections, you would configure the VPN tunnel with one or…
-
I was able to install and have confirmed that 7.1.3-7015-R4056-HF51903 does resolve the problem. Sonicwall is still working on incorporating the HF into a public release.
-
FYI, Sonicwall has provided me a HF to test on the NSA2700 we have. Unfortunately I may not be able to apply that until Saturday morning 02/01/2025 as it does not rise to URGENT PRIORITY as doing so will momentarily disrupt company communications.
-
Upgraded from 7.1.1-7058-R3569-HF49799 Yes, even after the reboot, the unit is using a self-signed certificate with the name of the X0 IP even though the management certificate chosen is a custom-specific certificate. And yes, that certificate does show validated under the certificates display list. This problem is also…
-
OK, this is more evidence that Sonicwall Support is a bunch of lazy people. I have a case open on this since 05/27 and so far the assigned support person asks for more information. HELLO, the information is right in front of you. Not one effort has been made to escalate this to someone actually capable of understanding the…
-
UPDATE: Apparently, this is caused by the resulting DNS lookup have more than one A record. I have a support case open for this. One had to be done was create an FQDN address object *.sharepoint.com and then create a firewall rule to block that as a destination. That is stating is simply. It is a lot more complex which I…
-
That really does not help at all, as blocking everything there will also then block other Microsoft services.
-
Sorry for the long delay. Other things have been keeping me busy. The HTTP service rule is working as intended. The problem is HTTPS is not catching anything. Below is the HTTPS rule which is not catching anything. The comparable HTTP rule is catching. So I tried changing to a custom rule and THAT is not working either.…
-
The Regex expression you listed is not usable, as it is extremely wide open, meaning it catches things such as http://www.google.com/mysearch/6225432.5245235234.5254325.54252.542522 The reason I had originally configured it with https? was to prevent the above. There is no such "HTTP Access" on a NSA2600 6.5.4.6-79n. Here…
-
I also find it funny that I am labeld as a NEWBIE. I have been working with Sonicwall firewalls since the days of SOHO2 SOHO3, TELE3 and PRO100. I was an active member of the original Sonicwall Forum as well as the third party Sonicwall forums. I as an active member when Sonicwall changed to a new forum software and had to…
-
Yes, that is what I am trying to do. So for example a user does a Google search for widgets, and on of the websites is actually http://10.10.10.10/default.htm I want to be able to block that.
-
No sorry that does not help. I know very well how to create address objects and so forth. That is a manual process to be added AFTER THE FACT. I need to be able to block users from accessing IP Based websites at the time of attempt, not later.
-
Unfortunatly there is an issue in 6.5.3.x that we were experiencing that required us to go to a newer version per Sonicwall support.
-
Thanks
-
I realize it "should not matter" but I am working on resolving constant events being logged in the Windows Server application log concern certificate mismatch. I wanted to make sure before investigating that problem that it was not somehow caused or tied to different cipher suites being used.