The Specified Name Is No Longer Available error may appear in one of several different ways when:

• Trying to access a network shared location on a Windows 10 PC from an older Windows computer.
• Attempting to access any network share using SMB (Server Message Blog) file sharing protocol.
• Accessing any network device that supports SMB protocol.
  

The error usually occurs when attempting to access the share from a client. The access attempt usually takes a long time before the error shows up.

Cause of Specified Network Name Is No Longer Available Error

Server Message Block (SMB) is file transfer protocol used on Windows systems for many years. Its primary use is to allow client computers to access remote files on another computer system. The computer storing the file needs to have SMB protocol enabled, and the client accessing the file needs to support SMB protocol as well.

However, if the system hosting the file uses a newer version of SMB unsupported by the client, it can lead to errors. Antivirus software, firewalls, and other network issues can also interfere with the SMB file transfer process.

This error usually occurs when the client, which is attempting to access the network share or device, doesn't support SMB protocol. It can also occur when accessing the network share is blocked or interrupted by antivirus software or a firewall.

How Do I Fix the Specified Network Name Is No Longer Available Error?

This issue applies to Windows 11, Windows 10, Windows 8, Windows 7, and Windows Vista, including both 32-bit and 64-bit versions of these operating systems.

1. Disable your antivirus software. This is the easiest fix to try first and often fixes this error. Most major antivirus apps like Norton, Avast, and McAfee provide the ability to temporarily disable protection.
   

2. Disable Windows Firewall and Windows Defender. Windows embedded security tools can also block SMB protocol and cause the Specified Network Name Is No Longer Available error. Disabling these tools may resolve the error.
   

3. Make sure file sharing is properly enabled on the system you're sharing files from. There might be some slight differences in correctly setting up this form of file sharing depending on the OS you're using.
   

   If you're on macOS, refer to our guides on setting up file sharing on your Mac.

4. Check the file sharing configuration. SMB protocol requires additional configuration to work on both the server and the client computers. On Windows, you'll need to open Administrative Tools to access Windows Features and make sureSMB 1.0/CIFS File Sharing Supportis enabled.
   

   Make sure to restart your Windows system to make sure the changes take effect.

5. Try a server mapping workaround. Map network shares directly by mapping to the server hosting the files via IP address rather than the network name. This approach bypasses the need to resolve the network name and could help with getting your file share to work properly.
   

   This should be a last resort since IP addresses on most networks, such as a home network, are not usually static IP addresses. Routers typically assign dynamic, changing IP addresses to devices. So even if using the server or computer's IP address works initially, it may not continue working.

6. Try a different sharing method. Since SMB is a somewhat outdated file sharing technology, you may want to consider sharing files over a network by using P2P or FTP protocol instead.
   

   You might also consider using cloud storage solutions to share files across computer systems instead.

Is SMB Enabled by Default in Windows 11?

Windows 11 supports SMB in terms of accessing shared folders on other systems. However, if you want to share folders and files in Windows 11, you'll need make sure file and printer sharing is enabled in the Network and Sharing Center.

This setting is on by default, but it's possible it was disabled, or that the Windows Firewall may be blocking it.

If you do decide to enable file and printer sharing in Windows 11, make sure to enable password protection so anyone connecting to your shared folder will still have to authenticate.