2010-02-08 15:53:01 UTC
experience before. We are 95% mobile clients environments meaning we almost
do not use desktops, 95% of users are on laptops. As long they in LAN or VPN
all works well but as soon a user is working offline strange thing happens,
anytime a user opens windows explorer or MS office application and try to
browse for a file on local C drive it takes good 5 minutes to fully open
windows explorer, basically window will open but then we see flash light
going back and forth for few minutes. This only happens when user is offline,
I’m assuming it is because XP client is trying to access map network drives
and takes long time to quit trying. I have never seen this before until we
have switch to use DFS. Any Idea how to fix this? Other then disconnecting
drives on log off, I tested it and if map network drives are not present in
offline mode this problem doesn’t exist because XP client is not trying to
access network drive since they are not there. Why this is not a solution?
Could be if 100% people are shutting down or logging of while leaving office
but they don’t most of them either hibernate or standby they laptops or
simple disconnect from LAN and walk away, so we cannot guarantee that their
map drives will be gone as they go offline.
So again do you guys see this as well with remote folks and any idea how to
fix this? I will also mention something that I think is related, I noticed
one difference between using “old” way mapping vs. DFS, previously when XP
client was disconnected from LAN in windows explorer under Type map network
drive had status “Disconnected Network Drive” now since we moved to DFS it
always regardless if connected or not Type is “Network Drive”.