copying files, "the specified network name is no longer available"

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jordan Mills - 18 Dec 2004 18:19 GMT

When I'm copying files across the network from one windows computer to
another, I sometimes get this error. It happens on both then command prompt
and explorer, anything that uses windows file shares (eg it does not affect
http or ftp). The time it takes to get the error is inconsistent, but it's
usually before I can copy a 500 mb file over a 100 mbps network. I've seen
this on many different networks, but can't find documentation of it on the
web. Any ideas?

Reply to this Message

Leriks - 21 Dec 2004 10:37 GMT

I have the same problem with 4 computers running XP proffesional SP2 and I
haven't found any solution either. Did you get some solution?

Regards
Lennart

> When I'm copying files across the network from one windows computer to
> another, I sometimes get this error. It happens on both then command prompt
[quoted text clipped - 3 lines]
> this on many different networks, but can't find documentation of it on the
> web. Any ideas?

Reply to this Message

LindaLin - 28 Jan 2005 00:20 GMT

Hi,

I got the same error too intermittently when trying to access a file from
a VMWare workstation to a shared network drive! Please let me know if you
get any solution or hint. Tons of thanks!!!

Linda

Reply to this Message

shades - 10 Feb 2005 22:19 GMT

Hi there
I had the exact same problem with more PC's all running Windows XP pro
SP2, and tried everything that I could find on the web... whitout succes

:-(.

Eventually I made it work and here is the solution that worked for me
(some would call it at workaround more than a solution - but hey!)

go to Start menu -> All programs -> Administrative tools -> Local Security
Policy
(Opens Local Security settings window)

In the left pane, navigate to security settings -> Local Policies ->
security Options

in the right pane find and make sure that the following settings are
disabled:
Microsoft Network Client: Digitally sign communications(always)
Microsoft Network Client: Digitally sign communications (if server
agrees)
Microsoft Network Server: Digitally sign communications(always)
Microsoft Network Server: Digitally sign communications (if client
agrees)

do this on all pc's and reboot.

It seems that the cause of this problem is a bug in Microsofts SMB driver
signing, and what this solution does is disabling it. (might not be a good
idea if you are on a domain).

Microsoft has a hotfix for this, but the only thing that it did for me was
removing the MrxSmb warnings in my event log?! problem remained though.

I hope that this works for you, otherwise, good hunting

Reply to this Message