Tuesday, October 15, 2019

Semi-canonical list for errors 0x80070035 and 0x80004005 on Synology NAS

Unfortunately, network problems can have a hundred causes.  This is a consolidation of the solutions found here, here, here, here and here

I did not get them all, so if the list below fails, you may need to root through the threads yourself.  This will at least give you a head start.

Note:  These solutions are largely aimed at the situation where one (or more) network machines can browse the share properly, and one (or more) machines can't. 

These solutions do not cover Windows Server or Active Directory (AD) issues.


Error 0x80004005: Unspecified error

For this error, you can (usually) browse to the affected share via IP address (i.e. \\192.168.1.xx\share) but not by name (i.e. \\NAS\share).  It may or may not show up in Network.

This is (usually) a local DNS problem.  If you have other machines that work, your router / DNS server is OK, and there is something wrong with the DNS on the affected machine.

For this reason, I recommend you edit the hosts file first.  If that fixes it, and you only have one problem machine, you're done.


Error 0x80070035:  The network path was not found

With this, you usually can't see the NAS in "Network", or browse to it at all.

Possible solutions:

P:   NetBIOS service needed but not starting.

A:  Network and Sharing Center: 
-  Check network is "Private" (either Work or Home). 
-  Go to "Change Adapter Settings"
-  Right-click on network adapter, select "Properties"
-  Double-click "Internet Protocol Version 4 (TCP/IPv4)"
-  Click "Advanced" button
-  Click "WINS" tab
-  Change from "Default" to "Enable NetBIOS over TCP/IP"

Note:  It is best to ensure this is done on all of the network adapters - even if they are not currently being used.

---------------

P:  SMB 1.0 is needed but not available.

A:   Enable SMB 1.0 as follows:
-  Control Panel / Turn Windows Features  On and Off (or Win + R, "optionalfeatures")
-  Check one of these:
  -  SMB 1.0/CIFS File Sharing Support
  or
  -  SMB 1.0/CIFS File Sharing Support / SMB 1.0/CIFS Client

You can also try checking / unchecking "SMB 1.0/CIFS Server" and "SMB 1.0/CIFS Automatic Removal".

Note:  SMB 1.0 is insecure and has been depreciated, and is not needed for accessing most NAS devices.  This includes most Synology devices.

Tip:  If you can log in to the NAS by IP address, do so and check the NAS logs to see what protocol was used.  If the problem machine can reach the NAS using SMB2 or higher, you might not need to enable SMB 1.0 support.

 ---------------

P:  Synology NAS SMB service not enabled.

A:  In DSM, go to Control Panel / File Services / SMB/APF/NAS and check "Enable SMB service".

---------------

P:  Synology NAS not handling SMB correctly.

A: Disable SMB 1.0 on NAS.
-  In DSM, go to Control Panel / File Services / SMB/APF/NAS.
-  Click "Advanced Settings"
-  Reset Maximum SMB protocol to "SMB3".
-  Reset Minimum SMB protocol to "SMB2".
-  Click "Apply".

Note:  Setting Maximum above SMB2 does not seem to do the trick.  The best combo seems to be setting Minimum SMB above SMB 1.0 and disabling SMB 1.0 on the affected PC.

Tip:  If you can log in to the NAS by IP address, do so and check the NAS logs to see what protocol was used.  If the problem machine can reach the NAS using SMB2 or higher, and can log in via IP address with SMB 1.0 disabled, you do not need SMB 1.0 support on either the NAS or the PC.

---------------

P:  IPv6 not working.

A:  Network and Sharing Center: 

-  Go to "Change Adapter Settings"
-  Right-click on network adapter, select "Properties"
-  Uncheck "Internet Protocol Version 6 (TCP/IPv6)"

---------------

P:  "Client for Microsoft Networks" disabled or not installed.

A:  Network and Sharing Center: 
-  Go to "Change Adapter Settings"-  Right-click on network adapter, select "Properties"
-  Ensure "Client for Microsoft Networks" is present and checked (enabled)

If not present, click "Install", then "Client for Microsoft Networks".

Note:  It is best to ensure this is present and enabled on all of the network adapters - even if they are not currently being used.
 
---------------

P:  "File and Printer Sharing for Microsoft Networks" disabled or not installed.

A:  Network and Sharing Center: 
-  Go to "Change Adapter Settings"-  Right-click on network adapter, select "Properties"
-  Ensure "File and Printer Sharing for Microsoft Networks" is present and checked (enabled)

If not present, click "Install", then "File and Printer Sharing for Microsoft Networks".

Note:  It is best to ensure this is present and enabled on all of the network adapters - even if they are not currently being used. 

 ---------------

P:  Out of date network drivers.

A:   Device Manager / Network Adapters / Update driver

---------------

P:  Network adapter driver corrupt.

A:  As follows:
 -  Network and Sharing Center \ Change Advanced Sharing Settings, turn everything to OFF on all profiles and options.  Save changes and close.
-  Device Manager \ Network Adapters \ Uninstall Ethernet and Wireless adapters
-  Scan for Hardware Changes to reinstall these devices and close Device Manger.
-  Network and Sharing Center \ Change Advanced Sharing Settings \ Turn everything to ON for all profiles and options - Save changes and close.


---------------

P:  Microsoft Virtual WiFi Miniport Adapter not set for proper NetBIOS operation.

A:  Network and Sharing Center: 

-  Go to "Change Adapter Settings"
-  Right-click on Microsoft Virtual WiFi Miniport Adapter, select "Properties"
-  Double-click "Internet Protocol Version 4 (TCP/IPv4)"
-  Click "Advanced" button
-  Click "WINS" tab
-  Change from "Default" to "Enable NetBIOS over TCP/IP".

 Note:  It is best to ensure this is done on all of the network adapters - even if they are not currently being used. 

---------------

P:  Windows Firewall is blocking NAS.

A:  Temporarily disable Windows Firewall.  If this works, you'll have to figure out how to permanently fix it.

---------------

P:  Bad login credentials stored in Credential Manager.

A:  Navigate to Credential Manager in Control Panel, or run keymgr.dll.
-  Go to Windows Credentials.
-  Remove stored credentials for affected NAS.

Note:  The NAS credentials might be incorrectly stored in "Generic credentials".

---------------

P:  Windows using outdated login information.

A:  Map NAS to a drive letter:
-  Right-click "My Computer" (or "Computer")
-  Map network drive
-  Enter NAS share using IP address
-  Check "Log in with different credentials"
-  Open mapped drive letter

This will hopefully force Windows to refresh outdated cached login information for the NAS.

---------------

P:  Bad / incorrect "Microsoft 6to4 adapter" or "6to4 adapter" drivers

A:  Device Manager / Network adapters:  Remove all "6to4" adapters.

---------------

P:  Necessary services not running.

A:  Using "services.msc", check that the following services are running:
-  Server
-  TCP/IP NetBIOS Helper
-  Workstation


---------------

P:  Network provider order wrong / Network provider registry key corrupt

A:  Check the following keys:
HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\HWOrder\Provider orderHKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order\Provider order

Should be set to one of the following:
   RDPNP,LanmanWorkstation
  or
  RDPNP,LanmanWorkstation, webclient

Also check:
HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder\Provider order
  and ensure RDPNP has a number lower than Lanmanworkstation


Also check: 
-  Control Panel \ Network and Sharing Center \ Change adaper settings
-  Tap Alt key to unhide menu bar
-  Click "Advanced \ Advanced Settings" in menu bar
-  Tab "Provider Order"
-  Ensure  the order is:
  -  Microsoft Remote Desktop Session Host Server
  - Microsoft Windows Network
  - Web Client Network (optional, may be missing)



---------------

P:  NAS is using Guest account access.

A:  In Registry Editor (regedit):

-  HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\
-  AllowInsecureGuestAuth = 1
-  RequireSecuritySignature = 0

Note:  It is not recommended that the NAS allow insecure Guest account access.

---------------

P:  Time sync issue is preventing NAS and PC from talking.

A:  Set clock on PC.
-   On NAS:  Control Panel \ Regional Options
-  Check "Synchronize with NTP server", server to time.google.com
-  Click "Update Now".

---------------

P:  Corrupt registry keys.

A:  In Registry Editor (regedit.exe):

-  Navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
-  For a 64-bit system, create a QWORD called LocalAccountTokenFilterPolicy
-  For a 32-bit system, create a DWORD called LocalAccountTokenFilterPolicy
-  Set  LocalAccountTokenFilterPolicy to 1.


---------------

P:  Jumbo frames not working.

A:  Network and Sharing Center:
-  Click Change adapter settings.
-  Right-click adapter, select Properties.
-  Networking tab
-  Click "Configure" button
-  Advanced tab
-  Select Jumbo Frame and disable


---------------

P:  NAS name not resolving to IP address.

A:  Edit the hosts file to link the NAS name and IP address manually.

---------------

P:  Security policy options incorrect.

A:  Using GPEdit.msc or secpol.msc:

-  Local Computer Policy -> Windows Settings -> Security Settings -> Local Policies -> Security Options

    Microsoft Network Client:
        Digitally sign communications (always)    DISABLED
        Digitally sign communications (if server agrees) DISABLED

    Microsoft Network Sesrver:
        Digitally sign communications (always)    DISABLED
        Digitally sign communications (if client agrees) DISABLED

Note:  gpedit.msc and secpol.msc do not exist in Windows 10 Home Edition by design.

---------------

P:  Bad files / settings in Sync Center.

A:  Start the "Sync Center".
-  Click on Manage Offline Files
-  Click View your offline files
-  Under computers, select the server and hit delete to remove it.

Note: If you've never messed with Sync Center, it is likely that there will be no offline file settings to delete / modify.

---------------

P:  HomeGroup not managing connections correctly.

A:  In Network and Sharing Center \ Change Advanced Sharing Settings\HomeGroup connections, turn off "Allow Windows to manage homegroup connections (recommended)".

Note:  If you're not using a Homegroup type network, Homegroup settings will not be shown, and this is not your problem.

---------------

P:  Two computers with the same hostname.

A:  Event Viewer
-  System logs
-  Search for Event ID 4321. It will tell you another computer with IP address x.x.x.x does not allow you to use the same hostname.

If there is no such event logged, this is not your problem.

---------------

P:   Client for Microsoft Networks corrupt.

A:  Uninstall Client for Microsoft Networks, reboot, reinstall, and reboot.

Note:  Windows 10 prevents this from being done via the GUI, and this could mess up your system worse than it already is.  For this reason I have not done it and I don't know the correct process, you'll have to find it yourself.

---------------

P:   File and Printer Sharing for Microsoft Networks corrupt.

A:  Uninstall File and Printer Sharing for Microsoft Networks, reboot, reinstall, and reboot.

Note:  Windows 10 prevents this from being done via the GUI, and this could mess up your system worse than it already is.  For this reason I have not done it and I don't know the correct process, you'll have to find it yourself.




No comments:

Post a Comment