topic Re: Unable to access your DNS-320L in My Router

Unable to access your DNS-320L

norster — Thu, 10 Oct 2019 20:16:03 GMT

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.

Re: Unable to access your DNS-320L

bill888 — Sat, 12 Oct 2019 03:11:00 GMT

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

Re: Unable to access your DNS-320L

norster — Sat, 12 Oct 2019 10:37:44 GMT

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.

Re: Unable to access your DNS-320L

bill888 — Sat, 12 Oct 2019 12:06:12 GMT

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.

Re: Unable to access your DNS-320L

norster — Sat, 12 Oct 2019 14:22:47 GMT

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).

Re: Unable to access your DNS-320L

bill888 — Sat, 12 Oct 2019 17:07:16 GMT

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)

Re: Unable to access your DNS-320L

norster — Mon, 14 Oct 2019 11:53:17 GMT

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.

Re: Unable to access your DNS-320L

bill888 — Tue, 15 Oct 2019 02:52:19 GMT

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

Re: Unable to access your DNS-320L

bill888 — Tue, 15 Oct 2019 06:19:17 GMT

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 ?

Re: Unable to access your DNS-320L

norster — Tue, 15 Oct 2019 09:25:57 GMT

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.

Re: Unable to access your DNS-320L

bill888 — Tue, 15 Oct 2019 11:00:07 GMT

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.

Re: Unable to access your DNS-320L

adrianscotter — Tue, 15 Oct 2019 11:30:41 GMT

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.

Re: Unable to access your DNS-320L

norster — Tue, 15 Oct 2019 17:05:30 GMT

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

Re: Unable to access your DNS-320L

norster — Tue, 15 Oct 2019 17:06:46 GMT

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.

Re: Unable to access your DNS-320L

bill888 — Tue, 15 Oct 2019 17:51:06 GMT

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-dynamic-dns.html

links to

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

Re: Unable to access your DNS-320L

norster — Tue, 15 Oct 2019 21:19:35 GMT

bill888 - I have a new twist, which seems to prove that it is definitely the DLink web Portal.

I have reset the DNS-320L, and set it up again, with new DLink account details.

I still cannot access my files through the internet, but using the DLink app on my phone, with WiFi turned off (so that I am using only the phone signal, and no internal network link), I can access my files.

I had to set up multimedia access, but that hasn't changed the DLink web Portal access - still no-go.

Re: Unable to access your DNS-320L

bill888 — Wed, 16 Oct 2019 04:44:39 GMT

There may still be a firewall or loopback issue with the Hub One. Replacing the router with something completely different would be one way of verifying or solving the Dlink Portal problems with your Dlink NAS.

Have you been physically away from your home when you test access your NAS via the internet using Dlink portal?

If not, did using a mobile phone via 3g/4g mobile internet to use Dlink Portal via a web browser to access your NAS work ?

Or while at home, can you set up a wifi hotspot on mobile phone, then connect a laptop to the hotspot to see if the Dlink portal can access your NAS via mobile internet?

I would suggest you look at my previous post about using DDNS if it is workaround for the Hub One issues when away from home.

Re: Unable to access your DNS-320L

norster — Wed, 16 Oct 2019 21:47:41 GMT

Progress - of a sort.

Bill888 your suggestion of trying it on my laptop paid off. Although DLink have a plugin for Firefox, it never seems to install, so I installed Chrome, and after installing the plugin and a couple of stutters - hey-presto - access to all my files.

I also tried this on my windows tablet, and had to install Chrome Portable, but again after installing the plugin and a couple of stutters - hey-presto - access to all my files.

Went back to my PC, and found the version of Chrome seemed to be a later version than that which I had just downloaded, so uninstalled Chrome, and re-installed the same version as my laptop and tablet - now just goes round and round saying Install the Plugin - Reinstall the plugin etc.

Will now try to figure out what is blocking my PC.

I was also getting a message when I logged into the GUI for the the DNS-320L that it was an insecure site, so I have taken off Port Forwarding and still appear to be able to access my files from my laptop and tablet.

Just tried my PC, and although my anti-virus says the site certificate is not signed, allows me through - so all is now as it should be.

Next stage will be to try from my tablet using my mobile phone as a mobile hotspot - just tried and that works too.

Yippee - I am a happy bunny.

Thank you to everyone that has helped with this. Step by Step trial is definitely the answer .