If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
copying files, "the specified network name is no longer available"
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? |
#2
|
|||
|
|||
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 "Jordan Mills" wrote: 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? |
#3
|
|||
|
|||
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 |
#4
|
|||
|
|||
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 |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Error copying files to zip drive | Tom M. | General | 1 | November 23rd 04 05:12 PM |
sluggish performance... | Jeff | General | 3 | October 25th 04 08:52 PM |
dos wild card syntax comm | barry martin | General | 0 | August 4th 04 02:47 PM |
wireless network no longer working | Blu | Networking | 0 | July 18th 04 02:29 PM |
Question about C:\Windows\Temp files | JR Berry | General | 6 | June 7th 04 09:32 PM |