MustafaA SonicWall Employee
Reactions
Comments
-
Since this is not a local user on the firewall, rather an AD user account, you should review AD Password Policy.
-
Yes, nothing else should be required.
-
As of Sept 14th Mobile Connect 5.0.15 for iOS platforms, which has the fix, is available on the App Store. https://apps.apple.com/us/app/sonicwall-mobile-connect/id466931806
-
First and foremost, please ensure that your SSLVPN traffic coming from the public source (initiator) is reaching the firewall. You can utilize Packet Monitor for this purpose and filter traffic based on the configured SSLVPN port.
-
For the CSR creation, there is no option for the Signature Algorithm selection. This is a screen capture from a SOHO device running 5.9.2.14. TZ200 firewalls were end of life back in 2018, so your firmware must be quite old also.
-
Yes, you can do that. You have two options: You can RDP to your internal server by configuring Port Forwarding on the firewall and restricting access based on a single public source IP with the Access Rule. Second option is to use client VPN such as Mobile Connect using SSLVPN or GVC using IPsec and RDP to the internal…
-
Yes, that is correct.
-
You should only require to change the settings on the X2 interface. It should not affect anything else, since you are not changing the WAN interface to another physical port of the firewall.
-
@gyalpo , can you please consult with your firewall admin if the NSv is deployed in Classic Mode or Unified Policy Mode? The Access Rules are different for those two modes. The tests I performed is on an NSv in Classic Mode.
-
Hello @SYSADMIN , We have the following KB article which should give you clarification. KB: How to Restrict VPN Access to SSL VPN Client Based on User, Service & Destination https://www.sonicwall.com/support/knowledge-base/how-to-restrict-vpn-access-to-ssl-vpn-client-based-on-user-service-destination/170505907430135/
-
Only one user will be able to connect at a certain time, due to one node license. Firewall will not allow multiple login sessions with same credentials at the same time, due to the license limitation. Each session consumes a license. And, on the firewall there is an option to enforce login uniqueness.
-
Hello @assadwaheed05 One (1) is the number of licenses you have for that service on the firewall and "Max:6" is the maximum number of node license you can get for this model. The limitation (max) has direct correlation to the hardware capacity. As you move up the firewall models, you will see that the maximum count will…
-
I would like to confirm that same API end point with the attached JSON content works on an NSv firewall, as expected.
-
JSON Content (PDF)
-
@gyalpo , I've tested the following JSON schema and it works, returning success. I am sharing the screen capture and the JSON content. As a side note, I tested this on a Gen7 physical appliance, and it should not make any difference on an NSv. JSON Content: { "access_rules": [ { "ipv4": { "from": "WAN", "to": "LAN",…