I can map folders within a network share to a drive letter. For example, by typing 
on the command line:

net use X: \\10.0.0.1\porn

I map the X: drive letter to the shared "porn" folder on \\10.0.0.1
I can also do this from a windows explorer window and choosing Tools > Map Network 
Drive.

However, this does NOT work when I try to map \\10.0.0.1\

When I type net use X: \\10.0.0.1\ I get "system error 53, the network path was not 
found".
And when I try to do it through Tools -> Map Network Drive, it seems waiting forever 
(no error, but nothing happens until I eventually cancel it).

Can someone tell me how to map an entire share, or is this really impossible?

Tip: Run a free scan for common Windows errors ad

re: Can map folder in share, can NOT map the share itself :( Saturday, March 21, 2009 at 12:32 pm Posted by mojoe (1327 messages posted) Open windows explorer and click on 'Tools' on the top drop-down menus. Then select 'Map a network drive' and browse to the drive\folder where you store your xxx files. [Reply or follow-up to this message] re: Can map folder in share, can NOT map the share itself :( Saturday, March 21, 2009 at 1:02 pm Posted by geek9pm (286 messages posted) Why do you use: net use X: \\10.0.0.1\porn instead of the name of the share? Like this: net use X: \\Share-porn The directory \porn may or may not exist on \\10.0.0.1 all the time. Did you find a reference that said you can use \\10.0.0.1 rather than an explicit name for a share on another computer? Geek9pm [Reply or follow-up to this message] re: Can map folder in share, can NOT map the share itself :( Sunday, March 22, 2009 at 8:13 am Posted by Banana (31 messages posted) Thanks, I actually tried referring to the other machine with it's IP as well as with its network name, but neither works. So I tried these both: ("fileserver" being the network name for the machine with ip 10.0.0.1) net use x: \\10.0.0.1\ net use x: \\fileserver\ But neither works, I'm getting the system error 53 (also tried both without the backslash at the end, and also with forward slashes instead of backslahses). A shared folder within there may indeed not always exist, that's why I want to map the "root" of that machine (containing all its shared folders), rather than one specific shared folder (such as the 'porn' dir in my example). [Reply or follow-up to this message] re: Can map folder in share, can NOT map the share itself :( Sunday, March 22, 2009 at 8:19 am Posted by Banana (31 messages posted) Well, when I do that, it works fine. The thing is, I don't want to map a specific shared folder (in my example the "porn" share on the \\10.0.0.1 machine), but the "root" of that machine, i.e. the (virtual?) drive or folder containing all its shares. Just as what I'm getting when I explore to \\10.0.0.1\ To clarify: when choosing Tools > Map Network Drive, I can map \\10.0.0.1\somefolder just fine. But I want to map \\10.0.0.1\ and not \\10.0.0.1\SomeSpecificFolder. [Reply or follow-up to this message] re: Can map folder in share, can NOT map the share itself :( Sunday, March 22, 2009 at 9:56 am Posted by geek9pm (286 messages posted) Some general rules. Do not share a root. Share only folders. ** You can only map a folder that is shared. Sub-folders of a a Share are available. Do not Web share, unless that is what you want. Avoid using the IP of a server, use its name. Use short names for Sabre folders and sub-folders. You can only map one share to a drive letter. If you want to map 13 shares, you use 13 letters. ** Yes, it is possible, and is often done, but it should only be available to the top administrator of the whole system. He needs it to do maintenance on the machines in his network. Security issue. Geek9pm [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows XP Discussion Forum