Since we moved to DFS we see reoccurring pattern which we have never\nexperience before. We are 95% mobile clients environments meaning we almost\ndo not use desktops, 95% of users are on laptops. As long they in LAN or VPN\nall works well but as soon a user is working offline strange thing happens,\nanytime a user opens windows explorer or MS office application and try to\nbrowse for a file on local C drive it takes good 5 minutes to fully open\nwindows explorer, basically window will open but then we see flash light\ngoing back and forth for few minutes. This only happens when user is offline,\nIâ€™m assuming it is because XP client is trying to access map network drives\nand takes long time to quit trying. I have never seen this before until we\nhave switch to use DFS. Any Idea how to fix this? Other then disconnecting\ndrives on log off, I tested it and if map network drives are not present in\noffline mode this problem doesnâ€™t exist because XP client is not trying to\naccess network drive since they are not there. Why this is not a solution?\nCould be if 100% people are shutting down or logging of while leaving office\nbut they donâ€™t most of them either hibernate or standby they laptops or\nsimple disconnect from LAN and walk away, so we cannot guarantee that their\nmap drives will be gone as they go offline.\nSo again do you guys see this as well with remote folks and any idea how to\nfix this? I will also mention something that I think is related, I noticed\none difference between using â€œoldâ€ way mapping vs. DFS, previously when XP\nclient was disconnected from LAN in windows explorer under Type map network\ndrive had status â€œDisconnected Network Driveâ€ now since we moved to DFS it\nalways regardless if connected or not Type is â€œNetwork Driveâ€.