Unable to access your DNS-320L

[#1]

I have successfully setup my Buffalo NAS, and can now access that.

I am trying to set up my Plusnet router so that I can access my D-Link DNS-320L NAS over the internet.

I appreciate that I have to setup Port Forwarding, but cannot find the right port to forward.

Each time I try to access the files on my D-Link NAS through mydlink.com, I get :-

"Unable to access your DNS-320L.

If you cannot access your DNS-320L, please check that:

• You have at least 256K of bandwidth
• Your DNS-320L is not being blocked by a firewall or an antivirus program"

It shows that my DNS-320L is there and accessible, but cannot access it.

I have tried turning off the firewalls in my Anti-Virus and Router, but still no access. I have tried forwarding port 80, but not sure whether it is something to port 80, or from port 80 to something.

Any help is appreciated.

[#2]

fwiw, perhaps you should ask on Dlink forum with regards to what ports are required to be open?

http://forums.dlink.com/index.php?board=347.0

For curiosity, you could perhaps put the device into DMZ on Hub One and see if that solves the problem?

Advanced Settings > Firewall > DMZ

[#3]

Thank you - I have looked there, and there doesn't seem much specific.

All instructions seem to say Port Forward FTP to 21. I have done that, and no joy.

Putting DMZ doesn't work either.

This used to work on my previous Router (TalkTalk) and doesn't on the Pulsnet one - no changes to NAS.

[#4]

hmm, strange you couldn't get FTP working by placing your DNS-320L into DMZ of the Hub One.

If you are using passive-FTP, you may also have to define a range of dynamic ports (eg. 51001 to 51009) on the actual DNS-320L, and then add corresponding port forward definitions to the Hub One.

Be aware you're not the first customer to discover port forwarding might not work properly on Home Hub 5/Hub One.  Plusnet don't provide any support for this feature.  You may have to consider using a 3rd party router to resolve your issue.

[#5]

Thank you. I have got Port Forwarding to work on my Buffalo NAS, forwarding external port 41388 to NAS internal port 9000.

I had hoped it would be something similar for the DLink (DNS-320L).

[#6]

Port 9000 on your Buffalo NAS is purely for web UI access.  

Long shot.  Try deleting the Port Forward you created for FTP port 21, then add your DNS-320L to DMZ again.

Another simple test is to use FileZilla FTP client to directly access your DNS-320L?

(You will need to know the internet facing IP address of your Plusnet connection.   eg.  use myip.com)

[#7]

Thank you - I did delete Port Forwarding and put the DNS-320L into the DMZ, but to no effect.

You mention that port 9000 on the Buffalo NAS is purely for web UI access - that is exactly what I want for the DNS-320L.

I can see it over my home network, but not from external.

[#8]

This won't fix your mydlink.com issue.

Determine the LAN IP address of your DNS-320L.   eg.  192.168.1.65

Determine the WAN IP address of your Plusnet connection (eg. use myip.com).  eg.  91.125.205.1

When on your LAN, confirm you can access DNS-320L directly with a web browser on port 80.  eg.  http://192.168.1.65:80

If http doesn't work, try https://192.168.1.65:80

If successful, set up port forward rule for external port 80 to internal port 80

Can you access it externally perhaps via 4G mobile ?    eg.   http://91.125.205.1:80

If the port forward rule doesn't seem to work, change the port forward rule to use a different external port number.  eg. external port 32801 to internal port 80

Then try   eg. http://91.125.205.1:32801

[#9]

Can you also confirm the DNS-320L is using DHCP to acquire an IP address, gateway and DNS from Hub One, or does it have a static IP address ?

[#10]

Thank you bill888, I appreciate your help.

Your first suggestionhttp://192.168.1.65:80 works, so I set up a port forward rule for external port 80 to internal port 80, and it still works internally.

I tried accessing it externally perhaps via 4G mobile ?    eg.   http://91.125.205.1:80 and that worked.

In answer to your second question (Can you also confirm the DNS-320L is using DHCP to acquire an IP address, gateway and DNS from Hub One, or does it have a static IP address ?) Yes, it is set up for a static IP address.

Is this down to the DLink portal ? The Plunet Hub uses .254 at the end, but the TalkTalk one used .1. I had to change the Buffalo NAS to look at .254, and the DLINK does look at .254, but I wonder how the DLink portal works?

I will ask on the DLink Portal Support and see what they say.

[#11]

The reason for asking whether DNS-320L was using dhcp or static, was whether you may have incorrectly entered the wrong gateway IP address, but you said you can successfully access the dlink via   eg. http://91.125.205.1:80, so that sort of rules out any incorrect settings on the Dlink NAS.   

You could perhaps change it temporarily to DHCP to see if it makes any difference. I doubt it.

As you can access the Dlink NAS directly without using the Dlink Portal, then it does indeed look like a portal issue.

Your guess is as good as mine as to how the dlink portal work.

One would think there is an initial registration process which subsequently causes your DNS-320L to 'phone home' periodically, and notify the Dlink portal of its 'current' IP address when it changes.   So when you use the portal on a web browser (I presume it is not an app), it therefore knows the IP address of your Dlink (Plusnet router) and permit your web browser to connect directly to it.

Have you tried re-registering your Dlink NAS?

Unfortunately, the Hub One doesn't offer DDNS.  I don't suppose your dlink NAS supports any 'free' 3rd party DDNS providers if you cannot get the Dlink portal to work?

You can change the default IP address on the Hub One to 192.168.1.1 if you wish, but TBH, I'd be very surprised if it did fix the problem.

Which Talktalk router did you used to own?

I am probably wrong, but there a rumour that the current TT wireless Hub may be unlocked and permits use of PPPoE even though TT uses DHCP protocol.

[#12]

I use a Synology NAS, have a PlusNet fixed IP but don't like using 'standard' ports.  I just set my (Draytek) router up to forward 5000 to my NAS for general access and use port 55000 as an ftp port and port 55536 for passive ftp.  I did create a separate user for ftp access and the relevant shared ftp folder.  To use my ftp I go to ftp://MyPlusNetIP:55536 with my user/pass and I get in. Hope this helps.

[#13]

bill888 - thank you very much for your help - I think it is now pretty certain that the issue lies with the DLink Portal, as I can access my files externally, as long as I remember the IP address !

I have contacted DLink and await their reply.

Thank you for your patience and talking me through it step by step - very helpful

[#14]

Hi adrianscotter - looks like the issue is down to the DLink Portal, as, with bill888's help, I can access my files externally, just not through the DLink Portal.

[#15]

I'm sure you have already checked, but check the DNS settings on your Dlink NAS are correct.  Wrong settings would prevent the Dlink from 'phoning home'.

If you are able to set up separate DDNS on the NAS, you won't need to remember your IP address (The address can change if you reboot the router or there is a temporary broadband disconnection)

Does this page help?

http://www.dlink.cc/others/how-to-configure-d-link-dns-320-storage-network-managementlan-setup-and-d...

links to

https://www.dlinkddns.com/login/?next=/