Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
My DNS-323 just arrived yesterday, and from the start I've had more problems than I expected. Before I ordered it, I read about the various issues, but it seamed like 1.02b fixed things. In all fairness, it my vary well be my network as well since I have less than a normal setup. But that's a longer story for another time. I slapped the drives in it (Seagate 200GB), plugged it into the network and powered it on.
First, the easy search utility didn't see the unit. No too surprising. I have a DHCP server (A real one) on the network, but it's not the default 192.168.0 space. I log into the server, get the lease IP given to the NAS and we're off to the races. I log into the unit, set it to use a static IP and reboot the unit.
Next I downloaded the 1.02b firmware and tried updating the firmware. The firmwar uploads, but when it hits 100% in the progress bar, there's no indication that it's really done and that you should reboot the unit. This is the same for IE and Firefox. Eventually, I just assume it's done and reboot the unit. It comes back and lists 1.02 as the firmware. Close enough.
Next, I go through the setup wizard and go to format the drives. Before the unit was updated, the drive space available listed 184GB. After the update it lists 198GB. The update mentions that kind of fix. So I select RAID1 for 198GB. I get the progress window for formatting, but it hangs on 94% every time. During formatting, the unit doesn't response to any other web page requests.. At some point after it hangs at 94%, the web admin interface response again...it just never finishes formatting. A reboot of the unit yields a RAID1 synced/completed volume on the status page. Fine. Odd, but it appears to have worked.
Now for the fun part. I start copying all of my files over from the file server onto the NAS using the command line robocopy/xcopy. All goes well for a while, then I'll get a "network name no longer available". At this point, I can ping the NAS, but it's admin pages don't respond at all and it's no longer on the network as far as SMB is concerned. The unit is powered on during this time, and nothing is blinking. WTF. At some point, it's web admin pages response again. Restarting the file copy then usually yields "the file is in use by another process" errors. At that poin rebooting the NAS is the only fix. Once it reboots, rinse, lather , repeat. File copies go fine for a while again, then it's back to the same problems. It's not just writing to the server either. IF I try downloading a large amount of files from the NAS, eventually I run into the same problem.
I have the firewall turned off. Virus scanners are off. This is quite frustrating and no how I envisioned it all working. Later I plan on wiring the unit directly to my machine to see if I still have the smb copy issues locally, of to see if it's a network/wireless/wap issue somewhere.
Is there any chance that the drives really aren't being reformatted, or that they're still in EXT3 or something from the initial boot up of the unit?
Offline
Just a partial update. During one of my latest tests, not only did the file copy fail with the network name not found/file busy errors, but my wireless access point hung. Piece of crap Limpsys.
Figuring I would need an external SATA/USB enclosure to format [now, or use to recover in the future], I snagged one of those and a new D-Link WAP while I was out and about this morning.
So far, file copies to the NAS are much more reliable, but not fool proof. Out of 3 tries to copy 1.5GB worth of 1.5MB photos, two succeeded, 1 failed towards the end. The different this time being that I got the network name no longer available error, but the mapped drives and the web admin was still available.
I'm going to do some more tinkering, including hooking the unit directly up to my ethernet port, doing more heavy file copies, and last but not least, just yanking the drive and formatting then so the NEXT gets a fresh try on them under this revision of firmware.
Last edited by claco (2007-03-11 01:22:12)
Offline
Finally, after sleeping last night off a little, I managed to move the NAS upstairs and hook it up directly to my ethernet port. Surprise surprise, I've copied 10s of Gigs of data back and forth without a single error. So clearly, SMB over wireless has some issue somewhere. I've tried two different access points, two different computers, with 3 different wireless cards. I have no idea what the real issue is, but in an environment where there are no ethernet cables, that makes using, and more importantly backup up this NAS, a crap shoot at best without errors. Yuk.
Last edited by claco (2007-03-11 20:49:06)
Offline
Solved! I feel so stupid as this should've been somewhat obvious to me. As it turned out, when I tested using direct ethernet and over wireless, BOTH connections had the windows firewall turned on. After searching the net for the "network name no longer available" errors, I stumbled across one that details how SMB can get cranky if ICMP is lost/blocked.
Sure enough, under the advanced connection options, icmp was not allowed under wireless, but was allowed under the ethernet connection. Once I fixed that, things are going just dandily!
Offline
Is this something you changed in the router set-up? My iMac G5 seems to loose the wireless conection each time I copy something. I'm using a Linksys router with fire turned OFF.
Offline