Windows 10: Network Shares mapped to DFS namespace. On boot PC cant see the path

OK i have been scouring the internet to find the issue but i cant seem to figure this out. About 2 weeks or so we started to have an issue where on boot user drives wont map correctly. We have the user drives mapped to a folder in the \\domain\Public namespace but for some reason windows doesnt see the location untill you enter the path in file explorer. For example. I have a U drive mapped to \\domain\Public\Usershare\Name. When i reboot my machine and log back in i can run a cmd to try to map a network drive manually and it fails saying that the path doesnt exist. if i go directly to the pat

:)

 

DFS Namespace issue

I've got an issue with network shares containing shortcuts of themselves. This creates and endless loop when searching, among other issues. When attempting to delete the shortcuts, I would receive errors. Using fsutil i was able to find that these shortcuts
are DFS Reparsepoints, and also was able to remove the reparsepoints and delete the folders (article). But they
kept coming back.

It took a really long time, but I finally figured out that each of the shares with this issue has a DFS Namespace set up, and I believe that the issue is how the targets were created. For instance the shares with this problem exist as such: \\Server1\Share1
and \\Server2\Share1 (these are replicated to each other). The namespace is listed as \\DomainName\Share but its namespace path is \\DomainName\Share1\Share1. I believe this is causing the namespace to create this reparsepoint INSIDE the share instead of
AS the share.

I hope this isn't coming across as gibberish. How do I fix this? I can't simply edit the namespace path, and I'm afraid deleting the namespace itself will break everything.

 

DFS Namespaces on Windows7/10

Hopefully someone can help me figure out this issue we are having...

We want to use DFS Namespaces to house files in one central location across all branches, it is setup and working properly at the central office the namespaces are setup at regardless of operating system (windows 7/10). Heres where the confusion comes in,
at all other offices, no one using windows 7 can access the namespaces or the network shares that the namespace replicate from. They will get an arbitrary error saying you dont have permissions to access this, which they do, and when they would go to access
a network share being replicated from it wants a domain login which none work...even a domain admin account will not grant access. Windows 10 users, no problem, they can access everything.
What is windows 10 doing differently than windows 7 to enable this access or where did we go wrong setting up the namespaces?

 

Computer not able to access one DFS path

Hello all,

Here's the situation:

A computer doesn't have access to a DFS path. The same user can access the dfs when he tries from another computer. The drive maps is deployed by GPO. The GPO is configured for Users, not computers.

These are the steps that I followed:

1 - If I map manually the path without using dfs, it works. If I try access using the dfs path... nope.

2 - The netlogon on the computer is running (as automatic).

3 - Removed the pc from the domain and rejoining. Same issue after that.

4 - There's no \ in the end of the DFS path, and it's not an issue on other PC's.

These are the errors from Event Viewer:

Event ID: 8192

Task Category: (2)

Level: Error

Keywords: Classic

User: SYSTEM

Description:

The user 'N:' preference item in the 'GPO - DRIVE MAPS {....}' Group Policy object did not apply because it failed with error code '0x80070035 The network path was not found.' See trace file for more details.

AND

Event ID: 7320

Task Category: None

Level: Error

Keywords:

Description:

Error: Computer determined to be not in a site. Error code 0x77F.