MS Server 2019 & SMB1 Share

Jason Peet 1 Reputation point
2021-03-06T23:54:58.72+00:00

Hoping someone can help with this head scratcher: Running Server 2019 STD on a VM and have enabled the SMB1 Protocol to enable us to access a Samba share on a Linux server. However, approximately every 2 days, the Win Server stops being able to access the Samba share. I can browse to the IP of the Samba from the server, but if I attempt to open any of the share folders I get "xxx.xxx.x.x/Folder is not accessible. You might not have had permission to use this network resource... Not enough server memory resources are available to process this command" If I do a network adapter restart, the connection is fine again. We've tried pretty much everything we can think of, so if anyone has any suggestions, it would be greatly appreciated.

Windows Server Setup
Windows Server Setup
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
240 questions
{count} votes

7 answers

Sort by: Most helpful
  1. Jason Peet 1 Reputation point
    2021-03-29T10:08:37.867+00:00

    Hi Sunny,

    So we never had Windows Firewall disabled. We did disable Eset though and it has made no difference.

    Any other suggestions? It seems to be all SMB traffic as we have scan folders on our printers which also stop working. Not sure if that helps?

    Thanks in advance.


  2. Jason Peet 1 Reputation point
    2021-04-02T11:57:07.917+00:00

    Hi Sunny,

    Apologies, that was a typo. I meant to say we have never had Windwos firewall enabled. So that rules out that also.

    We have just recently changed the network adapter from the VMware to the standard Intel adapter, but that hasn't changed things either.

    Also to note, we have printers with a scan function that saves using SMB to a share on the same server. These also lose connection which does point to an SMB issue.

    I believe we are completely out of ideas on our side. We have even replicated our network with a Server 2019 box and a Linus CentOS 6 box - but we are unable to replicate as that setup works fine.

    We would welcome any and every suggestion you can think of right now!

    0 comments No comments