Sub-Folders and file in DFS share are missing

I added a new 2016 server to our DFS.

DFS Replication has replicated all files, however, when I connect to the share I don't see all the folders and files. I verified that I am connected to the local server from the client, but not all the files appear.

Access based File Enumeration is turned off.

Thanks for the help.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
How did you verify that DFS-R replicated "all" files? If some are missing, my first guess is that replication is nit yet complete.
byt3Author Commented:
On the new server I browsed to the folder that contains the files. (Eg. E:\DfsShares\NamespaceFolder) to see all the files there.
When I browse to the share from a client at the site with the new server, I don't see all the files and folders (Eg. \\domain.local\NamespaceFolder).
Cliff GaliherCommented:
Where, specifically, did you check ABE?
 Acronis Global Cyber Summit 2019 in Miami

The Acronis Global Cyber Summit 2019 will be held at the Fontainebleau Miami Beach Resort on October 13–16, 2019, and it promises to be the must-attend event for IT infrastructure managers, CIOs, service providers, value-added resellers, ISVs, and developers.

byt3Author Commented:
Sorry, not sure what you mean by ABE.

We have a namespace called Kithomes$ that is shared from E:\DfsRoots\Kithomes$ on 4 servers (including the new one). I have Dfs replication setup to replicate that E:\DfsRoots\Kithomes$ folder.

When I go onto the new server and browse to E:\DfsRoots\Kithomes$ I see a folder named 1718. When I am on a client and browse to \\mydoman.local\Kithomes$ I don't see the folder 1718.

On the client if I open the properties of the share I'm connected to and go to the DFS tab, I see that the new server is the DFS Server that the client is connected too.

Does that answer your question?
Cliff GaliherCommented:
ABE. Access Based Enumeration. A mismatch in DFS causes very strange behavior.  You should never set it on shares directly, and o ly enable or disable via DFS. I was asking where you disabled or checked it. I'd recommend enabling and re-disabling via DFS or ise DFSUtil just to be safe.
Cliff GaliherCommented:
I'd also be curious what happens if you bypass DFS-N and went to \\server\share$ directly from a client. That way you are using SMB, but not relying on DFS targets. One less step in the chain.
byt3Author Commented:
Enabled and Disabled ABE using server manager for the share on the new server and also did the same in the DFS Management console on the namespace. Didn't seem to help.

Accessing it by \\server\kithomes$ had the same results.

I'm totally stumped by this.

The existing servers are 2008 and the new server is 2016, if you think that makes a difference. All 4 servers replicated with one server at our HQ and it is 2012.
byt3Author Commented:
Connecting to \\server\e$\DfsRoots\Kithomes$ will reveal all the files. So just straight SMB works fine. There is something about the DFS namespace that doesn't show all the files.
Cliff GaliherCommented:
"Enabled and Disabled ABE using server manager for the share on the new server "

That's exactly what you should NOT do. ONLY use DFS tools.

At this point i'd remove the target. Remove the share. Then recreate the share then recreate the target. This *really* sounds like ABE gone awry and now the cache is screwed up. That's the fastest way to reset the cache.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
byt3Author Commented:
No dice. Going to remove and re-add the DFS Namespace role, which requires a reboot, so I'll have to schedule that.
As a last resort you could try to enable / disable ABE via the DFS tools to see if it will correct any inconsistencies. I am not hopeful but work a shot.
byt3Author Commented:
Sorry for the huge delay in response.

After doing removing the DFS Namespace role and re-adding it later. It works.

I don't know if the long delay before I was able to look at this issue had anything to do with it though.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Distributed File System (DFS)

From novice to tech pro — start learning today.