D-Link Forums

The Graveyard - Products No Longer Supported => D-Link Storage => DNS-320 => Topic started by: Bulles30 on May 14, 2012, 06:05:40 AM

Title: Secure Internet Access
Post by: Bulles30 on May 14, 2012, 06:05:40 AM

Hi,

Is somebody able to explain how we can connect to the NAS from Internet using HTTPS ? I would use Web File Server, but I can gain access only without SSL. If I try to activate SSL (on the loging screen), I obtain an error message of time out.
I don't know if the problem comes from the NAS or the browser (or both). Of course, I tried from several computers with different versions of browsers and different browsers.
What is wrong ?

My config :
- ADSL link with fixed IP adress,
- bridge with port forwarding to the NAS,
- the bridge has some light Firewall abilities,

Many thanks for your replies,

Regards

Title: Re: Secure Internet Access
Post by: nmcar on May 14, 2012, 08:07:59 AM

Hi. I can connect to the NAS using https by forwarding port 443 to port 433 in my router setup.

Title: Re: Secure Internet Access
Post by: Bulles30 on May 15, 2012, 12:54:37 AM

Hi,

I'm like a donkey ! :-[
It's so simple and I didn't thought to that.
Thank's for the answer and sorry for this stupid question.

Regards,

Title: Re: Secure Internet Access
Post by: nmcar on May 15, 2012, 07:37:38 AM

Relax. I did not know that until I read it in a topic someone else posted. I assume you could make it work, but please be aware that I made a typo mistake. I meant to forward port 443 to 443 (not to 433, as I wrongly wrote). Greetings.

Title: Re: Secure Internet Access
Post by: Bulles30 on May 22, 2012, 02:20:29 AM

Ok,

With your help eveything goes well now. Last problem : Firefox and IE indicates a security certificate problem with the site. I must declare an exception in the browser to log in .

The security certificate for DLink seems to be wrong or elapsed. Have I to download an other one on D-Link site for exemple ?

Regards

Title: Re: Secure Internet Access
Post by: nmcar on May 22, 2012, 04:24:40 AM

Well, I just skip the sign that indicates that I have an invalid certificate and instruct the browser to continue. ;)

Actually, I just used secure access because I could not forward port 80 (it simply wouldn't access). Thus, I tried with port 443 and it worked.

Now, since I upgraded to fw 2.03, I can access through port 80. So, I do not have to deal with certificates and so on.