Hi there,
We have a similar issue with our systems at work, and it is directly related to the way our network structure is built. We could actually see the change when we moved away from a pure Novell Netware environment to running Netware, Microsoft Server 2000 and a storage area array. (It gets really complicated!) I find that drilling into a directory is okay, but if I go back up... well... I wait. Then it seems to run okay. What's happening in our case is that one server is talking to another, which is talking to our storage array, then passing the info back along the same path... and naturally Microsoft and Novell talk really well! You may not be in a mixed environment, but if you are, that could be it.
If Matt's tips don't work for you, and you have one, I'd suggest talking to your IT department and complaining about the speed. They may be able to do something, and may not even realize that there is an issue.
Ken
Main Topics
Browse All Topics
by: mvidasPosted on 2005-01-04 at 06:42:18ID: 12952391
Hi hazenoff,
That usually happens when one of the drives is unavailable. The same thing happens to me with one of my network drives, usually freezes for 30 seconds or so. The only real way around it that I know of is to disconnect the slow network drive(s) from your My Computer. You can tell which drive it is by clicking on My Computer, as the slow drive should stall that too. When you open My Computer, you'll see the list of drives A C D E etc. Whatever the first drive is you can't see right away is the offending one. Note that if you've refreshed your list of drives recently (by using the path like you explained above), it may not slow down. It only happens to me if I haven't listed the drives within the past 30 minutes or so. This sometimes happens with a CD or DVD drive as well, so you could try removing any discs before going to the path.
Matt