Windows 7 accesses too many network drives

Fujitsu / Amilo pi 3560
January 28, 2011 at 06:42:42
Specs: Windows 7 Home Premium, 2.2 GHz / 4060 MB
Bit of an obscure problem, at least I haven't been able to find a solution anywhere, so here goes:

On my home network I have a Linux file server with two drives,
/fil (mapped as i:\), which contains day-to-day stuff that i use all the time, and
/fil2 (mapped as j:\), which has some old large stuff I rarely access, maybe a couple of times a month.
So I have the server configured to spin down /fil2, since I hardly ever use it, and the disk is old, noisy and annoying and in my bedroom.

Now, this setup has been working great for years while I've been using primarily XP-based computers to access them as mapped shares.
However, since getting a new laptop with Windows 7, when I open i:\ in Windows Explorer after some downtime, the server spins up /fil2 as well, which seems totally unnecessary, and I'd prefer to have not happen.
There has been no change in the server configuration, and the other computers (still XP-based) that I've tested it with still leave j:\ alone when accessing i:\ as they should, which leads me to believe that it is indeed a Win7 problem.

If anyone has some insight into what may be causing this unnecessary "double" access or knows how to troubleshoot it, it would be much appreciated, thanks.


See More: Windows 7 accesses too many network drives

Report •

#1
January 28, 2011 at 08:16:00
Might be worth a try to turn off network discovery. This is assuming you have not mapped a drive to this j: on the laptop. If you have I would undo that and then see if fil2 gets spun up.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
January 28, 2011 at 08:35:00
Yeah, /fil2 is mapped to J: permanently as I've always done. I'm not sure of the network discovery settings on my old XP laptop (which didn't have the problem), though, so I've tried turning that off now, while leaving the mapping in place.
Waiting for stuff to spin down now and I'll get back to you, thanks :)

Report •

#3
January 30, 2011 at 07:09:59
Ok, so turning off network discovery didn't do it :/
I guess I'll leave it unmapped for now and make a bat file that maps it and opens it in Explorer or something.

Or install XP.

Thanks for the input.


Report •
Related Solutions


Ask Question