Link to home
Start Free TrialLog in
Avatar of jlavery
jlavery

asked on

slow browsing network drives when accessing through office

I have a clien tthat has a windows 2003 server with sp2.. its build up preety good. GB switch, the works. all the clients have office 2007 fully updated and when they access network drives through office its really slow. access through windows explorer (my computer) is not an issue, its only offiice. i mentioned offce 2003 as well since i have the same issue on my own LAN, just not as cranky about it.
Avatar of Will Szymkowski
Will Szymkowski
Flag of Canada image

Hello there,

Possibly already done/tried but have you made sure that all of the office patches are up-to-date? Service pack 3 seems to fix a lot of issues.

Keep us updated
ASKER CERTIFIED SOLUTION
Avatar of jlavery
jlavery

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
This is an ENDLESS problem with MS office, it has existed since word 2.0 and they have never fixed it.  the problem is that word will NOT release old drives from the queue, like if you once read a file from a floppy disk, but now there is no disk in the floppy drive, word will hang forever looking for a floppy disk.  It is the ultimate stupidity, and a good reason why you should migrate all users to open office -- www.openoffice.org.   It is FREE, and it is 100s of times better than MS office.

If you MUST stick with M$ office, tell the users to use windows file manager to find files, copy them to the local disk, use word to edit files ONLY on the local disk and no where else, and this problem will vanish in a week.  As long as users are editing files in word directly on network shares or local disks, you will NEVER fix it in a million years.
Do they have any persistent mappings to network drives that no longer exist?

Or drives that are mapped for remote locations?
you won't find a fix, as I said above, it is an MS Word and MS Office problem, and it has never been fixed by M$.  The only solution is to teach all users to copy files from network shares to the local hard drive usiing windows explorer, edit the file, and then copy it back.  This can all be done in less time than it takes waitig for MS office apps to find a remote file, which can be minutes.