BWC Cybersecurity Overlord ✭✭✭
Reactions
Comments
-
Hi @InfiniteCo in my experience only a single user session can be active on the Firewall from the same IP, in your case the remote WAN IP. It's either GVC or MGMT, you have to choose wisely :) --Michael@BWC
-
Hi @David W I guess it was you answering to my ticket a minute ago. It's not just gmx.de having the issue, my customer sent a message to online.de (which is handled by United Domains) and the problem still persists (outgoing). =?iso-8859-1?Q?.2021?= Hostname is ams0vm-hesra06.colo.sonicwall.com Originator is abc@abc.de…
-
The Private build I've got for my Radius thingy already contains OpenSSL 1.1.1k, so it's in the works. @Micah , in case someone asks. Next stop, dedusting the rest of the system. <fingerscrossed> 🤣 --Michael@BWC
-
I've got a private build today 10.2.0.7-34sv-SMA2517v1, unfortunately it's not working, it asks for the first time ever for the OTP, but crashed then with a "Server is currently unreachable", the TSR shows some exception of a Python Script. But it was the first try, after all these years I hope for the best. --Michael@BWC
-
Ticket #43666998 (United Internet comains) got escalated, status.sonicwall.com does not show anything. Thank you for contacting Sonicwall support. We have escalated this issue and escalation team is working on it. We will keep you update with further details. You can subscribe on status.sonicwall.com to get latest updates.…
-
We hope for the worst and fear the best, or was it the other way around? 🤪 --Michael@BWC
-
Just in case the support "never" heard about the problems, I opened Case #43666998 about the United Domains dilemma, and Case #43667007 about the incorrect configuration of the zone snwlhostedeu.com with a non resolvable NS for sjl0vm-heswd01.colo.sonicwall.com, which might cause problems resolving your own MX or HES…
-
Hi @THK, hard to tell, the inability of your MSX sendconnector resolving the HES host is surely related to the DNS misconfiguration at SNWL. The 1&1 thingy I can't for sure. GMX is also using the United Internet infrastructure, so it's related. It seems that the SNWL resolver used by HES is not able to get the job done…
-
Hi @THK, I totally overlooked your post, having the same, sorry for the double post. --Michael@BWC
-
Hi guys, maybe this is related, because HES customers reported about problems sending mails via the HES outbound gateway. It seems like a DNS misconfiguration. On SNWL's end because one of the authoritative servers can't resolve, whichs results in consequential problems resolving the HES outbound server name for example.…
-
Just checking, anything new on this? --Michael@BWC
-
Hi @Larry I'am not aware of a KB article which covers this topic, but maybe this helps, you should stop at step 2 :) --Michael@BWC
-
Hi @JanSkod a flow diagram or Judgement Order would be great to have, count me in. If I get you right, you have an Access Rule which blocks from/to specific addresses and another Rule allowing from/to specific addresses? The blocked packets got also blocked because of GeoIP? Did you configured your Allow Rule to consider…
-
@RyanS that's an unfortunate situation, SentinelOne provides a cleaner tool and SNWL as well, it seems a bit tailored though. Maybe @SuroopMC can help out here, because this will happen not for the last time, that a Trail License got lost in the process and an Agent cannot be removed via Management UI. Their should be a…
-
Hi @shultis it's at User Access -> End Point Control -> General (click on 1st Edit) --Michael@BWC