DSM-G600, DNS-3xx and NSA-220 Hack Forum

that mapped drive should be \\   not // sorry

\\192.168.0.100\Volume_1

Go the noob factor!

"net use" command (from a command shell - cmd.exe) is the easiest way to get exactly what you want without having to describe complicated GUI flows. Off-hand I don't know any reason an IP would be better than a  name; you can have persistence with either.

Here's the help output for net use (from an XP machine; I'm not aware of any important differences on Vista):

C:\Documents and Settings\Jeff>net use /?
The syntax of this command is:


NET USE
[devicename | *] [\\computername\sharename[\volume] [password | *]]
        [/USER:[domainname\]username]
        [/USER:[dotted domain name\]username]
        [/USER:[username@dotted domain name]
        [/SMARTCARD]
        [/SAVECRED]
        [[/DELETE] | [/PERSISTENT:{YES | NO}]]

NET USE {devicename | *} [password | *] /HOME

NET USE [/PERSISTENT:{YES | NO}]

Real examples:


Map S: drive to my DNS323 (named storage) by name (my PC username/password matches the one I configured on the DNS323) and force persistence (I think that's the default when using net use on XP anyway; but being explicit can't hurt)

C:\Documents and Settings\Jeff>net use /PERSISTENT:YES s: \\storage\Volume_1
The command completed successfully.

Same thing by IP address (unnecessary IMO):

C:\Documents and Settings\Jeff>net use /PERSISTENT:YES s: \\192.168.1.13\Volume_1
The command completed successfully.

Let Windows pick the mapped drive (instead of fixing it to S: ):

C:\Documents and Settings\Jeff>net use /PERSISTENT:YES * \\storage\Volume_1
Drive W: is now connected to \\storage\Volume_1.

The command completed successfully.

Same as the first option; but use a different username/password on the DNS323 versus PC (final * causes prompting for password)

C:\Documents and Settings\Jeff>net use /PERSISTENT:YES /user:dns323user s: \\192.168.1.13\Volume_1 *
Type the password for \\192.168.1.13\Volume_1:
The command completed successfully.

Look at what's mapped (note the confirmation that persistence is the default on my machine):

C:\Documents and Settings\Jeff>net use
New connections will be remembered.


Status       Local     Remote                    Network

-------------------------------------------------------------------------------
             S:        \\192.168.1.13\Volume_1   Microsoft Windows Network
             W:        \\storage\Volume_1        Microsoft Windows Network
             X:        \\storage\Volume_1        Microsoft Windows Network
Disconnected Y:        \\srv1\s$                 Microsoft Windows Network
             Z:        \\storage\Volume_1        Microsoft Windows Network
Disconnected           \\srv1\c$                 Microsoft Windows Network
                       \\storage\Volume_1        Microsoft Windows Network
The command completed successfully.

Finally; unmapped something (and remove it from remembered mappings), * instead of "s:" would delete all mappings:

C:\Documents and Settings\Jeff>net use s: /d
s: was deleted successfully.

Hope this helps.

-Jeff

Just a quick comment - you can map a drive to a share, and you can specify that share using either it's ip address, or it's NetBIOS name - but to describe these as mapping to an ip and mapping to a pathname would be incorrect and should be avoided so as to reduce confusion.

If you want to experience where I'm coming from - try to map a drive to the ip address of your router - it's a valid ip address, you can ping it, but since there is no share on that device, you won't be able to map a drive to it, in a similar fashion, try to map a drive to the ip address of a DNS-323 with two disks - you can't - you will be forced to choose between the two shares that are available - Volume_1 & Volume_2.

I'll come back to the pathname a bit later.

Using what is known as UNC or Universal Naming Convention - you can map the drive to the share using it's NetBIOS name or it's ip address, the syntax is \\servername\share or \\ipaddress\share for - example \\DNS-323\Volume_1 or \\192.168.0.32\Volume_1 - both of these have advantages & disadvantages.

Using the ip address works well if you are using static ip addresses, but if your ip address is set by DHCP, it may change and then your drive map will fail - using the NetBIOS name is one way of getting around this, but in mixed OS environments it can be problematic depending on the versions of SAMBA etc.

Now - path names - I have not seen it discussed much here, but a drive can be mapped to a folder within a share, rather than a share itself - and this would take the form of \\server\share\path - or - \\server\share\pathname - for example - if I created the following folder structure on my DNS-323 ....

On Volume_1, I create a folder called users, and within users, I create folders for each user - user1, user2, user3, etc.

A drive can now be mapped to \\DNS-323\Volume_1\users\user1 and from that system there would be no direct access to the user2 & user3 folders - (please note that this should be considered for convenience and not security, because if the drive map is done to high up in the folder structure, the user has access to all the "lower folders")

As I said before, I point this out simply to suggest the use of correct terms and hopefully reduce confusion

fordem wrote:

I point this out simply to suggest the use of correct terms and hopefully reduce confusion

:-/ I'm confused ...

I thought that "mapping a drive" meant that a drive letter was assigned on the client PC to use as a shortcut to some network share. See for example the Tools > Map Network Drive option in Windows File Explorer, or type "map a drive" or "mapping a drive" in to Help and Support in Windows.

For example, at work my H: drive on my client is mapped to a network share on a server, so I can open h: to see my files instead of having to open \\server\users\bing

When you configure a folder to be shared by the DNS323, like your users1 example, I thought that was "creating a share"?

I thought that using a UNC path like \\myDns323\myFiles or \\192.168.0.10\myFiles was "using a share", because I haven't created a drive letter mapping?

== edit ==
cd h: -> open h:
as Fordem noted.

Last edited by sjmac (2008-04-20 21:49:54)

sjmac - I'm not certain that I understand your confusion.

It's exactly as you say - the "share" is created on the device that stores the data - if you like we can call that the "server", and it may be used directly as a share - \\<server-name>\share or \\<server-ip-address\share, or  you can map a drive letter to it and call it, as in your example H: - something which is primarily done for ease of use, especially when the user is not familiar with shared resources.

Whether or not you choose to map a drive letter is optional, but, and this is my point, strictly speaking, you cannot map a drive letter to either an ip address, or a pathname - you MUST map to a share.

First you create the share and then you choose if you want to use it directly or if you want to map a drive letter to it.

Edit..

Ore more thing - and again strictly speaking CD (or CHDIR) is a command that allows you to navigate a folder or directory structure - it does work when switching drives, but so does entering the drive letter itself

Last edited by fordem (2008-04-20 21:32:19)

fordem wrote:

sjmac - I'm not certain that I understand your confusion.

From your reply I guess my understanding wasn't wrong and I am using the right names for things. Your "correct terms ... to reduce confusion" post suggested to me that mapping a drive was something else when I read it.