[SOLVED] Network drive in Windows 10

AtotehZ

Distinguished
Nov 23, 2008
403
13
18,815
Hello everyone,

I need to set up a network drive that can be easily accessed on my local network.

It will be set up on a Windows 10 pro server that's on 24/7 and has to be accessible from both Android, Linux and Windows.

What is the best way of doing this?
Back in WinXP I had no problem with this, but all the extra steps and finagling you have to do with permissions are kicking my ass and this time it just has to work.

If it was from Linux I'd just use Samba to create a network drive, but Windows 10 likes its network groups, unavoidable passwords, permissions and other BS.
 
Solution
Here is an older link from within this Forum:

https://www.tomshardware.com/news/h... computer that the,the drive over the network.

And:

https://www.tomshardware.com/how-to/map-a-network-drive-in-windows-10

The key is to plan out the location and sharing of the required network drive.

You know the location (server) then look at the applicable drive, partition, folder, etc.

List the computers and users that are to have access to the network drive and what control they will be allowed.

Get the network drive established and document (keep notes) on how you configured it. E.g. Drive letter and...
You could try FreeNAS (https://www.freenas.org/download/ ); it definitely works and it is very fast. It has its own O/S, but it interfaces with most anything. Installation is fairly easy, and the instructions are clear, but it does take time and repetition to understand them. FreeNAS works better with higher end components, such as ECC memory. You can usually find everything the FreeNAS hardware specs (suggestions) call for on eBay (or a big-box retailer such as Newegg , Amazon, or Walmart) at a decent price. Past-generation server components are fast enough and generally less expensive.

If and when you get a working system, disconnect the FreeNAS box from the WAN. Put the FreeNAS on a separate subnet, which you can do with an in expensive, consumer-grade switch, and two Ethernet ports on your main computer. Do not let FreeNAS update itself. Programmer turnover at FreeNAS is very high, and new people do not understand the software and do not care about your system. Don't let automatic updates destroy a working system and lose all your data. It can and will happen. Make backups of your data disks often. Have three sets, such as Week 1, Week 2, and Week 3, and then start over by putting Week 4's backup on Week 1's media. Statistically speaking it is almost impossible to lose data with this scheme. See Barbara Liskov's paper on this topic.
 
Here is an older link from within this Forum:

https://www.tomshardware.com/news/h... computer that the,the drive over the network.

And:

https://www.tomshardware.com/how-to/map-a-network-drive-in-windows-10

The key is to plan out the location and sharing of the required network drive.

You know the location (server) then look at the applicable drive, partition, folder, etc.

List the computers and users that are to have access to the network drive and what control they will be allowed.

Get the network drive established and document (keep notes) on how you configured it. E.g. Drive letter and path.

Then work to get one computer set up to access the network drive. Then, if necessary, specific users/accounts. And that will include establishing permissions or, if applicable, just leave the share wide open for any device or anyone to access and make changes.

Once you have a working template, then use that template as a model for other computers/users/accounts.
 
Solution
I don't think it's going to work. FreeNAS is its own OS. My server is a Windows 10 server.

It does look interesting though. Might use that for file sharing at LANs.
The O/S does not have to be an insuperable barrier to using FreeNAS. The latter uses FreeBSD for its O/S, and FreeBSD has a number of ports of well-known software you could use. Moreover, security of access is a big issue with FreeNAS, and it is well implemented and easy to use.