D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: rporetti on August 23, 2011, 05:41:10 AM
-
Hi folks,
I've had this problem for a while now and I'm starting to get worried as my back-ups are getting "way out of date."
I use Second Copy to back-up files from my main workstation and my server, to a DNS-323. Both machines' Second Copy, started issuing the error:
"The specified network name is no longer available."
From time-to-time, during these back-ups, I *also* have Windows raise the following error for the NAS:
"Windows - delayed write failed"
Any ideas on how to solve either problem would be appreciated - as my back-up system, is no longer backing up!
Cheers!
Rob
-
One other thing... I can use second copy to back-up to my laptop (wireless), to another machine on my network and also a Synology DiskStation that I borrowed from a buddy. So it does not appear to be a network problem. I also replace my network cable to the DNS-323.
Really need help here... thanks in advance for any assistance.
Cheers!
Rob
-
What Windows is telling you is that it's loosing the connection to the storage device - or to be more precise - the storage device is disappearing part way through the file transfer.
Network errors are a distinct possibility, but not the only one.
-
What switch are you using and have you tried the NAS in another port on that switch?
As Fordem says it sounds like a network problem but it could also be a hardware problem with the NAS or the switch.
-
Hi,
I had the exact same problem when copying files to/from my dns-323: "The specified network name is no longer available."
Tried replacing the cable, the port on my router, gave it a fixed ip, copied using the ip address, mapped, not mapped, all combinations I could think of but some some reason after a random time, the copy just stops and windows shows the above error.
Also ran a ping to the device while copying but no time out appeared when the error message pops up.
I have this problem already al long time and cannot find any real solution to it so any help/advise is welcome !
Thanks !
-
oh yes, just remebered:
transferring data using FTP doesn't cause any issues at all. even when I'm transferring data the "normal" way and using FTP for another transfer, the FTP transfer continues while the windows copy would fail after some time.
-
Describe the network linking the two devices - the error message points to a network problem. Windows is seeing the NAS at the start of the transfer and not seeing it when the transfer fails.
-
Hi,
Thanks for your anser!
it's a very simple home network. my desktop PC is connected (wired) to the my Linksys WRT54GS router and also my DNS-323 is connected to that same router. there is also an HP 2300 laserjet printer connected to the router and some wifi devices like HP all in one printer, a vista lapop and an xp laptop.
before the main desktop was an XP box but I recently bought a new one running win 7, but issues remain on all PC's.
When I first bought the DNS-323 it worked just fine but for a long time now I'm having trouble with it. already tried connecting it directly (using cross cable) to my desktop and with fixed IP on both and I had the same issue.
I've read a lot of posts on several forums about the error I have but it doesn't seem to be the same issue. I've been thinking about he master browser issue but also with only my desktop PC and the DNS-323, the issue occurs also.
Is it possible that for some reason the server software in the NAS is corrupt? since the problem started I already downgraded to previous firmware and upgraded again to 1.08 (currently running) but nothing helped.
I would be very hapy to see this resolved! Thanks!
-
How long are the network cables, did you crimp them yourself?
Theoretically the SAMBA daemon can be the source of the error, but I think that's quite unlikely - since we're not seeing large numbers of users complaining - corruption of the software on your particular NAS is equally unlikely, there are safeguards designed into the hardware that would have alerted you to such corruption.
-
I think the cables are fine. neither one I made myself. the cables between the router and the DNS-323 is the blue one that came with it in the box. the cable between the router and my PC is also one I bought.
it seems strange indeed that SAMBA is causing the error but I don't see any other reason. if one of the cables is broken, I would have errors transfering files using FTP as well wouldn't I?
I'll try to find other cables and try again. Is there any way I can verify the software on the NAS is working OK?
-
so I used other cables and connected them on different ports of the router (only has 4 ports) and tried to copy a 6GB file but it failed after about a minute. I even tried another file (3,5GB) to make sure the file isn't corrupt and the error also accured.
both times I was running a ping to my nas and it didn't show any time outs. if the device would "fall off' the network for some reason I would expect to see this in the ping as well. Am I right?
I performed the tests starting from \\dns-323\volume_1 and \\192.168.123.101\volume_1
I read in some articles that that I should drive map to the IP address and not to the hostname of the NAS but both fail. it almost looks like the device is being disconnected from the network but it isn't as the ping continues and copying using FTP goes just fine ...
that's why I started thinking about the samba software going crazy. it's really a mistery !
-
it seems strange indeed that SAMBA is causing the error but I don't see any other reason. if one of the cables is broken, I would have errors transfering files using FTP as well wouldn't I?
Not necessarily - different file transfer protocols can have different error correction algorithms that are more or less effective - ftp is a file transfer protocol that was designed for slow serial links so error correction is probably better than SMB which was designed for local area networks.
-
that makes sence ! ;)
do you have an advise on how to solve my issue? or where to start looking? I now almost constantly use ftp to transfer bigger file to avoid the errors but I'd like to hae the NAS working normally and use SMB :-\
-
Now is the time to start looking at what has changed in windows. Did the problem start after one of the windows updates? If so you must look at what was updated - I assume windows logs this somewhere. Maybe it has changed how the firewall works or altered time outs in some way.
-
I have the issue on all my home PC's (wired and wireless)! even my brand new Win 7 desktop gave the same issue since the beginning I installed it ...
let's say 4 months ago, I even reinstalled my old XP desktop and with only windows and drivers installed, I also had the same behavior when copying ...
all that is why I really think it's a problem with the DNS-323 itself
-
Hi folks,
I've had this problem for a while now and I'm starting to get worried as my back-ups are getting "way out of date."
I use Second Copy to back-up files from my main workstation and my server, to a DNS-323. Both machines' Second Copy, started issuing the error:
"The specified network name is no longer available."
From time-to-time, during these back-ups, I *also* have Windows raise the following error for the NAS:
"Windows - delayed write failed"
Any ideas on how to solve either problem would be appreciated - as my back-up system, is no longer backing up!
Cheers!
Rob
Hard to track down. You've likely ruled out the network, a cable or your router. Try testing the drive itself.... As in removing it from the enclosure.
-
I know this may seem a stupid question but has anything changed with your operating system - updates etc. and yes, I did ask it before but you didn't give any answer.
The reason I ask is because a friend had problems on his network that were caused by an update he installed and since you are saying you only have the problem with one program I would look at that first.
Have you tried another backup program and if so what were the results?
-
Sorry for my late reply, have been away for some time ...
Yeah I have tried everything I could think off. cables, router, drives etc.
@ivan: To answer your question. I have this issue on all my workstations, laptops, desktop (old XP and new Win7) so I really don't think it could be related to software or any update. I thought about it as well in the beginning but the issue is going on too long now and I even had everything reinstalled once on my old XP box and after a clean install I had exactly the same issue. Also when I just installed Win7 on my newly build PC, I immediately had the same issue. Really frustrating !
I've read about 'fun plug' but I'm a total noob concerning Linux so I don't know if that could help in some way?