Error copying file specified network name is no longer available

Search forums. Forum Rules. Log in. Install the app. Register Now! Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store. JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding. You are using an out of date browser.

It may not display this or other websites correctly. You should upgrade or use an alternative browser. Thread starter tincboy Start date Nov 28, Status Not open for further replies.

Joined Nov 20, Messages 7. I'm using FreeNAS 9 for my Windows clients sharing, But while I'm trying to copy files with more than MB size, I got the error of "the specified network name is no longer available" in the middle of copy process. Is there any thing to tweak to fix this issue?

Joined Oct 15, Messages 3, This is very odd. The problem you describe, with the "specified network name is no longer available" is not one that I recall hearing about in here.

I am intrigued by the MB approximate limit. Let me ask you this: 1 Is it always at around exactly the same place? For exapmle, half a dozen MB files all at once? Joined Mar 25, Messages 19, That error is usually indicative of your desktop losing connection with the server's sharing service. This can be due to things such as a loss of network connectivity between the client and server, firewall rules blocking traffic, or the service on the FreeNAS server suddenly crashing.

Obviously this list isn't all inclusive, but that's just 3 examples I can think of off the top of my head. There's plenty more but I think you get the idea. Joined Jun 4, Messages Running FreeNAS 9. The copy job speed drops to less than 1MB and then eventually it comes back to as higha s MB. Since Teracopy is patient and somewhat intelligent it continues on.

However, noticed that when viewing the same share from another machine it "drops off" as well. Possibly a low level issue with FreeNAS dropping connections Update: While watching a copy job I just noticed a "semaphore timeout" as well. Joined Jan 7, Messages I too am seeing this for windows clients the specificed network name is no longer available. Click to expand I experienced network issues with this configuration. The 3ware RAID controller may have been the source of my issues.

How is that for irony? I rebooted the WHS and checked the drive settings under each PCI controller each of the 3 PCI controllers have 4 drives attached, and I could see write caching was disabled by checking the parameteres for each bus and channel. Write caching was off for all but the 3 Hitachi drives. Not a single transfer completed successfully! Here is another interesting thing To my surprise, it was already turned back on for most of the drives!

I don't know how that happened unless the IBM tool itself did it. I also can't seem to enable write caching on one of my 1TB WD drives, and I don't know why it says the setting was successful, but when I check it again either within the IBM tool or Device Manager, write caching is off.

Any other ideas? I think I am going to try robocopy or some other network file copying tool for large file transfers for now, but I hate having to do that! New copy the file. If it is working , please send mail to me. Static ip did not help either here. I continue to get the "network name no longer available" error when trying to manually backup my 64bit Vista PC.

So this, with no 64bit connector, I am unable to backup my pc at all to WHS. I am wondering if the connector will have the same error when it comes out. I am not sure what else to try right now. So, that isn't going to help I have been doing all of the usual things that used to cause me grief and I haven't hit the "network name no longer available" problem once! Thank you, Microsoft! I don't know if this was fixed intentionally, but whatever they did in Power Pack 1 seems to have done the trick.

I am also seeing much better network throughput, as things seem to copy to the WHS much faster than before. I thought bugs like this would be corrected by mid WHS is fully patched and has the latest drivers, including the network drivers.

I used to get the same message when copying from an XP box, but decided to test with copies between the D: drive to a share ie both on the server as it bypassed potential problems like router configurations etc.

It always fails after a couple of hundred GB. This thread was invaluable. Disabling UPNP and the write cache on the drive I was copying from allowed the copied to complete successfully.

Anyway, I took Kens advice above and went to the Connect site to report the bug. You can't report bugs on WHS any more - you can only report bugs on 'Vail', the new beta which is based on R2. Whenever NAT is in place and a new connection is established to a server, the server check for previous connections from the same client IP address and deletes any previous connections.

Because NAT acts as a proxy for the SMB protocol by using the same IP address from the two client connection requests, the earlier connection is terminated. To resolve this we have to ensure that SMB connection is established on port , to do that we have to set following registry key on server. You also have to ensure that port is opened on the Firewall.

Start Registry Editor. Locate and then click the following registry key:. Add the following registry value:. I have been getting this error trying to copy files under a couple of scenarios. However, I have narrowed down one to a definite "solution". There are certain files that just won't copy. I spent a bunch of time carving up files into smaller and smaller chunks. I wound up with several 1K files that would fail every time.

I attached them to an email that I sent to Sunbelt support. They did not test them. I found that I had to disable SPF on both the source and the target machines for them to copy successfully. I have done this successfully with several source machines and several target machines that would fail if SPF was enabled on either. Maybe if Sunbelt sees this message, they will do something about it.

I got the problem on remote desktop where I was trying to copy some files from file server to PCs. I tried all PCs and got always the same error. It took me two days to find the reason. It was a very simple reason that was blocking file copy as follows: RDP on server was set to connect the server drive as local resource.

However, the same drive was already connected as RDP local resource!!! That was the reason blocking me to copy files from the server to local PCs. Sign in. United States English.

Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Windows Home Server Software. Sign in to vote. I get this error sooo many times it is no longer just a fluke on my home network. Does changing the workgroup mess it up? Everytime I start a file copy to the server this happens somewhere along the line. It will happen more often on large file copies.

I am simply trying to copy my home data to this server so that I can test the other uses of it. I posted a bug for it. I am not seeing that other people are having the same issue. If you are please vote. Tuesday, March 6, PM. On your bug I have voted and validated. Yep, I'm getting this too - usually after several gigabytes of copying has worked!

Have added my validation to the bug. Trying to bump this back up on 1st page so that it gets noticed. Have any fixes been discovered as of yet? Monday, June 18, PM. Right now I am reinstalling the OS. Tuesday, June 19, AM. I am still seeing this issue with the RC version.

If I disable and re-enable the network card after the problem occurs, the WHS will recover. I have the same problem. I have no problems with any other shares on any other PC's on the network. It looks like there are some other guys with the same problem. Tuesday, June 26, PM. My turn to go on the list I get about a third of the way copying a 1 gig file, everything stops for a minute or so, and I get "can not copy file : the specified network name is no longer available.

Looking at this thread, it seems to be a WHS issue, and not the hardware itself. I'll go vote i the other thread mentioned here Thursday, July 5, PM. Update: It's not a hardware issue, but definitely has something to do with adding more hard drive controllers. In the console, I removed the drives that were attached to the PCI controllers, went back to only using the four IDE drives connected directly to the mobo , and magically the "network name no longer available" problem disappeared.

Unfortunately this also means my WHS server is almost full again. I hope this issue gets fixed soon! Friday, July 6, PM. Sunday, July 8, PM. Can anybody comment on that? Nope, it's not because of duplication. I have NO duplication enabled whatsoever and I still get the error message. Or should I say I seem to have solved it in my own situation.

Hope fully this can help others here. The IDE connector from the power supply went into the Vigor fan and the Vigor had a second connector for the hard drive it was cooling. That's when the "network name no longer available" message started showing up while copying files to WHS. At first I figured it was the RocketRaid card going flaky on me. Didn't help. Obviously the RocketRaid card was not the problem. I removed the drive entirely and the problem went away completely.

But I still couldn't copy too many more files because the original 4 drives were full. I took that fifth drive to the client PC, hooked up a USB adapter to it, and started using it as an external drive.

Guess what Follow the instructions below to configure the services to run automatically:. Step 2: Type services. Step 3: Double-click Computer Browser in the Services window. Under the General tab, change the Startup type to Automatic , and click Start. Then click Apply and OK to save changes. Step 4: Double-click Server in the Services window. Step 5: Double-click Workstation in the Services window. Once all steps are finished, restart your computer and then check whether the issue of 'the specified network name is no longer available' is fixed.

This post covers two parts, how to open Windows Services in Windows 10 in 8 ways, and how to troubleshoot services. Here is a quick guide:.