Network error: The specified network name is no longer available

8,528

Solution 1

Do you have Symantec Endpoint Protection 11.0 installed?

According to the following Microsoft article, the issue may be due to Symantec Endpoint Protection 11.0. If you have it installed, consider upgrading or removing it.

https://support.microsoft.com/en-us/kb/961293

Solution 2

I was unable to copy a large file from a network share to my local hard drive (or access it directly from the parent application) with the same error.

It turned out to be an incorrect message. The real problem was that the network copy was timing out. I succeeded in copying this 4 gig file by using the Windows command-line utility ROBOCOPY, which has a parameter to extend the timeout wait. A command to try might be:

robocopy /z /v /w:240 source-dirname target-dirname

The robocopy command isn't well documented, but from fighting with it I found that it would not copy individual files, only the contents of a directory to another directory. Flags: /z means "resume on failure, don't restart the copy." /v means "verify the copy once complete." /w:240 means "extend the timeout delay to 4 minutes(240 seconds)."

In my actual copy I threw in the command "/fft" (assume FAT file times) because the docs say that is more reliable and I was desperate to have this stupid transfer finally complete, and "/fp", which displays the percentage complete of the file being copied. (It's a big file, I wanted to get an idea how long the process would take.)

Share:
8,528

Related videos on Youtube

Jason Foglia
Author by

Jason Foglia

Updated on September 18, 2022

Comments

  • Jason Foglia
    Jason Foglia over 1 year

    I'm receiving this message after getting a list of files. And trying to move a file out of the list. There is no Antivirus software installed on this server.

    The server is Win Server 2003 SP2.

    • HackSlash
      HackSlash about 6 years
      It's not clear what your question is or what the scenario around this error is. I know it's old but this thread comes up in google results for the error you describe.
    • HackSlash
      HackSlash about 6 years
      I found that I only get this error when using Hostname. If I attempt to access the system by IP address I don't get the error.
  • Jason Foglia
    Jason Foglia about 9 years
    No, I've googled this like crazy. No Symantec products at all.
  • DavidPostill
    DavidPostill over 7 years
    Please read the question again carefully. Your answer does not answer the original question.