Solved

Accessing https through dyndns from Sonicwall

Posted on 2014-02-07
5
897 Views
Last Modified: 2014-02-11
Hi Folks,

I have Sonicwall firewall and Aruba Controller connected to it . Objective is for me to access controller management page from outside.
I did the following tasks
1. Dyndns entered
2. Inside NAT Policies , I mentioned Outside (WAN Interface IP), Inside (Host - Management of Controller ) , Services (HTTP,HTTPS)
3. Inside Firewall , I mentioned Outside WAN insterface IP to local management IP to be allowed .

Well it is not working at moment, for outside PC , I could see dyndns through nslookup . But I am not able to access webpage. Any suggestions please .

BR,
Siddarth A
0
Comment
Question by:infiniti7181
  • 3
  • 2
5 Comments
 
LVL 25

Assisted Solution

by:Diverse IT
Diverse IT earned 300 total points
ID: 39843729
Hi infiniti7181,

What SonicWALL model do you have?

I'd recommend using the Public Server Wizard to achieve this by clicking on the Wizards link in the upper right-hand corner (depending on your model). The wizard will create the appropriate Access Rules, NAT Policies, Service & Address Objects necessary to make this work properly. Additionally, make sure you plug the Dyn settings into the SonicWALL rather than the PC/server agent. You should plug in the setting in the DDNS page of the SonicWALL.

Let me know if you have any questions!
0
 
LVL 11

Assisted Solution

by:Miftaul
Miftaul earned 200 total points
ID: 39843760
Did you go to Sonicwall Administration page to change the Sonicwall remote management port to 4443 (from 443). It could be that sonicwall is still using port 443(https) for its own remote management.
0
 
LVL 25

Assisted Solution

by:Diverse IT
Diverse IT earned 300 total points
ID: 39843845
FYI: It's not recommended to change your management port for HTTPS from 443 to 4433 because 4433 is the default SSL-VPN port, but rather change it to 4444 or some other non-conflicting port, if need be.
0
 
LVL 11

Assisted Solution

by:Miftaul
Miftaul earned 200 total points
ID: 39843982
Sonicwall suggests the changed new https port to be 4443 (not 4433). I agree that could be changed to 4444 as well. By default, 4433  is for the ssl vpn on sonicwall.
0
 
LVL 25

Accepted Solution

by:
Diverse IT earned 300 total points
ID: 39844546
LOL - I misread your port number...we are both saying the same thing! Apologies.
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
For many of us, the  holiday season kindles the natural urge to give back to our friends, family members and communities. While it's easy for friends to notice the impact of such deeds, understanding the contributions of businesses and enterprises i…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

919 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now