Good morning,
This morning all of our office experienced slow logons and missing drives that should have been mapped to DFS shares.
No errors in any event logs on the servers, just the client, indicating that the server is unavailable. The DFS shares are accessible if I just go to run, and type in the same path name to the DFS share.
We have two targets at this site, an older server 2008R2 file server, and a newer 2012R2 files server introduced 3 weeks ago. We've been running this setup for 10 years with no problems, starting with 2003 R2.
I ran a batch of updates to the 2008R2 files server last night. None of the looked to be related to DFS.
I've tried retargeting to the 2008R2 DFS share by making the 2012 R2 one the last in the manually defined order, but there has been no difference. There doesn't appear to be any DNS issues between servers.
If I run a "net use h: /home" it takes a long time, then returns "Drive h: is now connected to \\mydomain\department. Your home directory is h:\it\Brad".
When I type h: it takes me to the DFS root, not to my home directory. We have another drive "I" which is a common DFS share that maps fine.
4 days ago I did remove DFS, DC, DNS services from another aging 2008R2 server with no problems at the time.
I can't tell what is broken without an error message. Where do I look?
Thx
B