Home All Groups Group Topic Archive Search About

"Network Name No Longer Available"

Author
23 Nov 2006 7:41 PM
LS
I have two computers (A & B).

A is a Windows 2000 Server desktop that connects to a router in wired
fashion with Intel Pro 100+ Management adapter.

B is a laptop running XP Pro that connects to the same router wirelessly (G)
at 54 Mbps.

The router is a D-Link DI-624. The router has the latest firmware, and the
adapters have the latest drivers. A & B both belong to the same workgroup. A
has a fixed IP. B has an IP automatically assigned. A's NIC is set to Auto
Negotiate.

Whenever I try to copy files from B to A via network shares (connecting by
A's IP address, not its network name), a few files will copy and then I get
"The specified network name is no longer available," with regard to A, even
though A still appears on the network and does not seem to have lost its
connectivity. In troubleshooting, I have changed B from wireless to wired
(also set to Auto), and I still get this error. I have shut down all software
firewalls and still get the error.

What do I need to do to prevent this network dropping from occuring? I need
this to work not only for copying files, but for keeping network shares open
between the two computers. Any help would be appreciated. Thanks.

Author
23 Nov 2006 9:26 PM
Robert L [MVP - Networking]
This troubleshooting may help,

specified network name is not longer availableSystem error 64 - The specified network name is no longer available. System error 53. The network path was not found. Event ID 3013 - Description: The ...
      www.chicagotech.net/troubleshooting/systemerror64.htm 


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
  "LS" <L*@discussions.microsoft.com> wrote in message news:16ED3EEC-27A0-4A4E-9198-38D26128B7DE@microsoft.com...
  I have two computers (A & B).

  A is a Windows 2000 Server desktop that connects to a router in wired
  fashion with Intel Pro 100+ Management adapter.

  B is a laptop running XP Pro that connects to the same router wirelessly (G)
  at 54 Mbps.

  The router is a D-Link DI-624. The router has the latest firmware, and the
  adapters have the latest drivers. A & B both belong to the same workgroup. A
  has a fixed IP. B has an IP automatically assigned. A's NIC is set to Auto
  Negotiate.

  Whenever I try to copy files from B to A via network shares (connecting by
  A's IP address, not its network name), a few files will copy and then I get
  "The specified network name is no longer available," with regard to A, even
  though A still appears on the network and does not seem to have lost its
  connectivity. In troubleshooting, I have changed B from wireless to wired
  (also set to Auto), and I still get this error. I have shut down all software
  firewalls and still get the error.

  What do I need to do to prevent this network dropping from occuring? I need
  this to work not only for copying files, but for keeping network shares open
  between the two computers. Any help would be appreciated. Thanks.
Author
23 Nov 2006 9:30 PM
Ian
Two possible issues here:

1. Faulty powersaving option on wired network card. Look for an 'Allow
Windows to turn this card off to save power' option and untick it.

2. Automatic disconnection of shares. There is a registry fix for this.
http://support.microsoft.com/kb/297684
Author
27 Nov 2006 5:07 PM
LS
Thanks for your reply. I made some modifications, but am still experiencing
problems. Here is what I did:

1. Changed setting on wired NIC card to prevent power-saving or sleeping modes
2. Changed NIC card speed to 10 half to match my WAN Cable Modem speed
3. Changed autodisconnect registry setting to ffffffff in both wireless XP
and wired Win2K Server machines

After making the above changes, I performed a series of tests. On my XP
machine, I opened the network shares folders to the 2K machine and left them
open. Each time, these windows would auto-close and disappear after a few
minutes. If I were doing file copies to these shares, I would still get the
"Network Name No Longer Available" message. The regularity and periodicity of
the issue leads me to believe that it's a Windows setting and not an issue
with the NIC card or the cable. Is there something else I should change in
the registry on the 2K Machine or is it is possible that it's a setting on
the client side (the XP machine)?

I really would appreciate your help. Thanks again.