Hi We use a common folder which is shared on the network. We have mapped it to every computer as L: drive. No single user out of 180 users facing any issue..but one. This user has windows 7 professional 64 bit laptop. We have several other similar systems. Whenever this person opens L: drive, the explorer window starts showing a blue circle with not responding message on top. after 15-20 min, it will open up. He can access internet, network printers during this period without any issue. So he has good connectivity to office network. Other users with Windows 7 professional 64 and windows XP professional 32 are accessing same location without any kind of issue. What may be the reason for this not responding Network drive?
Have you tried changing Internet Explorer setting...? Weird I know..but reported to work even if IE not in use...
I am aware of this alternative. But we use mapping as the path is quite long and almost half of the time users are working on network folder files.
You could also create an .bat file with required parameters which should work without problems, or an Macro which maybe would be a better solution.
A little more information please. How is this one user connecting? Is it via a VPN, a local wired or wireless network, a docking station, a remote access server, or some other means? Given that you have a connection success rate of 99.44%, I say that one user has something wrong associated with either his computer or the manner by which he connects. Maybe he has a failing network card at bad cable or something as mundane as that. Not knowing exactly how he connects makes diagnosing the problem very difficult. Is he by chance using a personal computer to connect to a corporate system? If so, his firewall and antivirus may not be up to spec. Has he created a profile on another computer and tried to access L:? His profile may be damaged ... hard to know. If this problem persists and is a productivity problem, you may end up having to re-image the machine or get the user a different computer. Sometimes it's just simpler to sidestep the problem rather than attempt a real fix. If this is a business setting, time is money and the best solution may be to dump the machine and not keep expending resources getting you nowhere.