Windows 11 SMB Client cannot connect to SMB share - error 53 on `net view`

Question

Machine in question: Windows 11 21H2 22000.832
OSes on other devices that can successfully connect to the share: MacOS Ventura built-in SMB; iOS 16.5 built-in SMB; ES File Explorer on iOS, Windows 10; etc.
Share Host: TrueNAS-13.0 with domain name truenas.lan and NETBIOS name ALANG-NAS

After swimming through unuseful posts for hours, I felt the need to start actively seeking help.

Situation: The win11 SMB Client cannot connect to an SMB share hosted on the same network with its own fully qualified domain name. I cannot connect to it either via domain name or IP address.

As I was typing this, I found that I cannot connect to any SMB share on my network anymore..

Screenshots



Here is some common information requested on this issue:
ipconfig /all

Windows IP Configuration  
  
   Host Name . . . . . . . . . . . . : Alang-Desktop  
   Primary Dns Suffix  . . . . . . . :  
   Node Type . . . . . . . . . . . . : Hybrid  
   IP Routing Enabled. . . . . . . . : No  
   WINS Proxy Enabled. . . . . . . . : No  
   DNS Suffix Search List. . . . . . : local  
  
Ethernet adapter Ethernet:  
  
   Connection-specific DNS Suffix  . :  
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection (7) I219-V  
   Physical Address. . . . . . . . . : 0C-9D-92-C2-3D-B4  
   DHCP Enabled. . . . . . . . . . . : Yes  
   Autoconfiguration Enabled . . . . : Yes  
   IPv6 Address. . . . . . . . . . . : fd14:27e9:a812:40ec:7034:3796:bd55:7eea(Preferred)  
   Temporary IPv6 Address. . . . . . : fd14:27e9:a812:40ec:f0a8:83ab:bb1f:1637(Preferred)  
   Link-local IPv6 Address . . . . . : fe80::7034:3796:bd55:7eea%10(Preferred)  
   IPv4 Address. . . . . . . . . . . : 192.168.10.100(Preferred)  
   Subnet Mask . . . . . . . . . . . : 255.255.255.0  
   Lease Obtained. . . . . . . . . . : Friday, August 5, 2022 2:22:04 PM  
   Lease Expires . . . . . . . . . . : Monday, September 11, 2158 9:04:10 PM  
   Default Gateway . . . . . . . . . : 192.168.10.1  
   DHCP Server . . . . . . . . . . . : 192.168.10.1  
   DHCPv6 IAID . . . . . . . . . . . : 336371090  
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2A-27-00-34-0C-9D-92-C2-3D-B4  
   DNS Servers . . . . . . . . . . . : 192.168.10.1  
   NetBIOS over Tcpip. . . . . . . . : Enabled  

nslookup truenas.lan

Server:  openwrt.lan  
Address:  192.168.10.1  
  
Name:    truenas.lan  
Address:  192.168.10.5  

Test-NetConnection -ComputerName 192.168.10.15 -CommonTCPPort SMB
ComputerName : 192.168.10.5
RemoteAddress : 192.168.10.5
RemotePort : 445
InterfaceAlias : Ethernet
SourceAddress : 192.168.10.100
TcpTestSucceeded : True

Test-NetConnection -ComputerName truenas.lan -CommonTCPPort SMB
ComputerName : 192.168.10.5
RemoteAddress : 192.168.10.5
RemotePort : 445
InterfaceAlias : Ethernet
SourceAddress : 192.168.10.100
TcpTestSucceeded : True

telnet 192.168.10.5 445  
  
able to connect  



net view \\192.168.10.5\Vault  
  
System error 53 has occurred.  
  
The network path was not found.  

The network page is populated. Double-clicking on the computer that contains the share results in the same error as trying to connect using NetBIOS name

Things I have tried

1. netsh winsock reset
2. Enabling SMBv1 support on both client and host
3. resetting network via Settings

I am beyond desperate now and really do not wish to reset my PC. Any help will be appreciated.

Answer 1

Ran into this issue with a new Windows 11 setup. Tried some different suggestions that did not work. Finally solved it without enabling Smb1 by manually adding the credentials to the credential manager:

1. Run (ctrl+r): control /name Microsoft.CredentialManager
2. Select Windows references.
3. Add Windows reference.
4. Enter your remote path with credentials.

Answer 2

Hi Aaron, Hi Fred,

I managed to fix this! I don't now you enabled SMBv1 but this is how I did and it fixed everything:

1. Windows key + R, type optionalfeatures.exe and press enter
2. You will get this:
   
3. Tick the box "SMB 1.0/CIFS Client", and press OK! (it will take a while to complete the action)
4. You will be prompted to reboot: make sure you have closed everything and reboot! (it will look as if you have triggered a Windows update)
5. After the reboot: try the command net view \\YourServerIP\ and rejoice!

Regards,
Quantum Hosting®

Answer 3

I am having the same problem, however, enabling the CIFS option did not work. What's interesting to me is that if I open a command prompt with elevated permissions, I am able to view/map the SMB share. However, trying to access as a normal user presents the error above. Anyone else seen that?

Answer 4

@Matthew Hornung and all,

I'm facing the same problem on a new win11 enterprise installation.

By attemting

Test-NetConnection -ComputerName ******** -CommonTCPPort SMB  
  
ComputerName     : ********  
RemoteAddress    : fe80::265e:beff:****:1056%5  
RemotePort       : 445  
InterfaceAlias   : Ethernet  
SourceAddress    : fe80::5f0:48e8:****:9222%5  
TcpTestSucceeded : True  

I even try to connect mounting the drive via explore GUI and every kind of credential authentication fails.

After hard work, seems a connection with New-SmbMapping command resolved the issue... https://learn.microsoft.com/en-us/powershell/module/smbshare/new-smbmapping?view=windowsserver2022-ps, but every restart the mounting desappearing.

I tried to add -Persistent to the command and... explorer.exe starts to lag and, at the end, to crash systematically. This attempt lead me to reinstall the system, so DO NOT DO THAT

I'm using at the same time a win10 system. It works like a charm.

Microsoft guys, this is a blocking issue, please thake account of that problem!

Answer 5

UPDATE:

I created a local user on the same PC and he can access the remote folder. I'm running win11 enterprise

So, the problem appears to be when using a the azureAD/user enterprise user.

It is absolutely crazy!