Error 0x80004005 accessing CIFS from Windows server

Issue: Accessing shares hosted on third party file server (like NetApp or EMC) from Windows server 2012 returns error

Windows cannot access \\ServerName

Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.

Error code: 0x80004005
Unspecified error

Cause:

With Windows server 2012 and Windows 8, Secure dialect negotiation is introduced in SMB 3.0. This feature depends upon the correct signing of error responses by all SMBv2 servers, including servers that support only protocol versions 2.0 and 2.1. Some third-party file servers do not return a signed error response. Therefore, the connection fails.

Resolution:

On the Netapp filer:

Disable SMB2 on the storage server by entering the following command: options cifs.smb2.client.enable off

options cifs.smb2.signing.required on

http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=474548

On the server:

Run the Powershell command:

Set-ItemProperty -Path “HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters” RequireSecureNegotiate -Value 0 –Force

or

Set-SmbClientConfiguration – RequireSecureNegotiate 0

Disable Virtual Machine Swap File .vswp

For each powered-on virtual machine, a .vswp file is placed in the virtual machines directory on the datastore. This file is required by VMkernel to swap virtual machine memory to the disk in case of excessive overprovisioning. The swap file size can be calculated with the formula (.vswp File = Allocated Memory – Memory Reservation). As per default, the reservation is set to 0, so the .vswp file size is equal to the amount of virtual memory.

Virtual Machine with no Memory Reservation

Having the whole amount of memory from all virtual machines occupying the datastore wastes a lot of capacity. To get rid of the .vswp space, you have to reserve parts or all guest memory. If your virtual machine has 16GB and you reserve 50%, your .vswp file is only 8GB. If you reserve 100%, the file is still there but with a size of 0 bytes. The file will never disappear completely.

Please note that the swap file can only grow while the virtual machine is running. If you want to shrink the file (by increasing memory reservation) you have to power cycle the virtual machine.

Virtual Machine with full Memory Reservation – Reserve all guest memory (All locked)

Since vSphere 5.0, there is also a second vmx .vswp file whose size is about 50-150MB. This is the swap file for overhead memory reserved for the VMX process. You cannot remove that file.

Disable Virtual Machine Swap File (.vswp) | Virten.net.