You’ll see “The requested network name is no longer available” while trying to reach NAS, a remote device, or the server/Domain Controller (DC). This issue can also occur on the server if the controller tries to access such resources, add domain users, or promote the DC.
It signifies the resource is no longer available or the admin has restricted device access. They may have shut down the server. But the problem might also develop accidentally.
If a network resource is offline, you can’t access it until the admin enables it. In the latter instance, you can try client or server-side solutions.
“Specified Network Name is No Longer Available”
- The needed protocol is turned off.
- Ports that need to be open aren’t.
- Security applications keep track of when a network resource is accessed.
- Problems with the application’s user folder include wrong permissions, compression, or encryption.
- The domain controller did not meet the requirements before being promoted.
- The software for connecting to the network had bugs.
Fix Specified Network Name No Longer Available
Some solutions listed below will only work if you can get to the network server or domain controller. If you don’t have access, you need to contact the system administrator and ask them to do these things. Other solutions require you to change something on your computer, which is easy.
Enable SMBv2/v3 Protocol
A network uses the Server Message Block (SMB) protocol to access shared resources on the same network. Currently, only SMB v2 and v3 are used, and SMB v1 is no longer supported. So, by default, many devices don’t have SMBv1 turned on; instead, they use later versions.
But neither the client nor the server may have these protocols turned on. So, you have to do it by hand to fix your problem. SMBv3 and v2 use the same stack, so to use either protocol, you only need to turn on SMBv2.
Open Run; just press Win + R.
Type cmd and press Ctrl + Shift + Enter to open the Elevated Command Prompt.
Enter the following commands:
Restart your PC
sc config lanmanworkstation depend= bowser/mrxsmb20/nsi sc config mrxsmb20 start= auto
- Win+R opens Run.
- Ctrl+Shift+Enter opens Windows PowerShell.
- If the server runs Windows 8 and Windows Server 2012 or higher, type:
- $true set-smbserverconfig-enablesmb2protocol
- Type Y and click Enter if prompted.
- In previous versions, type:
- Set-ItemProperty “HKLM:SYSTEMCurrentControlSetServicesLanmanServerParameters” “DWORD” “1” “Force”
- Using Set-ItemProperty? Restart your PC.
More than activating SMBv2 alone may be needed. If you have SMBv1 and v2/v3 enabled on your system, but the server only allows SMBv2/v3, your device may need to correct an attempt to use the SMBv1 channel rather than the SMBv2/v3 channel.
In this case, you will need to disable it on the client side.
- Open the command prompt at the top level.
- Press Enter after each of the following commands:
- sc config lanmanworkstation depends on bowser/mrxsmb20/nsi
- sc config mrxsmb10 start= disabled
- To use the change, you need to restart your PC.
You can also use Windows PowerShell to disable the protocol:
Rarely, a server may support SMBv1 but disable it while supporting SMBv2/v3. If you can’t resolve the issue after trying the preceding steps and solution, you may need to enable SMBv1 on the server and client.
Open Firewall Ports
Any network protocol can encounter this difficulty. Each protocol uses different ports to start and maintain a connection. To avoid the problem, ensure the ports are open.
Disable Third-Party Antivirus
Antivirus and network scanners can limit network access. To prevent this issue, temporarily disable client or host security.
Remember that software protects your system. Before deactivating real-time or network security, be sure the resource is safe.
Add the network resource or user to the exclusion list to fix the error without stopping the software. If you don’t have server access, ask the system admin if an exception is needed.
Change the Settings for the AppData Folder
Suppose you are experiencing this problem while utilizing an application like Windows Subsystem for Linux. The problem may be caused by issues with the application’s user folder located within AppData. Incorrect permission settings are one of the potential causes of the pain, and it prohibits the application from accessing a network resource and prevents it from accessing the user folder.