TKWITS Community Legend ✭✭✭✭✭
Reactions
Comments
-
AFAIK App Passwords, SMTP Auth, and other features may not be available depending on your security settings.
-
@TonyA @Community Manager
-
Run a packet capture and review the logs to determine what function of the Sonicwall is blocking the traffic.
-
I've never done an 'always on' config so I cant help you there (i didnt think this was possible unless you are referring to connecting pre-login). With the MSI version you can specify the server parameters during installation, so the user only needs to enter their credentials.
-
When connecting with NetExtender and a new version is found (on the firewalls firmware), the user will see the prompt as shown in the article you linked to. IIRC the NetExtender downloaded from the Sonicwall VPN Client downloads page is just the base MSI with no config, and the one downloaded from either the admin…
-
I dont think you understand how routing works and thats ok. Generally, routes are to / from SUBNETS and your screenshot shows a destination of an IP address. While strict routing on a per IP basis is not wrong, its very dependent on the situation and needs. Read up: https://en.wikipedia.org/wiki/Routing…
-
The end user only needs to click Ok on the window notifying them of the update to NetExtender. It does not require admin privileges. They missed a step in the article: Go to SSLVPN \ Client Settings \ Default Device Profile \ Default Device Profile \ Client Settings \ NetExtender Client Settings, and enable 'Enable Client…
-
https://www.sonicwall.com/support/knowledge-base/how-can-i-configure-a-site-to-site-vpn-policy-using-main-mode/170504380887908/
-
AFAIK you can't disable a virtual interface. Disable the Access Rules that control access to / from those VLANs and see who complains.
-
"HTTPS content filtering is IP based" Add the IP addresses of api.openapi.com to the exceptions...
-
Are you doing DPI-SSL? If so add the URLs to the DPI-SSL exceptions too.
-
Test outside of the Sonicwall connection and see if it works...
-
You are essentially turning the Sonicwall into a mini switch via software. It would be better to just install a managed switch...
-
Were you using static routes on VM B and the Cisco? Presumably you have a switch (providing layer 1 and 2) off of X6; disconnect X6. Again, verify proper functionality without the Sonicwall 'in place'. Narrow your scope to rule out issues.
-
You dont have to completely pull out the Sonicwall, that is not what I meant... but I am not going to go through step by step of other ways of testing. You need to be able to think and troubleshoot yourself. Learn the OSI model, start troubleshooting at layer 1, and work your way up the layers. Hint: Instead of using OSPF,…