Hi All,

I've created a new DFS namespace (\\company.local\Public) on Windows Server 2012 R2 in Microsoft Azure. As a reference I have used the following blog post: http://clemmblog.azurewebsites.net/high-available-file-share-in-windows-azure-using-dfs/

The next step was to connect a (domain joined) laptop to the Azure virtual network using the Azure VPN client. After connecting I can browse to the file servers and the shares that are present on the file servers but when I try to browse to the shares in the DFS namespace (\\company.local\Public\Data) I get the following error:

But when I ping the namespace (company.local) I get a reply.

 

I can also use Remote Desktop to connect to servers in my environment with the Azure VPN client active, it all falls apart when I try to browse to the dfs share. At the moment we're kinda lost for ideas so any hints or tips are welcome :)

P.S. I have configured DFSN to use the FQDN for use with workgroup machines.

Hi,

I assume the DC is not one of your DFS folder target - \\domain.local is an available DNS name which is genreally your PDC. So it will try to access your PDC for a shared folder "public" and if it is not availble, an error will occur.

Please have a try to add \\domain.local as a namespace server of that DFS namespace to see the result.

Hi,

Thanks for the reply, I've tried adding the \\domain.local as a namespace server but it fails when it tries to create the 'public' folder. This makes sense seeing \\domain.local doesn't actually refer to a server.

To make things more complicated, I've been testing with a VPN session to our local Fortigate firewall and then browsing the DFS namespace and this works perfectly. The problem only occurs when using the Azure Point-to-Site VPN client.

• Edited by Bas van der Kruijssen Monday, June 01, 2015 9:59 AM

Hi,

Have a try to use FQDN in DFS instead of NetBIOS name to see if it will get it to work:

https://support.microsoft.com/en-us/kb/244380