Sonicwall NSA2600 - Strange behaviour after making changes

I'm trying to make some basic changes to a new NSA2600.

We had changed X0 (LAN) and X1 (WAN) to bridged mode, with the intention of using another gateway - however, that plan has now changed and we intend to use the Sonicwall as the network gateway.

So - X0 has been changed from bridged mode to Static IP - / Default gateway of and the management interface has been enabled on this IP - I've also temporarily enabled management on X1 (WAN)

My problem is - I cant access the management interface on the LAN IP address (from within the LAN) - but I can access the management interface using the WAN IP address (through X1).

So far I've tried the following to troubleshoot:

- Changed LAN IP address from (PING dies on, and starts working on - so it appears to be getting the IP address OK)

- Changed Interface X0 to have no management access, and no PING - however, pinging the IP address still gets a response.

- Restarted the Sonicwall

Anyone have any ideas? :)

Who is Participating?
carlmdConnect With a Mentor Commented:
You should be able to access the LAN management interface if you are connected via the vpn. Point your  browser using the lan ip address on the port you have set.

If you have the LAN devices set to use a default gateway other than the Sonicwall LAN interface, or a switch that gets you there, then you are not using the Sonicwall as your point of egress. This is also probably what is preventing you from access the management interface.
Aaron TomoskyTechnology ConsultantCommented:
The easy way is to run the setup wizard again.
masnrockCommented: - that sounds like a subnet mask, not a gateway. As Aaron pointed out, the easy fix is the wizard to set up your Sonicwall again.

If you want a more nitty gritty answer, send us some screenshots.
WEBINAR: GDPR Implemented - Tips & Lessons Learned

Join the WatchGuard team on Thursday, March 29th as we recount some valuable lessons learned in weighing the needs of a business against the new regulatory environment, look ahead at the two months left before implementation, and help you understand the steps you can take today!

BergstrAuthor Commented:
Sorry - I meant subnet not gateway.

I've tried using the wizard and that doesn't appear to work - however, after having a think about it, I'm thinking this is probably self inflicted, and happening because its not completely configured and in-place.

I've configured a site-to-site VPN connection to this NSA - and I'm accessing it remotely - I imagine by default, you cant access the LAN management interface from the VPN - that's my first problem! - however, they cant access it either - at the moment all of their PC's are using a different default gateway (not the Sonicwall) - so i'm wondering if the Sonicwall needs to take over as being the default gateway for everything to start working.

At the moment, while its just plugged into the LAN and using a spare internet connection its not a huge concern, so i'll wait until its installed properly before we spend any more time trying to figure it out! sorry, and thanks for the pointers anyway :)
Ahh... Could you describe the network layout and firewall configurations? What you mentioned so far helps
BergstrAuthor Commented:
Plan is to try and sort this Saturday - will let you know how it goes :)
Blue Street TechLast KnightsCommented:
Any update on this?

You may need to configure the VPN to allow SA Management within the VPN policy as well.
BergstrAuthor Commented:
After connecting it up properly and configuring the sonicwall as the default gateway for the network, everything worked as it should - including VPN and management via VPN.

Thanks for the help :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.