Map Drive Without UNC

5 pts.
Mapped drives
My customer purchased client mgmt software with multiple user licenses. The software developer says in order for the software to work properly in multi-user mode i need to load it onthe C drive of the server, fully share the C drive, and map this drive to the other computers without using UNC: " The MPN folder, which is installed on the server, must be on the root of the drive it is installed (i.e. C:MPN). The root drive needs to be fully shared … with full control/read/write permissions to everyone. In addition, security needs to be set up as full read/write permissions to group EVERYONE. Most operating systems require a new share be created for the root drive … the C$ default share will not work. The MPN folder does not get shared. " The workstation(s) gets mapped to the ROOT drive that the MPN folder resides (i.e C or D). All workstations must then be mapped, with a network drive letter directly to this drive. An example of a properly qualified data path - which can be viewed at Help>About from within ECLIPSE® - would be 'S':MPN " DO NOT use the Uniform Naming Convention i.e.: \serverc-drivempn " DO NOT map the drive directly to the MPN folder. It must be a full drive-to-drive mapping I am at a loss please help.

Answer Wiki

Thanks. We'll let you know when a new response is added.

When the client needs to access the files on the server, the company suggest not using “\\server\mpn”, instead they want “s:\mpn”, wher s: is mapped to \\server.

If the software gives you the option of where you want to install it at, install it to a location like “c:\program\mpn” and then share out the “c:\program” folder. If it doesn’t give you the option of where to install it, and you have to share out the entire c:\ drive, then the program is total crap. Call them and let them know your security concern. Surely they have a way to work around it.

The only way to map a drive would be to map to a UNC path.

I would take a hard look at the security changes you are going to be making. By allowing everyone full control over that network share you’ll be giving everyone full control of the OS volume of the companies server. If someone gets a virus on there computer it WILL infect the server and cause all sorts of problems.


I believe the vendor would have everyone map a local drive letter to the UNC path, then access the software through the local drive letter. This would typically be done through a login script.

Eclipse, hunh?

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • carlosdl
    I agree with Denny. Fulfilling those requirements will pose a security risk. As for the data path, what I understand from the posted text is that you have to map a drive (to a UNC path, which is the only option as stated above), and you have to use that mapped drive when configuring the software, and not the UNC path directly.
    84,805 pointsBadges:
  • Kevin Beaver
    You can use the subst command (at a Windows command prompt) to substitute a drive letter for a UNC. Trying subst d: \serverc$ at each workstation would likely be a way around this. Just be careful since sharing out drives - especially server drives - like this is a bad, bad idea. This is how internal security breaches such as password cracking (sam, ntdis.dit, and system files are accessible on the server) and unauthorized data access (basically any file on the server is fair game to any Joe user browsing the network).
    27,515 pointsBadges:
  • Pjb0222
    Giving everyone full rights to the ROOT of the server is something I would never do. Get your money back. Also, the requriement to install the software on the server OS partition is another "red flag" that screams find a different product. A simple NET USE is all you need for mapping the drive from the client.
    3,310 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: