Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm running into a curious issue. As part of a deployment routine, I'm mounting the c$ share of a remote server and copying files to that share, then disconnecting it with net use <drive> /delete. However, I'm encountering strange behavior:

C:\Users\user>net use T: /delete
System error 2 has occurred.

The system cannot find the file specified.

Okay, well I'll just use Windows itself to disconnect the file. Computer shows:

enter image description here

Well that's odd...let's just right-click -> Disconn...oh...

enter image description here

Since this isn't a persistent mount, it'll be gone on a reboot. However, I'd like to know why this happens. On a related note, all my network drives have the red "X" but I can get into all of them just fine. I don't hear problems from other users on the network, so it's puzzling.

Oh, to add to the puzzle:

C:\Users\user>net use
System error 2 has occurred.

The system cannot find the file specified.

Any idea what's going on? This is Windows 7 Pro x64, all updates applied.

share|improve this question
    
Are the drives mapped w/ the same account running net use /delete ?? –  BigHomie May 1 at 16:52
    
@BigHomie Yes, they are. –  Nathan C May 1 at 16:52
    
Can you delete them after you go into the drive (and thus, after the red X goes away) and exit back out? –  BigHomie May 1 at 16:53
2  
@BigHomie Well...yes, don't see how that relates though. –  Nathan C May 1 at 16:55
1  
..As part of a deployment routine, I'm mounting the c$ share of a remote server and copying files to that share.. Can you provide more detail as to how/when these drives are mapped, and also has this always been a problem, or is this a new problem, or new deployment routine (new routine meaning there's really no baseline of this ever working in the past) –  BigHomie May 1 at 17:21

1 Answer 1

up vote 2 down vote accepted
+100

Some Googling reveals someone else that had this issue. The problem was down to an issue with a registry key. Their issue was on Windows Server 2008, but the same principle for Windows 7.

Open Regedit, and navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order

Find the string called "ProviderOrder", the value should be a string with multiple values separated by commas (for example mine is: "RDPNP,LanmanWorkstation,webclient,BCMLogon"), ensure "LanmanWorkstation" is one of the values.

Credit / source: http://panerarichang.blogspot.co.uk/2011/07/win2k8error-code-0x80070002-system.html

Update: I was able to recreate the issue you faced by removing "LanmanWorkstation".

share|improve this answer
    
Mine is nfs41_driver,RDPNP,LanmanWorkstation,webclientc, so that doesn't appear to be the issue. It does give me a few other ideas as I have the NFS client installed as well as ExpanDrive to access my nagios box... –  Nathan C Jun 23 at 15:31
    
Just for testing, what happens if you change it to the same as mine? "RDPNP,LanmanWorkstation,webclient,BCMLogon". Since this is an order of priority, something else might be trying to handle it. –  Joey Jun 23 at 15:33
    
Try uninstalling those softwares and see what effect that has... –  Big Chris Jun 23 at 15:33
1  
Thank you. the nfs41_driver was the problem. After changing the order it works properly. –  Nathan C Jun 23 at 15:50
    
Glad I could help. Thanks. –  Joey Jun 24 at 9:17

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.