It is important to know that there are several typical issues that have been previous documented in other technotes for this issue that require checking AV exclusions, share permissions, account issues, etc. and therefore, may need to review those settings as well.  This technote is focused on newer security restrictions for server message block (SMB) protocol within Windows Server 2022 and newer.

Newer SMB protocol restrictions are in place and not properly configured for the environment.  

Solution 1

Disable the newer restrictions if not needed:
  For the eDP server, open powershell window and run the following commands:
    set-SmbClientConfiguration -enablesecuritysignature $false -force
    set-SmbClientConfiguration -requiresecuritysignature $false -force

  and then for the file server where the share resides open a powershell window and run the following commands:
    set-SmbServerConfiguration -enablesecuritysignature $false -force
    set-SmbServerConfiguration -requiresecuritysignature $false -force
    set-SmbServerConfiguration -smbservernamehardeninglevel 0 -force

Note 1:  If the share is actually located locally on the eDP server then all 5 commands shown above would need to be executed on that eDP server.
Note 2:  Ideally, it is not best to reduce security.  The customer reporting this issue was okay to make SMB work similar to previous versions of Windows.  

Solution 2

Properly configure SMB restriction settings, certificate, etc.  This would be environmental.  Customer should work with their IT Admins to make sure properly configured as this will be different for each customer.