Hello,
At one of our customers we implemented Always On VPN which works fine. We use the VPN connection to connect to file shares and a print server for the Azure AD joined device which also use Windows Hello for Business. DFS is also being used.
The situation is as followed. When we have a direct connection to the corporate network with a LAN or WiFi connection, everything works fine. I can connect directly to \\domain.local\dfs$\....
When I connect to the network from outside with Always On VPN, I can connect to \\servername.domain.local\share but cannot connect to \\domain.local (and not to \\domain.local\dfs$). When I start a remote desktop session to domain.local, we can connect without issues. So we just cannot connect to DFS namespace.
We are also not able to connect to any server based on DNS name (\\server\share), only with FQDN (\\server.domain.local\share).
VPN configuration are set equally comparing to an other customer which connecting to DNS name for opening shares works fine, and also have no issues with connecting to \\domain.local\. Difference is that they are not using DFS.
Anyone an idea which can help us out?