Comments on: Map Drive Without UNC

By: pjb0222

pjb0222 — Wed, 16 Dec 2009 16:30:13 +0000

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.

By: kevinbeaver

kevinbeaver — Thu, 03 Dec 2009 13:11:40 +0000

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).

By: carlosdl

carlosdl — Thu, 03 Dec 2009 00:02:48 +0000

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.