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

Another thing others could try, as they're using a NAS and probably EntraID users on their computers, is putting the NAS hostname in front of the username.

Example : [hostname][username]

This has helped in some situations on EntraID connected computers, but not in my cases with the hostname of the medical devices.

Answer 2

Estimados,

El problema puede ser que el firewall esta bloqueando la conexión en el computador que esta compartiendo carpetas compartidas por SMB,...

Para realizar la prueba realicen lo siguiente:

En Windows es fácil desactivarlo en el panel de control...

En Linux deben ingresar el comando en una terminal "sudo ufw disable"

luego intenten conectarse nuevamente desde Windows... en una ventana cmd ingresen el comando "start \IP"

Answer 3

In my /etc/samba/smb.conf, I fixed it by commented out the line map to guest = bad user

For people who's user names in windows is not matching in linux you can add this to /etc/samba/smbd.conf username map = username.map

In a new file called username.map put in... linuxuser = windowslogin@outlook.com windowslogin@hotmail.com

Change the above user/logins to your local linux user name & windows login email(not the local user name). You can add multiple windows logins for every linux user.

Answer 4

Hi

1.Please check you have the axxes for that share drive from IT team.

2.and try to flush dns and then check

3. Check the dns records from server ream if all are gettting same issue.

If you are only one who is facing please try to update the group policy

Answer 5

According to my server logs, Windows 11 insists on appending the domain to the username, even when using a local account on a Workgroup. So, instead of sending 'username' it sends 'username@host' causing a credential fail on the server.

I have a computer I bought with Window 10, it worked fine until the Windows 11 upgrade, now I cannot access my SAMBA shares, and it appears no way to fix it.