|
Your download link is at the very bottom of the page... always. |
Processed through Paypal No account required. Donate Bitcoin to this wallet: 1KkUMXvQ2ko3xcJkzitB7WYgoW6m79WFfm Donate Ethereum to this wallet: 0x40E56922F43637224935CDC35e2c96E0392A8505 Donate Litecoin to this wallet: LLYAFEyqjH69gkyCEpRjXNyedRCWrVChfL |
Home » OlderGeeks.com Freeware Downloads » Networking and Port Forwarding » Network Drive Control (NDC) v1.67 | File - Download Network Drive Control (NDC) v1.67 | ||||||||
| Description | ||||||||
|
Always scroll to the bottom of the page for the main download link. We don't believe in fake/misleading download buttons and tricks. The link is always in the same place. Network Drive Control (NDC) v1.67 Authors description: "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, 10 and 11, both 32-bit and 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 and 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 7 "default printer" did by being network specific. (Start → Devices and Printers → Manage Default Printers) The short of it is I wrote a modular 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 to a drive letter via Server Message Block (SMB), Common Internet File System (CIFS), Netbios, WebDAV, as well as map local directories to a drive letter. (Note: Windows does not natively support drive mapping to a drive letter via FTP, so neither does Network Drive Control. Windows only natively supports "network place" mappings via FTP, and those network place mappings do not have drive letters. There are commercial products out there that can map drive letters via FTP though custom drivers.)" "Network Drive Control is free and has a built in help function. All binaries are signed, including the installer." "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 flaw in Cisco QuickVPN, not in Network Drive Control. Cisco's AnyConnect used with Cisco's enterprise class routers does not have this issue." Changes v1.67 - September 4, 224 1. Switched the development machine to Windows 11 Pro. 2. Fixed bug where NDC would sometimes report Windows 11 as Windows 10. Of course it reported Windows 11 correctly when run on Window 10 when tested in my Windows 11 VM, but now that the NDC development has been moved to a bare metal Windows 11 system, it misreported it. 3. Added a checkbox to each line that tells NDC not to automatically map the drive even if the PC is on the correct network for that drive. I added this mainly to help with trouble shooting. I found that it was useful because I have an occasional need to map the USB backup drives that are on my NAS. One could always have used NDC this way simply by setting up mappings with manually entered nonexistent Network names, and then using the "Connect" button. But being able to set the mapping up correctly so one can automatically connect if need be, but just toggle the function on & off, is less of a kludge. 4. Updated help files. Click here to visit the author's website. Continue below for the main download link. |
||||||||
| Downloads | Views | Developer | Last Update | Version | Size | Type | Rank | |
| 5,876 | 12,749 | Michael J. Burns <img src="https://www.oldergeeks.com/downloads/gallery/thumbs/Network Drive Control1_th.png"border="0"> | Sep 08, 2024 - 12:34 | 1.67 | 2.27MB | ZIP |  , out of 71 Votes. |
|
| File Tags | ||||||||
| Network v1.67 Drive Control (NDC) | ||||||||
Click to Rate File Share it on Twitter → Tweet
|
