Each computer that is going to share a folder or entire hard drive has to have this share first created.
Then you need to join the computer to those shares at as many computers as you have.
Generally a mapping assumes a drive letter that is not used locally to that one system. So if you had 5 computers and you want to map a share to the C: drives, then at that 1 computer that has access to the other systems drives, if your system was configured with:
C: = Hard Drive
D: = DVD/RW Drive
E: = ( Available, but commonly used with flash devices )
F: = ( Unused )
And G: thru Z: also unused
I would start creating the mappings at Z: and work your way backwards to F: , this way you never have a conflict of 2 devices assuming the same drive letter.
So if you have 5 computers to connect to from the 6th computer, then from the 6th computer you can have mappings of:
Z: = computer #1 C: drive map
Y: = computer #2 C: drive map
X: = computer #3 C: drive map
W: = computer #4 C: drive map
V: = computer #5 C: drive map
BUT.... you have to set these up manually 1 by 1, however if you are going to have more than 1 computer associating with say these 5 computers and you want them to assume the same mappings, you can create a batch file with NET USE and PERSISTENT switch to keep the mappings after shutdown of the computer. This script only has to be used once at each system ( or for each profile / user on that system, unless added to all users in which local configuration profile inherritance gives all users present and future the shares the very first time that the user logs on to that system and the profile is created. )
/persistent:{yes | no} = Use this option to control the persistence of connections created with the net use command. Choose yes to automatically restore created connections at the next logon or choose no to limit the life of this connection to this session. You can shorten this switch to /p if you like.
As seen here:
http://pcsupport.about.com/od/commandlinereference/p/net-use-command.htmLastly, for corporate or those who have money to have their own client/server environment of their own, you can do this in group policy as well.
http://www.howtogeek.com/99403/it-how-to-map-network-drives-on-windows-clients-via-group-policy/