OK, this is my first Microsoft DirectAccess deployment, so maybe I'm just lost in translation.
I have Windows 8.1 clients connecting to a 2012 R2 multisite DirectAccess setup (2 DA servers for global load balancing).
Once the clients are setup and working for the most part all is good. They can access internal resources for the most part, and client Powershell diag cmdlets for DirectAccess come back with expected good results and I can ping internal resources and get the proper IPv6 response as required.
The odd part starts when we browse CIFS server shares.
I can pull up a server via UNC path, such as \EXAMPLENAS and see the shares. However when I click on any of the shares (let's say IT) I get an error "the request is not supported" as shown below:
(sorry for the obscurity, but you get the idea)
But oddly enough, if I map a drive to that same share, say Z: to \EXAMPLENAS\IT then it immediately maps and opens the Explorer window to the share while still on DirectAccess only.
So my questions are:
- Is that something by design? If so that's frustratingly odd.
- If it isn't by design, is there a fix for this issue?
I've checked all through the DA server setup/config and there really isn't anything that I can find that even hints at something like this, and so far every search on MS KB, Google, SF, and others seem to have been fruitless.