D-Link Forums

The Graveyard - Products No Longer Supported => DNS-323 => D-Link Storage => Beta code! => Topic started by: ddtof on June 19, 2009, 01:44:47 AM

Title: https ? Samba throw the router ?
Post by: ddtof on June 19, 2009, 01:44:47 AM

Hello,

I just have checked "Allow SSL/TLS connection only" and it works (no ftp possible, only ftpes). But for the moment filezilla locks on a MLSD command but I think it is due to the fact I have not yet rerouted the passive mode port range.

No I wonder if it is possible to go furthur in security:
When we connect to the administration page, we use http so the password is "visible".
Is it or could it be possible to connect on the admin pages in https and disable the http to "hide" the connection password?

An other question (may be I should have put it in an other post???):
If I want (if possible) access my NAS by samba outside my intranet, what ports needs to be redirect on the NAS on my box-router?

I'm more and more a fan of this Nas323 ;)

Title: Re: https ? Samba throw the router ?
Post by: Banshee1971 on June 21, 2009, 05:53:35 AM

For my case, if i want to access my NAS from my Work Intranet, knowing they let 8081 pass, i simply create a rules on my Router (Port Forward) to forward the 8081 to me NAS.
I use Tomato for Firmware, so i "disable" this rule. When i want to access the NAS, i only need to enable the rules (without the need of reboot the Router).

Title: Re: https ? Samba throw the router ?
Post by: fordem on June 21, 2009, 08:26:23 AM

I could be wrong but I'm not certain you two are discussing the same type of access ...

You mention forwarding port 8081 which suggests you're using http, and the original poster is specifically asking abount SAMBA or SMB access which generally requires multiple ports (138, 139, 445 come to mind) and which is generally not considered secure when used across the internet.

Title: Re: https ? Samba throw the router ?
Post by: ddtof on June 21, 2009, 02:28:50 PM

Thanks a lot for your replies, so you suggest to not use SMB outside the intranet for security reason... Good advice if it is not secured.