The purpose of NDC is to have Windows automatically map network drives by network name when you logon, just like Windows can be made to set the default printer by network name.*
Windows Vista, 7, 8 & 10
You are viewing this site from IP Address: 184.108.40.206
The above IP address is called: ec2-54-224-164-166.compute-1.amazonaws.com
copyright Michael J. Burns
v1.20 Release date November 4, 2017
Have Windows default mapping of network drives be network dependent, similar to how the Windows default printer can be set to be network dependent.
Network Drive Control (NDC) for Windows Vista, 7, 8 & higher, both 32-bit & 64-bit, is an example of a utility I wrote to solve a frustrating problem I frequently encountered, namely wanting my network servers, both at work & home, mapped to Windows drives in a network specific manner. While one can tell Windows to try to map all of the drives at logon, I didn't like the long delays waiting for the time outs of the drive mapping for the networks that are not connected. (i.e. Waiting for the mapping of the home network drives to timeout when on my work network, and vice versa.) So I wrote my own utility which would examine the network environment after I logged in, and based on what network it found itself on, it would only attempt to map those drives it knew were on that network. Basically, I wanted the map network drives on login to function equivalently to the way the Windows "default printer" does by being network specific. (Start → Devices and Printers → Manage Default Printers) The short of it is I wrote a two module program to do just that, and hence Network Drive Control was born.
Network Drive Control allows you to configure the automatic mapping of network drives when you logon based on the network(s) to which you are connected. An example would be to have your laptop automatically connect and map one set of network drives when at home, and another set of network drives when at work or school, and none if it detects that the PC is connected to a network where no mappings have been configured.
Network Drive Control has no limit to the number of networks or drives that can be configured (except Windows built in limits), and drive letters can be redundant. i.e. If on one network you like a resource to be mapped to drive, say, X:, and on a different network you'd like to have a different resource also mapped to X:, you can configure Network Drive Control to do so.
Network Drive Control utilizes Windows features built into Windows Vista through 10 (both 32-bit and 64-bit), and supports drive mapping via Server Message Block (SMB), Common Internet File System (CIFS), Netbios, as well as WebDAV..
Network Drive Control is free and has a built in help function.
We add the usual weasel words that there are no warranties that this software will work correctly or will even run on your machine, and that you use it at your own risk.
Note: Cisco QuickVPN, used by some Cisco small business routers, does not allow the use of network names, and so Network Drive Control won't be able to identify the remote network. This is an issue within Cisco QuickVPN, not in Network Drive Control. Cisco's AnyConnect used with Cisco's enterprise class routers does not have this issue.
Click here to download locally
Click here to view the Release Notes
Feedback can be sent to me at
*Yea, I know. Many implementations of
Window 8, and every Windows 10 I've seen, don't have "Manage default printers"
on the "Device and Printers -> Printers and Faxes" toolbar anymore, and Windows
10's "Let Windows manage my default printer" is problematic.
When my annoyance level gets high enough, I'll write an NDC-like utility to give back that type of control.