Solved

Accessing https through dyndns from Sonicwall

Posted on 2014-02-07
5
911 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 25

Assisted Solution

by:Blue Street Tech
Blue Street Tech 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:Blue Street Tech
Blue Street Tech 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:
Blue Street Tech earned 300 total points
ID: 39844546
LOL - I misread your port number...we are both saying the same thing! Apologies.
0

Featured Post

Percona Live Europe 2017 | Sep 25 - 27, 2017

The Percona Live Open Source Database Conference Europe 2017 is the premier event for the diverse and active European open source database community, as well as businesses that develop and use open source database software.

Question has a verified solution.

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

Most of the applications these days are on Cloud. Cloud is ubiquitous with many service providers in the market. Since it has many benefits such as cost reduction, software updates, remote access, disaster recovery and much more.
This program is used to assist in finding and resolving common problems with wireless connections.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

635 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