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. Sunny Qi 10,896 Reputation points Microsoft Vendor
    2021-03-08T03:22:56.253+00:00

    Hi,

    Thanks for posting in Q&A platform.

    Regarding of the issue "Not enough server memory resources are available to process this command", please follow the following method to see if the issue can be resolved.

    Step 1. Press Windows logo key + R at the same time. Type regedit in the Run box. Then click OK.

    Step 2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

    Step 3. Look for the IRPStackSize key. If the IRPStackSize entry is not present in this subkey, you need to create one.

    Step 4. Right click the empty space on the right. Click New and then choose DWORD Value.

    Step 5. Name it IRPStackSize and then press Enter.

    Step 6. Right click IRPStackSize. Then choose Modify.

    Step 7. Type a larger value in the Value data box. Then click OK. (Values may range from 0 x 1 to 0 x C. These values are equivalent to 1 to 12 in decimal notation.)

    Please kindly note that if the error message remains afterwards, increase the value of IRPStackSize more.

    Best Regards,
    Sunny

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Jason Peet 1 Reputation point
    2021-03-08T12:24:29.213+00:00

    Hi Sunny,

    Many thanks for taking the time to respond to my query. We have actually implemented the steps you reference starting at an IRP StackSize of 24 and working our way up (we are now at 32).

    Is there a recommended sie that we should use? So far, it has made no impact.

    Many thanks,

    Jason.

    0 comments No comments

  3. Sunny Qi 10,896 Reputation points Microsoft Vendor
    2021-03-09T08:50:58.043+00:00

    Hi Jason,

    Thank you very much for your feedback.

    Before we go further, may I know if there is any related Event log in Event viewer when issue occurred? If yes, please help to provide the detailed event log for further troubleshooting.

    Best Regards,
    Sunny

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  4. Jason Peet 1 Reputation point
    2021-03-18T11:45:59.707+00:00

    Hi Sunny,

    Apologies for the delayed reply - it's very busy at work at the moment. So I have looked at the logs and whilst there isn't an entry every time this issue arises, this was the last entry when it was recorded.

    Failed to establish a network connection.

    Error: The transport connection attempt was refused by the remote system.

    Server name: 192.xxx.x.x
    Server address: 192.xxx.x.x:445
    Instance name: \Device\LanmanRedirector
    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.

    It is truly driving us nuts, so would very much appreciate any guidance you can give!

    0 comments No comments

  5. Sunny Qi 10,896 Reputation points Microsoft Vendor
    2021-03-23T04:19:54.907+00:00

    Hi,

    Thank you very much for your feedback.

    Based on provided information, I would suggest you disable Windows Firewall or any other third party anti-virus software temporally to test if the issue can be resolved.

    Best Regards,
    Sunny

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments