Windows 10: Windows 11 SMB Client cannot connect to SMB share on Windows server 2016 after update

I have a Windows 11 that goes in network error "Windows cannot access 'path'" trying to access a shared folder on a windows server 2016 after an update of the 12/03/2025.Same error even on 127.0.0.1Another windows 11 client can access the folder without problemTried:netsh winsock resetEnabling SMBv1 support on both client and hostresetting network via Settingsuninstalling the last updatemodify the hosts file in the System32 foldertried net user command with another user

:)

 

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.

 

SMB-Share not found

Hello together,

i have a problem and i'm troubleshooting since 15 hours.

I installed a new Windows Server 2016 (nano without GUI), added it to my domain, assigned my default GPO also applied on all my other servers, installed the fileserver with work-folders and deduplication.

Now i cannot access the SMB-Shares, neither the default admin shares, nor a newly created smb-share on a different drive for testing. I always receive the message "The network path was not found" (Error Code: 0x80070035)

Event-Viewer shows the event 30803 in the SMBClient:

Failed to establish a network connection.

Error: {Device Timeout}

The specified I/O operation on %hs was not completed before the time-out period expired.

Server name: SERVERNAME

Server address: 192.168.101.24:445

Connection type: Wsk

Guidance:

This indicates a problem with the underlying network or transport, such as with TCP/IP, and not with SMB. A firewall that blocks TCP port 445, or TCP port 5445 when using an iWARP RDMA adapter, can also cause this issue.

The client tries to access is also Windows Server 2016 or Windows 10, both doesn't work.

Already checked Windows Update, disabled SMBv1, disabled SMBv2 and changed back to SMBv1, opened SMB-Firewall Ports recommended by Microsoft (also tried disable the Firewall, without success)

Permissions are also okay, access won't work with \\Servername\share, \\IP-Address\share, \\servername.domain\share

I can access from the File-Server other SMB-shares without problems, also can open the local shares with IP-Address or Servername

Also checked the Get-SMBServerConfiguration and changed settings similar to my other servers