TKWITS Community Legend ✭✭✭✭✭
Reactions
Comments
-
Did you use the migration tool for the upgrade?
-
Under Device \ High Availability \ Advanced there is a 'Synchronize Settings' button. https://www.sonicwall.com/support/knowledge-base/how-to-configure-high-availability-ha/170503978252820/
-
You'd have to enable jumbo frame support before you can configure MTU sizes greater than 1500 bytes. https://www.sonicwall.com/support/knowledge-base/how-to-enable-jumbo-frame-support-in-sonicos-gen6-gen7/170505523725177/
-
You will need something handing out DHCP addresses. Which device you choose is up to you. The Sonicwall can easily be your DHCP server.
-
It's complicated... You cannot individually specify which network the NAT applys to over the VPN, it's all or none. That said no matter what you attempt to do with NAT-ing the Sonicwall itself will ALWAYS send its own traffic out an interface with the interface IP. The NAT will never apply to the DNS traffic generated by…
-
Sonicwalls really WANT a public IP address and direct internet connection on their WAN interface, so if you put it behind another router it will not get that. Being behind another router/firewall (Double NAT) is do-able, but you'll run into more issues with it that way, and its better to get practice in a production-like…
-
AFAIK you cannot use the IPSec client in the manner you are looking for. You can however use the SSLVPN client.
-
Maybe the backend is still an old IBM mainframe... "What is going on???" Agile development / DevOPs / whatever buzzword you want to use for a complete lack of forethought when managing projects.
-
Make an address object for the DNS server, then set that as an allowed network for the user in the VPN tab.
-
Do you have Ping enabled under Management on the interface you are pinging? Im guessing 10.10.10.252 and 10.10.20.252 are your LAN interface IPs? Are those addresses what you are pinging? What are you pinging from, what network is it on, etc.? Please provide more information when posting.
-
For DHCP WAN interfaces use Zero touch.
-
Upgrade to a newer firmware. I dont remember which one fixed it, but its best to keep your firmware up to date.
-
Have you tried resetting Edge settings to default via edge://settings/reset ?
-
Are you running the latest firmware?
-
What troubleshooting have you done?