How to fix the inaccessibility of SMB resources on the local network when the VPN is up?

Question

VPN

I am building L2TP over IPSec, the default gateway in the VPN connection setting is disabled. Network 192.168.88.0/24, in the local network from where the tunnel is being built, there is no such network. In general, everything works fine, but there is one thing - when the tunnel is raised, local resources via smb stop working. When I try to log in, I wait a couple of minutes and then I get an "Extended Type Error". And so only by the domain name, by IP-address goes. DNS in the VPN settings are local or removed altogether (there is no difference here). Where to dig?

Answer 1

The problem was solved by prescribing ONE DNS server in the IPv4 VPN connection protocol. After that, a problem appeared that when connecting to a VPN, a *Session entry is created in the account manager, which contains the login and password from the VPN connection. So SMB uses this entry as a priority. The solution is the following (via technet):

You can disallow the credential to be stored in the Credential Manager by setting the following registry entry to 1:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
Value Name: DisableDomainCreds
Value Type: REG_DWORD
Value: 1