Discussion Locked

Network Name No Longer Available - Win2K

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Copy a large (5Gb) file between Win2K server sp2 and Win NT 4 sp5. After copying has been going on a while, an error comes up "The specified network name is no longer available." MS article Q255678 discusses this issue, and references Q161372 re: SMB Signing. Question: I have never explicitly turned on smb signing...my NT 4 servers don't show EnableSecuritySignature or RequireSecuritySignature values in the HKEY_LOCAL_MACHINE\system\currentcontrolset\services\lanmanserver\parameters key. These articles indicate that, if smb signing is enabled, this problem will present itself. Has anyone experienced this problem, and is there an easier fix than modify-the-registry/reboot? TIA for any help. Russ.

2 replies

by jb007

Try robocopy from the resource kit:

"Alternatively, you can use the resource kit's Robocopy utility for individual copy and move operations or for ongoing directory replication. Like Scopy, Robocopy supports the preservation of NTFS permissions, auditing, and ownership information during copy and move operations (i.e., if you run it with the /sec switch). The utility also offers several other useful features, such as the abilities to mirror entire directory structures, seed directory structures on a target drive without copying files, exclude files that meet certain criteria, and restart aborted copy operations at the point of failure. You can use the At command (or Task Scheduler, depending on your NT service pack level) to schedule Robocopy to perform particular file-copy or directory-mirroring tasks at various time intervals during the day. Because Robocopy provides superior flexibility and efficiency, you might even consider using Robocopy in lieu of NT's built-in directory-replication service for intraserver replication of the Netlogon folder's contents."

http://www.microsoft.com/technet/tips/default.asp

Although not a fix for your particular problem it may be a way around it until you find an answer.

regards,James

by rknapp

This problem presented itself when I upgraded our ArcServe 6.0 to ArcServe 2000 on a Win 2000 Server SP2 machine. I rebuilt the server with Win 2000 Server, but didn't install SP2. I installed ArcServe 2000 and the problem has not presented itself again. I suspect SP2, or the fact that I upgraded to ArcServe 2000 after installing SP2. With this latest rebuild I have changed the order in which things are done, and so far have not experienced the problem. I will be installing SP2 soon, and I willreport if the problem returns. Thanks.

This discussion is closed to new replies.