Connecting NAS Box (Thecus N2200 EVO)

[#1]

We've just moved to PlusNet as our ISP and our NAS box (Thecus N2200 EVO) no longer connects. I think it something to do with IP addresses but that's the extent of my technical ability. Any ideas? We're using the router which plusnet supplied us with.

[#2]

in what way is not connecting?
it probably is connected but just has a different IP address now that you are using a different router.
find out what the IP address is from the router.

[#3]

It just says connection path not found, connection is not restored

If I find the router IP what do I then need to do?!

[#4]

you need to log on to the router admin page, and then find out what IP address has been assigned to the NAS.

[#5]

I use this network scanner as a lazy way to find device IP addresses.

[#6]

Is the NAS box configured with a fixed IP address or is it configured to get it's IP from DHCP?

[#7]

Given the problem, it's more likely to be the former rather than the latter.

[#8]

not necessarily.
the new router might be giving out IP addresses on a different range compared to the previous router.
so even is the NAS was DHCP you'd still end up with the same problem.

[#9]

I don't follow that line of thought at all, @chenks76.  You're saying if the IP address of the NAS used to be, say, 192.168.0.x and now it's, say, 192.168.1.x then it wouldn't work?  Why not?  A decent modern printer could cope with this, why not a NAS?

[#10]

Because the shortcut or mapped drive being used will still point to the old IP address regardless if it has a static or dhcp address.

[#11]

That doesn't make sense, @chenks76 .  If you are using a mapping to a particular IP address then you cannot use DHCP.  You can achieve a fixed IP address by setting it on the device or by setting an override on the router (which would be SHCP, I guess) but it's the same either way.

[#12]

yes you can.
you can map to any IP address, there would be nothing stopping you from doing it.
as long as the device never picked up a new IP address then the end-user would be none the wiser.

based on the questions and comments from the OP, it would seem unlikely that any static IP address had been set.
if they had the knowledge to do that then surely they would have the knowledge to know why it's no longer working on a new router.

[#13]

On Windows when you map an external drive it is mapped to a computer name as can be seen using

c:>net view

from a command line. But that of course means that name must map to a physical machine which implies that the name used is resolved using DNS.

So if you have a mapped drive of \\MyLaptop\Music, MyLaptop may resolve to 192.168.0.5 but if you then change the LAN addressing to say 192.168.1.X then this should resolve too the share. But I know from experience that this doesn't always work as I think the IP address is stored locally in the registry so I have found the the best approach is to delete the share and re-map it.

[#14]

My bet is that the IP address was assigned by the setup routines when the box was bought and that the new router is on a different subnet to the old router.

[#15]

---

@Anonymous wrote:

On Windows when you map an external drive it is mapped to a computer name

---

not entirely true.
you can just as easily map a drive using just the IP name, there is no requirement to use the FQDN or any other device name.