Comments
-
I am having this issue with a TZ105. Does someone have informations whether the latest firmware will help or if SonicWall will resolve this issue for this model? Also I am struggling with the generation count of the TZ series. The only resource I found was the link below. Is this according to the official way of counting…
-
Does anyone have a clue whether there are TZ models and/or SonicOS versions that are not affected by this?
-
Thank you for your answers. Highly appreciated. @BWC "some form of Modem for DHCP" Do you think a static IP on x1 could solve this? I will try immediately.
-
I have 5018 running with about 4 weeks of uptime and this issue is gone so far. I will keep running 5018 for another month or so. @César_S and @EAnderson_SN were also affected as it seems in this thread: https://community.sonicwall.com/technology-and-support/discussion/comment/8785 Maybe one of them has seen the issue with…
-
We have tried many many many things now. The only way that brought us one of the tunnels back to work was a downgrade to R1296, deleting a tunnel and creating it again. The other tunnel is still not working properly, for reasons we don't know...
-
Thanks a lot @TKWITS In fact when I change the Peer ID of a working tunnel, I get pretty similar results. We will to talk to the people managing the 3rd-party firewalls.
-
Are you sure there is a firewall rule allowing Management? On SonicOS 7 check your firewall rules (probably LAN to LAN [if the subnet your workstation is in belongs to the LAN zone]) => Edit rule => optional settings => tick "Allow Management Traffic" In SonicOS 6 and before the setting is directly in the window where you…
-
Dear @A_Elliott Thanks for your message. I can only find the following in the release notes: GEN7-22807 Client connections consistently fail with "Timeout" log messages when attempting to connect to a firewall with SSL VPN Server enabled. But this is under the "Known issue" section of the April 2021 firmware. Did you find…
-
Hello @EAnderson_SN Thank you for your message. I have installed the latest Firmware 7.0.1-5018 recently. There was nothing mentioned in the release notes, so I have little hope that the issue is fixed. I also had this Issue at a customer's site once, but in our office it happens more much often. I don't know but it might…
-
Thank you. Support asks me: "do you know which Hotfix you need, do you have any reference number" can you help me
-
Thank you. I can not find any further reference or information about GEN7-21234. Do you have any details? IIUC GEN7-21234 is resolved in SonicOS 7.0.1. How can I be affected then? https://www.sonicwall.com/techdocs/pdf/sonicos-7-0-release_notes.pdf
-
I also tried changing the port to 4434 and back to 4433 and switching the SSL Server WAN Interface-Button off and on. Only the restart of the sonicwall would resolve it.
-
Hi @Ajishlal I know this works when using only one entry in the list of DDNS. What does NOT work is having two DDNS entries, one for X1 and another fo X2. I need this because both Interfaces are connected to external modems. It seems to interfere with my Failover policy which prefersx X1 over X2 when connecting to the…
-
Dear @Ajishlal Thanks for your response. In my scenario, I have different external modems with dynamic behind X1, X2 and X3. In order to connect to these Interfaces from the Internet, I absolutely need the "Bound to" setting to work in any of the Failover-Settings. This was working perfectly fine in SonicOS 6.5 and before…
-
I can confirm this exact problem between pre-Gen7 and Gen7 firewalls.