11-02-2011 06:00 AM
I am running Windows 7 32 bit connected to a Cisco workgroup hub, which is connected to a Cisco/Linksys E4200 Wireless Router. I have two NAS 110 connected to the workgroup hub, one used primarily for storage and one used primarily for backup. I am having issues with one of my NAS 110 servers, the one I use primarily for storage.
I recently (the last few days) started having issues where my windows 7 PC started getting errors on a daily basis with connecting to the NAS 110 used for storage. The computer seemed to be able to see the device and I could manage it through the Discovery software, but when you clicked on it, you would get a network path not found error. I checked my router and compared the two NAS device settings against each other and synced them up as much as possible. One difference I did not reconcile is that the NAS I was having problems with is running firmware 1081, while the one I was not having problems with is running older firmware (0376 I think). I had set one to automatically update and one not. Anyway, after tweaking based on various online forum suggestions, it actually got worse, to where I couldn't even see the NAS drive through discovery or file explorer. I finally used the reset button on the NAS drive and am now back to another place, slightly different.
Currenlty I can see the NAS drive through Discovery and File Explorer but cannot "manage" the NAS drive through discovery or going directly to the IP address assigned. The message now pulls up a typical explorer page indicating that the page cannot be displayed, with more detail information indicating that the server is not accepting connections.
I'll keep perusing the forums and seek technical help through support, but sometimes posting the information as a new post can get different results. Any thoughts or suggestions are welcome.
11-03-2011 07:58 AM
I would like to start troubleshooting with the very basics here.
Please attach another ethernet cable to the NAS and perform one more reset. Be sure to hold the reset button at least 30 seconds, otherwise the device won't reset properly.
Let me know how this works out.
11-03-2011 08:25 AM
I'll definitely try that when I get home tonight. I almost did it this morning when I got to work, thinking, perhaps that I didn't do the reset cleanly or hold the button long enough or something.
11-03-2011 06:21 PM
Okay, so I did the reset by actually following the directions this time and now I get the following when I use Discovery to "Manage" the server.
XML error: junk after document element at line 3
11-04-2011 07:11 AM
Thank you so much for the update.
Unfortunately when the error you received appears the drive is defective and will need to be exchanged.
Should you need any data from the drive you'll want to contact data recovery:
For warranty exchanges, please visit the following web page:
09-19-2012 02:51 PM
Hello, I had the same problem, however......
I am using windows 7 and was ble to successfully back up my laptop to the NAS 220. However when I try to access it via Discovery or directly to my mapped drives I get the "network Path was not found". I did a full reset and am getting the same error. A note, I am able access the NAS via Discovery as well as via a mapped drive on my machines running Windows XP.