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

Aaron You 16

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

netsh winsock reset
Enabling SMBv1 support on both client and host
resetting network via Settings

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

Andrew Lawton 15 Reputation points

2023-04-15T15:52:22.7266667+00:00

I have pinpointed the issue. Having checked all the logs on my NAS firewall, it appears that Windows 11 tries to connect to the SMB server (on my NAS) using the microsoft account username(!?!?!) and not the correct username on the NAS, which is saved in the the credentials for the SMB share in Windows 11. I hope Microsoft fixes this issue really fast. What is happening: Lets say my username on the NAS is MrX and my password is 1234. My microsoft account on the Windows 11 laptop is (for this example) MrXmsAccount@live.nl When I first try to acces the SMB shared folders on my NAS using Windows 11, I provide the username "MrX" and the password "1234" and as a result Windows 11 can access the shared folders. I allowed Windows 11 to save these credentials. The next time Windows 11 tried to access the shared folders on my NAS it provided the following credentials: username: "MicrosoftAccount\MrXmsAccount@live.nl" (instead of just MrX) and password 1234. Please fix this microsoft, this cannot be by design....
Paul Tan 40 Reputation points

2023-06-13T02:37:32.9933333+00:00

use .\username and your NAS password. That should fixed your problem.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Rich McCabe 5 Reputation points

2024-01-05T18:46:11.0166667+00:00

He got the upvotes because it does work. Right or wrong. Resolved my issue.
Zack Wrubleski 0 Reputation points

2024-12-25T03:19:31.8966667+00:00

Logged in just to thank Paul. That solved my issue on Windows 10. To re-iterate, Windows started to use Microsoft credentials associated with your MS account rather than a plain credential. The audit log on my server had it alter the username and workgroup/domain. It just started happening in the last week. Must have been an MS update.

Hope others can find this or let me know what I'm doing wrong.

15 answers

Fred 1 Reputation point

2022-10-17T19:42:56.11+00:00

I have the same exact issue.

Can't find and answer to this.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Ben Rowe 0 Reputation points

2023-02-03T17:05:30.36+00:00

Yup - got exactly the same issue here.

I've even spun up a Windows 10 VM on the windows 11 host and can access the SMB share so i know there is nothing wrong with the network connection on the host. There must be something else blocking this.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Hank Cohen 0 Reputation points

2023-09-17T16:27:29.59+00:00

What worked for me was to 1. Enable SMB 1 on the client and simply mount the network drive using file explorer. Don't know yet if it will still be there after a reboot but if not a startup powershell script should be able to redo the mount every time the system reboots.
Please sign in to rate this answer.
Dawesi 0 Reputation points

2023-11-08T06:24:03.19+00:00

That worked for a while, but then now doesn't and can't use any SMB... Microsoft have admitted they are playing with SMB not just SMB1... so time will show what they stuffed up.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Dawesi 0 Reputation points

2023-11-08T06:26:33.1066667+00:00

GO TO SMB Settings and enter a workgroup name, make sure you computer has the SAME workgroup.

This solved my issues on a Azure AD machine.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
notxnik 0 Reputation points

2024-02-10T09:42:15.0133333+00:00

Anyone has an update on this? I can't access an SMB1 share on several medical devices any more.
Devices works just fine, so why dump it if it's on an isolated network...? I guess I will have to look for some third party software which has a built-in SMB client to connect to those devices capture or sync the files to a PC... Really Microsoft, why make it more complicated than just activating or deactivating SMB1... Why go through the trouble?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

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

15 answers

Your answer