I'm trying to enhance security by enabling SMB signing on my Active Directory domain using the Group Policy Objects: 'Microsoft network client: Digitally sign communications (always)' and 'Microsoft network server: Digitally sign communications (always)'. However, I encountered a problem on a Windows Server 2019 that runs software relying on UNC paths like `\servernamefolder`. I receive an error saying, 'Network error, insufficient access right to \\servername\folder.' Additionally, the Event Viewer logs show Event ID 1026, indicating that file leasing has been disabled for SMB2 and SMB3 protocols, which might impact performance. I've checked the registry key HKLMSystemCurrentControlSetServicesLanmanServerParameters for `DisableLeasing`, but I'm looking for help here. Any suggestions? Thank you!
1 Answer
Make sure that both the server you're working from and the server you're trying to reach have the group policies applied properly. A restart can sometimes help, even if it's not usually necessary. If that doesn’t solve the problem, consider using Wireshark to capture SMB setup packets for further diagnosis.
Just to clarify, the server in question runs software that accesses UNC paths on itself. When users connect via RDP, they trigger an executable that tries to access its own folders. There’s no separate source and target server in this case.