Storage Trouble connecting to NAS

Hi

I am having some trouble with one of my NAS devices. It is a Buffalo Linkstation Pro Duo, and was working perfectly fine yesterday. Switched it on today, and it's looking like it's not there. When I try to browse through the mapped drive I get the following error:

An error occured whilereconnecting F: to
\\192.168.0.10\ FunkyFairies
Microsoft Windows Network: The network path was not found.

This connection has not been restored.


Also when I try to troubleshoot, I get the following issues found

The remote device or resource won't accept the connection Detected

The device or resource (192.168.0.10) is not set up to accept connections on port "The File and printer sharing (SMB)".


When I view the NAS Navigator, the device is shown, but not with it's usual name, some strange characters.

The IP address pings fine, and this is happening on more than one PC (ie won't connect on either). I do have another NAS, and that is perfectly fine, and appears OK in the NAS Navigator, and can broswe to it no problem, unlike the other one.

Please help!!

 

Sounds like the NAS has been reset to factory settings if the name has changed.

Browse to its webpage and check out its config.

 

The name was always kept to the factory name, the one it has now is a zero with a line through it, i... then 3/4 written in ascii then capital I with a line above it.

Would love to browse to it, but can't.

It pings, but can't browse to it.

 

So http://192.168.0.10 does nothing?

 

That is correct. Sorry, after posting it in Hardware, thought it should go into Tech, but wasn't sure

 

It does have a fixed IP and hasn't changed IP due to being on DHCP?

 

have you tried https? https://192.168.0.10

edit: \\192.168.0.10\ FunkyFairies <-- is that the unc path? as it has a space in it.

 

It has fixed IP address (as far as I am aware)

Has always been that IP address

IP address pings as well.

 

Just tried https, and no luck.

I think that is the unc path. was unaware there was a space, so whether that was just my typo.

 

This is really strange.

Just thought I would try \\19.2.16.0.10 in IE, and guess what.....

It worked. I then went to my computer and can now browse the files.

I have not done anything else, expect try it in IE.

Really, really strange.

Want to try and get to the bottom of it though.