ns map a share indigenous another an equipment using mine user account.I launch one elevated command prompt (cmd.exe, best click, run as administrator).Navigating to common drive (Z:) outcomes in:The system cannot discover the journey specified

Now if I open a non elevated command prompt, I have the right to navigate to Z: simply fine.

You are watching: The system cannot find the drive specified



Opening a Windows explorer as administrator and recreating the network shares didn"t work for me. Then, I uncovered this solution: produce the re-superstructure on the command note itself. It operated for me.

net use f: \\remoteserver\subfolder also if the journey is already mapped in windows explorer, still the worked.

Note: only use a solitary backslash prior to subfolder



Probably that is no a problem of record permissions but it"s related with:

Network share being linked with sessions (i.e. Different users may have actually a different set of network shares). Keep in mind that one user can have more that one session.How User Account manage works.

Since practically all users supplied an administrator account in XP (as most programmers didn"t stroked nerves to make their programs job-related with minimal accounts), Microsoft do a "limited version" of administrator accounts beginning with Vista, an in some situations the two "versions" counts as various users (since they are different sessions).

Try launching an elevated Windows traveler (i.e. A Windows traveler launched v "Run together administrator") and also recreate every network shares, that should do the trick.

See more: Download Windows 7 All In One Activated Iso Kickass + Compressed

The reason for having to recreate the share is defined on this MSDN blog entry:

Mapped Network Drives through UAC on windows Vista

Edit: pertinent bits from the blog entry (emphasis mine):

To leveling things, let"s assume you are running together an administrator through UAC allowed (although, come be much more secure, the is far better to run as a traditional user). Once you log in in, you create a new token. Us then detect that you have actually UAC enabled, us log in a 2nd time, and also end up through a new (highly restricted) token, i beg your pardon we use to start the shell. There space two separate login events.(...)This convenience function makes it less complicated to operation into concerns with mapped network drives. Before Windows 2000 SP2, machine names remained internationally visible until explicitly removed or the device restarted. For security reasons, us modified this behavior start with windows 2000 SP2. Indigenous this allude forward, all tools are connected with one authentication i would (LUID) - one ID produced for each logon session.(...)Because these mapped drives are connected with LUID, and because elevated applications room using a various LUID generated throughout a separate login event, the elevated application will no longer see any mapped drives for this user.