I tried all the great suggestions here with no luck.
In another thread I read about network manager to keep shares alive. I tried it, but still no go.
I am close to my wits end here. I can't think of anything else to try.
It happens to all my networked drives.
I have 2 other computers, besides the HTPC on the network.
The main drive I try though is 750gb RAID 5 array.
I use the root and some folders for TV shows that I navigate to.
I also use a 300GB drive on another computer again using the root.
I did try to use a folder instead at one time, but that just so the same results so I went back to using the root.
markrb - But like NightmareRambo77 asked - how many folders are there on this root drive that you are trying to access on the networked computer?
Then I would like to know if the networked computer is Linux or Windows.
If it is Windows, what version (98, 2000, NT, XP Pro/Home) of Windows.
Is this through Samba (SMB) or with Windows Networking or maybe throgh NFS.
Basically we need more info to help us duplicate this problem so we can help in troubleshooting.
No matters if there is only 1 network folder or more on my MP folders list the slow response time still been too large. i work normally with 6 network folders from 4 differents comps.
I have two other PC's. The server and my main machine on the network. Most files are located on the server RAID 5 array. It's about 750gb's in size.
The server is simply another WinXP Pro machine with simple drive shares.
Most of the files are in the root. There are probably 60-70 files there.
I have 4 Directories in the root of the RAID drive. Each is a Different TV show. If I have multiple seasons then the seasons are broken into directories in the main folder.
If I get time I will move the sub folders to another drive so there are simply files in the share. If that works I will try creating shares of folders instead of drives. This way it always appears as a root drive. I will also force an IP on the Server and try to map using the IP address. It all comes down to time though. 12 hours a day at work leaves little time for the PC.
I ran a Cat 5 cable to my HTPC and tried it direct wired. There was no difference. I tried maping as network name instead of the share name with no difference.