Windows 10: Windows 11 SMB Client cannot connect to SMB share

​

Windows 11 sometimes fails to connect to SMB shares that are perfectly accessible. You see Windows cannot access \share or, when using the command line, System Error 53 – “Network path not found.” This happens even when other devices (Mac, iOS, Windows 10) connect to the same share without issues. In this post, we are going to […]

This article Windows 11 SMB Client cannot connect to SMB share first appeared on TheWindowsClub.com.

read more...

 

SMB Share Problem Confounds IT Guy!

Have an existing LAN with a Windows 10 PC and a Windows 11 PC that both can access an SMB share on the network. I replaced the Windows 10 PC with a new one running Windows 11. The new Windows 11 PC cannot see the SMB share.

1. Have confirmed that all SMB protocols are enabled on the new PC.
   
2. Have disabled the third party firewall and the Windows firewall on the new PC; did not change the result.
   
3. Have disabled the anti-virus on the new PC; did not change the result.
   
4. Have disabled all items in Startup Apps; did not change the result.
   
5. If I boot in Safe Mode w Networking, it works. I can see the SMB share.
   

So it works if I boot in Safe Mode, but it doesn't work booting normally with all Startup Apps disabled.

What am I missing? What else happens in Safe Mode beside Startup Apps being disabled? What's blocking me?

Confused

 

Issue with SMB Shares W10 Client and Server

Hi all,

Have been trawling high and low to look at this issue and I know there are some other threads out there that discuss this, but not this specific issue.

We have 2 Windows 10 computers, one acting as SMB Server and the other a client sharing an application that depends on an MS Access Database. The issue is that the session is being temporarily disconnected and therefore crashing the Database.

A few things we've tried already:

1. Turned off Autodisconnect -1

2. Updated Network Drivers

3. Updated from build 1903 to 1909

4. Tried the keepconn setting in lanmanworkstation to 65535 in Registry

When checking the logs we find a key notification in the SMB Server Eventlog stating that the connection was cleaned up:

Information 10/02/2020 3:44:11 PM SMBServer
1905 (1018)

The server closed the session as part of periodic system cleanup.

Session Id: 0x600004000001

Instance Id: 0

Reason: Kickoff time expired

So we can't seem to find a way to stop this happening. Nothing on Google just yet that I can find that relates to this error. As soon as the SMB Client is disconnected the application running on the client crashes whilst it tries to reopen the handles.

Any help would be greatly appreciated.

Ta,

Jase.

 

Problem connecting to SMB Share on Linux server with Windows 10

Hello All,

Recently my Windows 10 laptop no longer sees the SMB shares on my Unraid 6 server, everything was working fine until a week or so ago. Other Windows 7 machines on the same network have no problem seeing or connecting to the same SMB shares. I did some searching
on the Web and it was suggested that you try to sign into the computer with a local account rather than a Microsoft account but that did not help. I also tried the registry edit suggested in this post:

https://www.schkerke.com/wps/2015/06/windows-10-unable-to-connect-to-samba-shares/

This did not help either, I am currently running Windows 10 Home 64 bit on an Asus UX305LB laptop and my last update was KB3093266, I believe I was able to connect to the SMB shares for a while after the update. It's pretty important that I be able to connect
to the server as I use it to backup the computer, thanks in advance.