As we start to play with Windows 8 in our environment; we run into many new things. One such issue was trying to mount a network drive from a Netapp Filer.
We issued the command and received the following error:
System error 2148073478 has occurred.
A quick check at Microsoft showed this was due to Windows 8 and Server 2012 now using “secure negotiate” in their use of SMBv3. This requires servers using SMBv2 (which the filer in question uses) to use a signed response for all error messages which some filers don’t use and it causes the connection to fail.
The suggested resolution was to get the third party vendor to provide an update which in this case was not possible as it’s a “Release Candidate” at this time. This is not always the best thing to run in a production environment. Especially, for only a couple clients that are being used to test the new operating system versus having a genuine need.
The other option was to perform a registry edit via PowerShell to disable the “secure negotiate” on Windows 8.
I opened the PowerShell window and pasted:
Set-ItemProperty -Path “HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters” RequireSecureNegotiate -Value 0 -Force
But, it didn’t work. I received this nice little message:
> Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Serv
ces\LanmanWorkstation\Parameters" RequireSecureNegotiate -Value 0 -Force
Set-ItemProperty : Requested registry access is not allowed.
At line:1 char:1
+ Set-ItemProperty -Path
"HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstatio ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
+ CategoryInfo : PermissionDenied: (HKEY_LOCAL_MACH...tion\Parame
ters:String) [Set-ItemProperty], SecurityException
+ FullyQualifiedErrorId : System.Security.SecurityException,Microsoft.Powe
rShell.Commands.SetItemPropertyCommand
One of the things to remember is Microsoft is trying to be more secure with such things. Being a local administrator isn’t what is used to be.
The way around this was to right-click the tile for powershell (I have the administrative tools displayed on the desktop). This made a check appear on the tile and a menu appear at the bottom of the screen. On that menu was the option to “run as administrator”
I clicked the option and was able to run the command.
After that; I was able to mount shares from the filer.
techdork 