Windows Server - " Specified network name is no longer available"

Some of the computers cannot logon with this message " " Specified network name is no longer available" I am on Small Business Server 2003 (SP2), what can I do to treat this

make sure your all computers are members of the same workgroup/domain. I think you also might want to ensure that all of your computers are on the same subnet or if you hae different vlans defined then make sure you have properly implemented inter vlan routing.

Follow this link-

http://www.techsupportforum.com/forums/f138/solved-the-specified-network-file-name-is-no-longer-available-184430.html
http://support.microsoft.com/kb/961293

Possible cause:

This is caused by Symantec Endpoint Protection 11.0, Symantec has identified this as a known issue.

Solution:

To resolve this issue, contact Symantec to assist you with the SymantecEndpointProtection software or Symantec Antivirus software. 
For more information about how to obtain support for these products, visit: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007121216494948
Use one of the following methods: 

  

Method 1: Update your copy of Symantec Endpoint Protection to the latest version available 

Symantec has identified this as a known issue (bug) and they have published a an update to these programs to resolve this issue: 

·     http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007102613484948


  

Method 2:  Completely remove Symantec Endpoint Protection 11.0

Please follow Symantec documents or contact Symantec support to use this method. To contact Symantec visit one of the following Symantec Web sites: 

  

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007101615023748

  http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/5db8e519e16d42f2882573290005aa1d?OpenDocument

Disconnect the current Mapped Drive and generate a new one according to the
current status of the folder.
If you can not re-map you have to check the sharing and the permissions.

check this link

http://

Hi Gerry,

If you are facing this error
Error 64: "The specified network name is no longer available" (ERROR_NETNAME_DELETED). There might be problem with network adapter.

Then follow the steps to troubleshoot network adapter problems

   1. Use the Ping or PathPing command-line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips.

    To watch Ping statistics, use the ping -t command. To see statistics and continue, press CTRL+BREAK. To stop, press CTRL+C. If you detect lost packets in the statistics output, it indicates networking problems up to Open Systems Interconnection (OSI) layer 3 (IP-level connectivity).

    If the remote system that you ping is across a high-delay link, such as a satellite link, responses may take longer. Use the -w (wait) switch to specify a longer time-out.

   2. Check the event logs for network-card-related entries or connectivity-related entries.

   3. Check whether the network adapter is on the Microsoft Hardware Compatibility List (HCL). To see the HCL, visit the following Microsoft Web site:
    http://winqual.microsoft.com/HCL/Default.aspx?m=x (http://winqual.microsoft.com/HCL/Default.aspx?m=x)
   4. Check other computers that use the same default gateway that are plugged into the same hub or switch. If these computers do not experience network connectivity problems, the problem may be a faulty network adapter on one computer.

    If this is the case, update the network adapter driver to the latest version.
   5. Contact the vendor of each motherboard and update the BIOS of the boards. Some network adapters and motherboards or BIOS versions are incompatible. Obtain the latest version from the vendor's Web site or contact your hardware vendor.
   6. Check the network adapter and uplink hardware (hub or switch) for common settings. Make sure that all complementing network resources (network adapter, hub, and switch) are set to the same speed and duplex level. If the media type is set to autosense, autosensing, or autodetect, or "Auto Select," make sure that all components are autosensing correctly.

    On some switches, a duplex setting of Auto may cause it to use half-duplex. You may have to force it to use full-duplex.

    Reset the switch, restart the client, and test the connectivity.

    Put the client and the server on a passive hub. If communication resumes, the problem may be caused by an incorrect network switch configuration.

    For more information about how to configure the devices, contact your hardware vendor.
   7. Manually set the network adapter of the computer that has connectivity problems to half-duplex and a lower speed.

    Connect the system to a switch that is configured to half-duplex and 10-Mbps, or use a 10-Mbps hub, to see whether connection can be established at a lower transmission speed.

    To increase performance, increase the speed settings manually to 100 Mbps, and then restart the computers. Test for network connectivity loss, increase the setting to full-duplex, and then restart the computers. If network loss occurs, reduce the duplex setting and the speed to the previous settings.
   8. Swap the network cable between the failing system and the hub or switch.
   9. Replace the network adapter with a network adapter that has been tested and proven reliable. To do this, follow these steps:
     1. Remove the network adapter diagnostics program.
     2. Remove the network adapter in Network properties.
     3. Install the new network adapter.
  10. Run Network Monitor at the same time on both ends of the network connection. After you filter the traces on the addresses of the two systems, compare both traces to see whether you can see the same traffic.

    Use TCP Retransmit, the Network Monitor Experts tool, to detect TCP retransmissions. To do this, follow these steps:
     1. Start Network Monitor.
     2. On the Tools menu, click Experts, and then click TCP Retransmit in the navigation pane.
     3. Click Add to Runlist.
     4. Click Run Experts.
    If frames are missing in one of the traces, check all intermediate cabling, hubs, switches, and routers for hardware or configuration errors.

    In Network Monitor, view the Capture Statistics summary frame. This frame is the last frame of the trace. If it contains a value other than 0 in the following statistic counters, the connectivity problem may be caused by a hardware or configuration problem:
    STATS: MAC CRC Errors = 0
    STATS: MAC Frames Dropped due to HardWare Errors = 0 

Reference :- http://support.microsoft.com/kb/325487