Velvet Star Monitor

Standout celebrity highlights with iconic style.

news

0x80004005 (Unspecified error) when accessing network share in Windows 7

Writer Matthew Harrington

I'm getting error 0x80004005 when trying to access a network share in Windows 7. The network share was created from a Windows 7 computer and is being accessed by a Windows 7 computer. The same exact configuration worked properly a month ago and for whatever reason doesn't work anymore.

I've tried

  • Creating HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\LocalAccountTokenFilterPolicy and setting the value to 1
  • Removing all 6to4 adapters in Device Manager
  • Disabling IPv6 and setting IPv4 to a static address on the same subnet mask as the other computer
  • Verifying the two computers are on the same workgroup
  • Disabling the firewall and antivirus
  • Updating Windows
  • Accessing the share using \\[IP_ADDRESS]\[SHARE] and \\[HOSTNAME]\[SHARE]
  • On the host computer (server) checking \\localhost for the share - the share does appear and I can access files
  • Enabling NetBIOS over TCP/IP

How can I access this network share? Any help would be appreciated!

3

3 Answers

I recently resolved this issue by enabling the following group policy permission:

Local Computer Policy>Computer Configuration>Administrative Templates>Network>Lanman Workstation>Enable insecure guest logons

Fixed by installing KB4487345.

I had this problem in Windows 10, trying to access an open share (without username).

To fix it, you need to enable "AllowInsecureGuestAuth" in the registry under
"HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters".

You can check what it is on your system with

reg query HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters /v AllowInsecureGuestAuth

And you can set it to enable "AllowInsecureGuestAuth" with

reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters /v AllowInsecureGuestAuth /t REG_DWORD /d 1

You need to do that in a Command Prompt or Powershell started as Admin (or "Run as Administrator")

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

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