Dear Guys,
I have a problem and no idea what to do, please help! One of our customers have a Windows Server 2012 R2 Essentials server, which has SMB1 feature installed and enabled because of some old scanner. They have ~15 client computers, most of them works correctly with the server's shared folders, but some of them is not.
Now I'm working on it remotely, making a VPN connection through SSTP and try to reach the server with it's IP address (\\192.168.1.5), after 15-20 seconds I got error code 0x80070035 on 1 client and 0x80004005 on 2 other clients. I'm trying to reach the server's shared folders with one of the custumers Windows 10 PC's (1803), and from their branch office server which is running Windows Server 2008 R2, and from my own Windows 10 PC (1803). None of them is a domain joined computer, however there're a few working, but not domain joined computers. SSTP connection is set on all of them used with the remotewebaccess.com certificate, connection works correctly, as some clients are working correctly through that and they can reach the shared folders.
We have other Windows Server 2012 R2 Essentials servers with SSTP and file sharing, I had made some investigation yesterday. I'm connected to them by SSTP, tried to reach shared folders from my PC and all of them was working. Then I had downloaded an SMB test program which can test all of the SMB versions and found that all of these servers were successfully tested through VPN on every SMB versions, and our server in our network is successfully tested too. The program not resolves the problematic server's name by Netbios (it is enabled on all of the interfaces), and tries to test SMB1 and got a timeout, so it is not testing other SMB versions. I think it can be a problem with the enabled SMB1 protocol, which is the only difference with the tested and the problematic server. None of the others have SMB1 enabled.
If there's no other idea I'll try to remove it in the evening, but I have to try another solutions because they need to use SMBv1 and other clients are still working, so there should be a solution.
I have tried tons of registry hacks as forums mentioned for this error codes but nothing has changed. Do you have any new idea what to do?