Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I have a fault and would like to hear any ideas before sending it off to D-Link (for a refund / replacement).
The Fault
Performing copying operations with for example explorer or with viceversa, I get this message after a few minutes of copying.
Cannot write data. The specified network name is no longer available.
At this point I cannot contact the Box at all. Time to shutdown the DNS-323 and start again.
Using the D-Link Easy Search Utility (DLESU)
Info: No users set; no groups set; no access permissions set; no quotas set; DHCP is disabled - it has its own IP address; Firmware 1.03; set up is for two separate hard discs - not mirrored.
And
If there has been a 'failure' during backup or copy DLESU says - Device no longer available.
Similarly with a 'failure' in the middle of a copy whilst looking at the DNS-323 Configuration, Firefox says - Firefox can't establish a connection to the server at 192.168.0.9.
Blown out again! Time to shutdown the DNS-323 and start again.
The fault happens any time from 3 to 20 minutes after the DNS-323 unit is started up.
Background
I have three DNS-323 set up with two mirrored for live data and the third as a backup system. I know what a backup system is and I am doing it my way. I would have set it up differently if I had known I was going to buy three.
Most of the backup is to one disc in the DNS box. A couple of weeks ago the backup copy process was getting slower, probably due to this defragmented / untidy disc (?). Then this most used hard disc started to click in use, but still worked ok. The other drive has lighter usage and had no problems.
Then the DNS Box started to become unavailable to the network. Eventually I thought that the untidy hard drive was at fault, and I reformatted it. Unfortunately the problem continued - network unavailable after a while. I pulled the now formatted hard drive and worked with the other drive for a while. The Box dying symptoms now started soon after start up. I put the now formatted hard disc back in and tried a major backup to it. This did not work due to the ''three to 20 minutes ok then unavailable syndrome''.
Working through things, I first thought it was the overused / defragmented hard disc. Maybe it was on its way out. But when this drive was pulled the other hard disc worked fine until the box gave up the ghost. My chief suspect at the moment is the DNS-323 box. And maybe the overworked hard drive is dud as well.
Any thought - gratefully received
Biscotte
Offline
dont know if this helps you, but also my dns always loses its "name" in the network (xp-network, dns connected via samba), so when do a copy process consisting of many files after some time i get a "network ressource/name no longer vailable". but rebooting the dns doesnt help here.
what i did was no longer use the "\\dns-name\Volume_1" as a network mapped drive bu instead i use "ip-number of dns\Volume_1" and i no longer have the "can not find network name/ressource" error when copying.
so thats not a solution but a workaround. if any1 has a solution and knows why the dns always loses its name in an xp-network, please let us know!
cheerio
Offline
I just copied 1804 files, in 176 folders, totaling 775 MB across my network - doesn't matter how my drive is mapped - or if I pick the drive out of "My Network Places" the copy goes through in exactly the same way.
Neither one of you mentions anything about the network itself - and that I believe is where your underlying problem originates - a network infrastructure that has problems and causes errors will function reasonably well with light loads, becuse of TCP/IPs robust nature, however, as the traffic increases, the errors themselves generate more traffic and more errors until the network fails.
This is not uncommon with wireless - the transfers I mentioned above were done over GbE
Offline
w00, Fordem,
Thanks for the replies.
I have three of these units. Only one is playing up. Two are mirrored and this one, with which I am having problems, is not mirrored.
w00,
I can't think why the DNS-323 has worked OK for months and now needs a different way of being accessed. I just wonder what might have changed to cause such an address requirement?
That said, I will try the suggested IP address trick when I get home. Thanks.
Fordem,
I too was moving large amounts of data - thousands of files in the tens of Gigabytes across lots of subdirectories. All without problems.
Now the DNS-323 conks out after a few minutes - even under very light load - say 500 meg transfer. And with the copy programme, viceversa there is a transfer speed option that restricts transfer to a percentage of the maximum rate - I have tried this option with 70 percent and 50 percent. Still get the network unavailable result after a couple of minutes copy time. Note I also have used 'explorer' and Far to perform copy functions. Both these copies cause the DNS to conk out too.
Network Info
The network has worked fine for a couple of years now. It is hard wired - CAT6 - Netgear modem router with one solitary CAT 6 lead to; 3-Com 24 port switch 100mb/sec; each of the three DNS-323 has its own unique IP address; traffic is rock bottom minimal until I do backups, then becomes unavailable; two printers are on the network - each with its own unique IP address. The network has worked fine for a couple of years now.
The only wireless is from the modem to my daughter's computer. There is no wireless to connect to the DNS-323s.
Thanks again
Biscotte
Offline
Biscotte
If you are only getting errors with one DNS-323 then you need to look specifically at that device and it's connections - physically interchange it with one of the others, so that it is using the network cable and switch port, if the problem stays with the DNS-323, consider it defective, if the problem stays with the network connection, isolate further by changing the cable and then trying a different port on the switch.
Also - the network having functioned "fine for a couple of years" does not eliminate it as a suspect - components fail, cables fail.
Offline