8

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.

  • Are the drives mapped w/ the same account running net use /delete ?? – MDMoore313 May 1 '14 at 16:52
  • @BigHomie Yes, they are. – Nathan C May 1 '14 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? – MDMoore313 May 1 '14 at 16:53
  • 2
    @BigHomie Well...yes, don't see how that relates though. – Nathan C May 1 '14 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) – MDMoore313 May 1 '14 at 17:21
9
+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".

| 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 '14 at 15:31
  • 2
    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 '14 at 15:33
  • Try uninstalling those softwares and see what effect that has... – Kinnectus Jun 23 '14 at 15:33
  • 3
    Thank you. the nfs41_driver was the problem. After changing the order it works properly. – Nathan C Jun 23 '14 at 15:50
4

I had the same problem but it was caused by a defective NFS4.1 driver installed by a Windows NFS client I had had used recently.

Inspired by other answers to this issue, I checked this Windows Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order

I had a string value named ProviderOrder containing this data: nfs41_driver,XwpNTrdr,RDPNP,LanmanWorkstation,webclient.

Unlike other users reported, LanmanWorkstation did appear; the problem was caused by nfs41_driver. Just remove it off the list and it will work again.

| improve this answer | |
  • 1
    Please clarify and add a little more context to this answer to convey what you are suggesting exactly. – Pimp Juice IT Sep 7 '17 at 0:05
  • I had this exact same issue. I knew it was down to trying out mounting NFS4.1 on windows 7 pro. Could only find this SuperUser post once i discovered 'net use' returned an error. NFS driver was the issue. – SimonAlfie Oct 8 '18 at 13:53
0

In my case it was hiding in the registry: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2]

When I deleted the corresponding key the drive disappeared for good.

source: unable to delete a network drive in windows 7

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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