Help!!! Patient NAS drive/Network expert required!!

candlestick

candlestick

Suspended / Banned
Messages
1,461
Name
The King Of Prestwich
Edit My Images
Yes
Evening,

I am at my wits end with my NAS drive/network and could do with some help! I recently upgraded from Windows 7 to Windows 8, and I have been having problems with my Iomega Home Media Cloud Edition NAS ever since, but I'm not convinced the problems are connected.

The best way I can describe the situation is that I can see my NAS drive briefly on the network, when I either reboot the NAS or my router (I'm with Sky btw) before it either disappears from the network and/or the NAS description (HendersonNAS in this case) disappears but I can still see the IP address, and ping it, but can't access the actual drive from either my laptop or any of my other devices. I must confess I removed my port settings/firewall on the router when it started playing up, but surely this would only affect my ability to see the drive in My Computer???

Has anyone got some time to talk me back through the setup via MSN or email or PM? It would be greatly appreciated (even if I only get to the point where I can back up what's on there and sell it on!!!). A successful candidate can be assured of a nominal contribution for some beer tokens if that hooks anybody in??

Cheers in advance! :(
 
Sounds like a firewall issue to me but I have no experience of Win8.
 
Normally if I'm copying stuff across, I'd literally pick it up as visible in windows explorer/file manager or whatever they call it these days. To actually adjust the settings, setup a torrent etc, I'd normally type in the IP address into Chrome and carry on from there
 
candlestick said:
Normally if I'm copying stuff across, I'd literally pick it up as visible in windows explorer/file manager or whatever they call it these days. To actually adjust the settings, setup a torrent etc, I'd normally type in the IP address into Chrome and carry on from there
Click to expand...

In explorer as a drive letter or in the bit at the bottom as a uPNP device (shows as a storage device)?
 
Normally under Network at the bottom, I can see my laptop and the NAS. I can then usually drop down underneath to see the various partititions of the NAS (Photos, Movies, Music etc)
 
Does it make a difference if you try and access it by ip (in explorer type into the address bar: \\ipaddresshere )?


Is everything wired (could it be wireless issues)?
 
Normally it would be wireless, but I've tried hooking up to the router via Ethernet with exactly the same results. Will try putting the ip address into explorer instead of using a browser and report back
 
Still no joy - I've uploaded 3 screen dumps to Flickr if that helps : http://www.flickr.com/photos/tenderstuart/ - the router pic shows my attached devices. 192.168.0.7 is the NAS drive in question & historically it would show a name in there too. The 'explorer on boot up' pic shows what I could see in Windows 8 file manager briefly after I'd rebooted the drive & the 'access from explorer pic' shows what happened when I put the \\192.168.0.7 address into file manager.
 
candlestick said:
Still no joy - I've uploaded 3 screen dumps to Flickr if that helps : http://www.flickr.com/photos/tenderstuart/ - the router pic shows my attached devices. 192.168.0.7 is the NAS drive in question & historically it would show a name in there too. The 'explorer on boot up' pic shows what I could see in Windows 8 file manager briefly after I'd rebooted the drive & the 'access from explorer pic' shows what happened when I put the \\192.168.0.7 address into file manager.
Click to expand...

That doesn't make sense, if you're putting the ip in it shouldn't be telling you the name is not contactable..

Is the nas getting its ip automatically or have you specified it?

It might be worth trying to submit a support ticket on the Iomega site, I'm not sure exactly how that make work but normally there is a form of unix running these boxes. It may be that some configuration has gone askew.
 
Automatically if I remember correctly - it used to be on 192.168.0.2 if I remember correctly.

I've sent Iomega an email, but I'm not holding my breath.....it doesn't sound like customer service is their strong point...
 
What does opening a cmd window and running

ipconfig /all

give you?
 
I almost want to say its a local dns issue but I don't know why it resolved the name from the ip above..

I'd put it on a static ip as a matter of course with such devices.

If not dns I'm thinking network fault maybe? Have you tried putting it on a constant ping by ip and name?
 
neil_g said:
I almost want to say its a local dns issue but I don't know why it resolved the name from the ip above..
Click to expand...
DNS isn't used with Windows names (no "." in the name). My local domain here is "home", depending on whether I use "buster" or "buster.home" (buster is a machine here) the name resolution is done in different ways. buster.home is done through my DNS service on my firewall, buster is resolved using the networks master browser (which is a FreeBSD machine here, but can be anything from a Windows machine or a computer running Sambas nmbd service).

The master browser is determined by elections on the local network which get triggered when a master browser can't be found (which can be for a variety of reasons). Typically, the master browser will be chosen to be the "workstation" with the newest O/S. The machines also all need to be in the same workgroup (not sure how windows 8 handles this) and subnet for this to work nicely. Anything beyond this starts to involve domains, which is a whole new problem set.

Sometimes my network gets in a pickle and I've had to set my main desktop machine to never be considered as a master browser. Occasionally on boot it decides it wants to take over the world and didn't play nicely (this involved a single registry change).

net view

can also help as that lists what your computer "sees" as a local network.
 
Sorry, busy day today at work, so only just got online to see your reponses. Much to my surprise,I've had a reply from iomega customer services, who have suggested a few things to run through, and not the usual 'reset your computer' nonsense!

I'll try their suggestions, plus the stuff you've suggested, and report back later in the week, as I've got a busy few days ahead (first week back in work after paternity) - thanks for all your help so far! :)
 
Funnily enough, I've just emailed Iomega again this morning, and this update was my next job! :) Their suggestions were the following:

1) Set a static IP address on the NAS - I couldn't do this, as I can't access it!
2) Give my computer a static IP, and connect to the NAS directly via ethernet - still couldn't see it.
3) Run my PC as a DHCP? server using tftpd32 and try and access the drive directly - again, no sign of it! :(

I then plugged the NAS back into my router and carried on with my browsing, getting ready to write my reply to Iomega....and then, as if by magic, the drive appeared back on the network (both in file manager, and by browsing using the ip address). I decided to take the opportunity to copy over appx 10Gb of photos, that i'm not sure whether or not I backed up, onto my laptop. I started it running, and it was transferring fine at appx 4Mb/s and then after about 40mins, it stopped, and the router dissappeared from the network again!!?!?? :O

I've emailed them back with my findings, along with a couple of screengrabs, so don't know where to go next.....
 
Do you have two DHCP servers on your network?
 
What is on your network?

You may find your NAS has a DHCP option AND your router has one. If they are both on, things will get royally confused.

To find out, you will have to isolate the possible DHCP servers (it's only likely to be the router and NAS TBH). Do you have a spare network switch handy?
 
I've been thinking on the same lines as everyone else on this thread about network conflicts etc. then it occurred to me that my very first NAS used used to do this. Be available and working for a while then disappear and come back.... then it failed completely.
 
Hmm dchp duplicate servers you'd get more issues than just the nas playing up.. Maybe. Stranger things have happened I guess.


It almost looks like a failing network interface on the nas? Presumably the Ethernet cables have been tested/swapped out? Ports on the router/switch swapped? To rule all of that out..
 
I've swapped cables, and I also have a spare router which I've swapped in, just in case it's the ports themselves that are duff, but neither have had any kind of effect.

Surely in the case of multiple dchp servers, if I'm connecting directly to the drive it wouldn't matter anyway?
 
candlestick said:
I've swapped cables, and I also have a spare router which I've swapped in, just in case it's the ports themselves that are duff, but neither have had any kind of effect.

Surely in the case of multiple dchp servers, if I'm connecting directly to the drive it wouldn't matter anyway?
Click to expand...

if youve got 2 dhcp server then your devices on the network will be getting conflicting information so potentially would cause an issue where the IP would be changing often or, if the subnet is different on one server, will become inaccessible (but like i say all of your devices would have this issue not just the NAS).
 
I am local and can help for a short while tomorrow afternoon / evening if you want me to have a look???

Cheers,

Ste
 
My WD MyBook World NASes are doing exactly the same thing as your iOmega after I migrated to Windows 8. I got fed up quickly since whatever Win 8 did to the NASes prevented all other devices on the network seeing them as well.

I reinstalled Win7 and back came the NASes "out of the box".

My guess is there's nothing wrong with the NAS it something to do with Win8. If you find out how to fix your NAS, please post how.

Many thanks
 
livig said:
My WD MyBook World NASes are doing exactly the same thing as your iOmega after I migrated to Windows 8. I got fed up quickly since whatever Win 8 did to the NASes prevented all other devices on the network seeing them as well.

I reinstalled Win7 and back came the NASes "out of the box".

My guess is there's nothing wrong with the NAS it something to do with Win8. If you find out how to fix your NAS, please post how.

Many thanks
Click to expand...

Try disabling ipv6
 
Copied from Iomega website:

Windows 8 compatibility with Iomega network devices

Question

Will my Iomega network storage device work with Windows 8?

Answer
Iomega is currently working to complete compatibility testing of our network storage devices with Windows 8. In most cases, you can use Windows 8 without issues on your client computer to connect to currently shipping Iomega devices (running Lifeline 3.2.3 or above). You can connect to your device using Iomega Storage Manager (ISM), or connect by mapping a network drive letter.

Managing Your Iomega Network Device
You can access Settings for your Iomega network device thorough ISM. You can also access the web management interface for your Iomega device by entering the device IP address into the URL bar in Internet Explorer.* When the device home page opens, select the Settings icon to access the device console.

File Backup from Windows 8 to an Iomega Network Device
Iomega QuikProtect is not compatible with Windows 8 and will not be supported. In place of QuikProtect, Iomega recommends that customers use the new native File History backup feature built into Windows 8. To access File History, select Control Panel → System and Security → File History. File History supports network drives and has been tested and found to work with Iomega devices.

Installing Iomega Storage Manager under Windows 8
Iomega Storage Manager installs correctly under Windows 8. A warning regarding "Personal Cloud" during installation will not affect operation of the feature. Also, if the option is selected to install QuikProtect, you will see an error message indicating the feature cannot be installed. To avoid this error message when installing Iomega Storage Manager from the web setup portal, select the Custom installation option and de-select QuikProtect. The next update of Iomega Storage Manager will detect Windows 8 during installation and automatically launch File History instead of attempting to install QuikProtect.

Twonky Media Server
Twonky Media Server should work correctly with Windows 8; however testing is still in process. Click Notify Me at the bottom of this window to receive an email if the information in this article is updated.



*NOTE: Testing with new Metro style Internet Explorer browser is not yet complete. If you encounter issues, try using the standard IE browser to connect to your Iomega network device.
 
Copied from Iomega:

QuikProtect
Iomega QuikProtect is not compatible with Windows 8 and will not be supported. In place of QuikProtect, Iomega recommends that customers use the new native File History backup feature built into Windows 8. To access File History, select Control Panel → System and Security → File History
 
I know this (above) may or may not explain this issue as he has some access, but it may help others.

Cheers,

Ste
 
Gonna try a downgrade back to Windows 7 and see how I get on!!??
 
Right, downgraded, and currently I can see the nas device....getting a backup while I can, and we'll see how go from there.....the saga continues
 
Ste_Lord said:
How did you get on with this?

Ste
Click to expand...

I've just got in from work and, touch wood, I can still see the drive on the network! :)

We must therefore conclude that Windows 8 is rubbish, and I hereby retract my statement on my Windows 8 thread of how good it is!

Thanks everyone for your help, especially Ste for his offer of localized technical support!
 
You must log in or register to reply here.
Back
Top