MustafaA SonicWall Employee
Reactions
Comments
-
Please create a web case and reference GEN6-3898 so that we can share the HF build firmware, which has the fix for this issue.
-
@billmayer , please check the scanned port that is associated to the report? Do you have any port forwarding for that? Also, please ensure the report is for the correct firewall. Trust me, I've seen such mistakes, and not limited with few. Otherwise, create a web case and attach the Scan Report, TSR, and EXP files to be…
-
@Dev , it looks like you have an active connection from the Capture Cloud Portal. This is not a browser issue for sure.
-
Option 1: If you are not using either HTTPS or SSLVPN, then simply disable those services. Option 2: Don't leave access to the HTTPS Management and/or the the SSLVPN Ports wide open. Use WAN to WAN Access Rule to limit based on source IP addresses. If you have remote users utilizing SSLVPN and they have changing public…
-
@billmayer if you are referring to the CA (Certificate Authority), as the Provider, all you need is the CSR (Certificate Signing Request), which can be either generated on the firewall or with third party tools such as OpenSSL, PowerShell etc. If you are referring to something different, please clarify and share more…
-
@Gandhi , can you please share more details about the firmware, and which API sequences you are using? After change commit, when you run GET Request, do you see the object you added?
-
Have you tested the following two signatures? (App Feature Video 1&2)
-
@Andy_357 , I am glad it is resolved now, happy to help you 👍️. Please highlight as "Correct Answer" so that others with similar issue can benefit from this.
-
Policy Drop indicates that the issue is related to the Access Rule. Have you enabled "Allow Management Traffic" on the respective VPN Access Rule?
-
@Seafront90 , your issue appears to be already reported and our engineering team is working on a fix. Please create a web case and reference SMA-4165 so that your logs can be further analyzed.
-
I would suggest to discuss your current and future requirements with a SonicWall partner in your area to identify the right model. https://www.sonicwall.com/partner-locator/
-
@johncrowe , some of these IP addresses are associated to AWS EC2 instances. Have you looked at this issue from that perspective? You need to understand why those destination IP addresses are sending RST packets to terminate the TCP session. With the current limited information, I don't think this is a firewall issue.
-
@Sam168 , can you please share more details? What is meant with "smoothly"?
-
@HMC, here is an example. The asterisk on the ingress and egress interfaces indicates where the packet was captured. Moreover you can see that the IP address 192.168.168.100 of the host computer is translated to the IP address of X1 WAN interface which is 10.61.12.145 and the packet leaves the firewall on X1.
-
@HMC I'd suggest to utilize Packet Monitor, and capture the traffic flow based on the destination IP address only which will give you the original source IP and the translated source IP addresses.