Comments
-
Hello @Trav, Welcome to SonicWall community. Since this website is hosted on HTTPS, without server DPI SSL, we will not be able to see if the client is visiting https://server.com.au/ or https://server.com.au/rdweb. Due to this reason, even if we try to create an App rule, it will not get applied. So, IMHO it would be best…
-
Sure, no problem. Keep us posted.
-
@SEBASTIAN, I found a reported issue where this was not showing on either devices on 6.5.4.5 but that is marked fixed in 6.5.4.6. Have you involved Support team on this? This looks like a new problem on 6.5.4.6 itself. Thanks!
-
@Security_1234, So, physical connection wise, the dotted line is correct. You would then need to go to High availability -> monitoring settings tab and set the monitoring IP for that interface to be XXX.XXX.XXX.251. So, when you put XXX.XXX.XXX.251 on the browser, it will take you to the log in screen for the secondary…
-
@Security_1234, Yes, the physical connections should be identical on both primary and secondary firewalls. Please take a look at the topology diagram for HA environments in the KB below. So, the dotted line in your diagram should be connected and that is how both the device will share a common IP for ISP1. By using the…
-
Hey @Frank76, I am not sure if this will help, but you can give it a try. Please re-import the group from the AD, but when you do, please select the option "No domains (imported user group objects will match the named groups in any domain)" under the 'Handling of the imported user groups' domains:' section Use this group…
-
Hello @Security_1234, Welcome to SonicWall community. When two devices are configured in HA, they have identical physical and logical configuration. So, if X1 is configured with IP1 on the primary device, so will the X1 interface on the secondary device. They share identical IP addresses on each interface. For management…
-
@daniel_lilja, I could not see anyone reporting this or any such suggestion during beta. I would suggest having this raised as a new RFE through Sales. Thanks!
-
@daniel_lilja, Unfortunately, I could not find any useful info on it. I do not see anything listed so far. I can try to find out internally and let you know. Thanks!
-
Hey @daniel_lilja, I have moved it to the right category now.
-
@Alberto, The KB has been modified to show the right command. Thanks again!
-
Yes, I was testing via Swagger directly.
-
Hello @Alberto, Thanks for letting us know. I will reach out to the concerned person and have that corrected.
-
@GAG, Yes, the SSO feature uses NetAPI/ WMI queries to the end machine to find out the username which cannot reach a machine connecting from WAN side. But, good to know that things are working as expected. Thanks for confirming. Have a good one!
-
@abkumar, I actually did try that as well. Even after the successful authorization using the bearer token, I was getting the exact same error. I also tried using any API post that and got "unauthenticated for invalid credentials" as the message. Is there something more to be done after the authorization? Thanks!