SonicWall VPN - Server is not reachable

We were trying into set up a SSL VPN on a TZ215 Sonicwall - which we have done before for other customers but we keep getting Server is not reachable on this one.  We setup HTTPS on user login on Sonicwall; turned on WAN on SSL-VPN, using port 4433; using ten IP's not used on network; used Default DNS settings; added two users, assigned to SSL VPN and Local Subnets.  We are using the latest version of Netextender - checked the server IP by doing a Whatismyip and then used that with :4433 and LocalDomain but keep getting the server is not reachable - have rechecked settings - not sure what else to look at.
Daren Anderson, MSISPresidentAsked:
Who is Participating?
 
Blue Street TechLast KnightCommented:
Hi Daren,

Have you registered the device? All all security service syncing with SonicWALL Cloud?
Which SonicOS version are you running? (you can  find it in System > Status section of your SonicWALL) Make sure your SonicOS version is the latest General Release if not then update it at mysonicwall.com.
It sounds like a system issue not a NetExternder issue but I'd like you to clarify that for me.
  • Where are you seeing "server is not reachable", e.g. in the GUI of Net Extender, on the web page...?
  • Have you tried to connect with NetExternder or Mobile Connect yet?
Make sure there are no services conflicting with 4433. You said you allowed users on HTTPS, which could have prompted someone to change the management port to 4433 since there could be other services using 443.

Until I hear back, give the firewall a reboot and see if the issue persists.

Let me know.
0
 
PberSolutions ArchitectCommented:
I would try getting down to more basics.  Can you telnet to port 4433 to see if it is open?
0
 
PberSolutions ArchitectCommented:
Did you review your access rules to ensure the SSLVPN  rule is properly configured and enabled?
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
Daren Anderson, MSISPresidentAuthor Commented:
The OS is Enhanced 5.8.1.14-48o and the Sonicwall is registered - have been using about three years.  When I tried to telnet to 4433, it said it could not open connection to the host on port 23 - Connect failed
0
 
Blue Street TechLast KnightCommented:
You didn't answer all of my questions...

Where are you seeing "server is not reachable", e.g. in the GUI of Net Extender, on the web page...?
Have you tried to connect with NetExternder or Mobile Connect yet?
Have you rebooted?
Make sure there are no services conflicting with 4433. You said you allowed users on HTTPS, which could have prompted someone to change the management port to 4433 since there could be other services using 443.
0
 
Daren Anderson, MSISPresidentAuthor Commented:
The server is not reachable is when we use Netextender and yes, we have rebooted the Sonicwall.  I will try to change the 4433 and try something else - they use other services so will check those
0
 
Blue Street TechLast KnightCommented:
So what happens when you browse to the web page (https://Public_IP:4433)?
0
 
Daren Anderson, MSISPresidentAuthor Commented:
I get Server not found
0
 
Blue Street TechLast KnightCommented:
Any word on if you have flushed out the port conflicts with 4433?
0
 
Daren Anderson, MSISPresidentAuthor Commented:
sorry no, I havent been back to the customer site - maybe tomorrow or Friday
0
 
Blue Street TechLast KnightCommented:
OK, let me know. Since you can't access from anywhere it sounds like a port/service conflict.
0
 
Daren Anderson, MSISPresidentAuthor Commented:
I was back over to the site and tried to change the 4433 to 443 and changed the Web Management settings to 444.  Saved and reset Sonicwall - it says its preparing but then comes up with the same error about the server is unreachable - any other thoughts?  Thanks.
0
 
Blue Street TechLast KnightCommented:
That is not entirely what I was saying...what I said was check for port conflicts (all of them that would apply to 443 and 4433 or that of which you are trying to change them to). Although you changed ports that doesn't alleviate the conflicts necessarily. You have to know all the ports being used on the perimeter or public facing - that is the only way you can determine port conflicts. Technically the SonicWALL should take precedence since it is the most upstream device but there could be some funky routing or NAT'ing going on that is causing a conflict. There maybe another service running on 4433 AND there maybe another service running on 443. You need to verify that there are no conflicting services for either 4433 or 443. If you have no conflicting services running on either port and the SonicWALL is registered, there should be no issues.

Also, I never heard back from you if your SonicOS is at the most current release!

Can you get to the firewall from outside via remote management? Set it up and try that. I have a feeling if you can't login remotely the wrong Public IP is being used or there is a configuration error on the appliance upstream controlled by the ISP.

If all else fails there maybe an issue with the SonicWALL in which case, try a factory default to remedy or call SonicWALL support to issue an RMA.

Let me know!
0
 
Daren Anderson, MSISPresidentAuthor Commented:
We have had some other major issues - unrelated to this - at the customers so this was put on the back burner - would like this to be kept open for a couple more weeks so we can address it again.
0
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.