asked on 1/23/2019

DFS Issue

I have a server 2012 R2 running DFS.There is also another server 2012 r2 that has a share on there using DFS as well. I have 4 DC's, 2 onsite and 2 at another site. Everything was working correctly right up until I ran updates to all my servers and reboot them to apply updates. Now I am getting people randomly telling me that they cannot connect to shares when signing in. After a few reboots they could. I have checked DNS and it looks good. When a user is at a broken state, What always works is the home drive which is applied on the profile tab in AD. That is referenced to a dfs share. What sometimes works after a few reboots is the logon script that has the rest of the peoples drives that they haven't been getting consistently. Does anyone have an idea of whats going on. Thanks a head of time.

Windows Server 2012 DNS REST Microsoft Server OS Networking

Last Comment

Steve

1/29/2019

MVP IT

1/23/2019

ASKER

I forgot to mention when being in the broken state to fix it fast I go to windows explorer and type in the path to the dfs share. If I hit enter it will error out and tell me the path doesn't exists. Its only when I press the browse button and browse to the path I then run the script manually it works.

Steve

1/24/2019

OK, to clarify, is it only shares using DFS that are failing? do you have other shares also showing issues (e.g. sysvol or netllogon on the DCs?)
Do you use DFS Namespaces (e.g. \\<domain>\Share) or normal share access (e.g. \\<servername>\share)?

Check the event viewer on both DFS servers as there is a section specifically for DFS. check application & system too. Any errors showing?

MVP IT

1/24/2019

ASKER

It's just the shares using dfs. other drives that are from the script map fine but are not using dfs. For dfs names we use \\domain\share.

Steve

1/24/2019

Did you check event logs on the dfs servers as above?

ASKER CERTIFIED SOLUTION

MVP IT

1/28/2019