To fix network share issues, verify network connectivity, ensure both devices are on the same network, check sharing permissions, confirm firewall settings allow file sharing, and restart affected systems. Also, update network drivers and verify correct credentials are being used to access shared resources.
How to fix network share issues ?
Windows cannot access my \WDMYCLOUDMIRROR network device and map as a drive.
Error code : 0x80070035 (the network path was not found
However, I can access it via Mycloud website but it os way too long to transfer files.
What should I do to solve the problem ?
Windows for home | Other | Internet and connectivity
3 answers
Sort by: Most helpful
-
AI answer
2026-06-18T17:22:46.07+00:00 Follow these steps in order and test access to
\\WDMYCLOUDMIRRORafter each major step.- Verify the device and network
- Make sure the WD My Cloud Mirror is powered on and connected to the same router/network as the Windows PC.
- Confirm the PC is on the same network (same router/Wi‑Fi SSID) and that internet and local network access work.
- Try accessing by IP address
- In File Explorer, enter
\\<device-IP>(for example,\\192.168.1.50) in the address bar instead of\\WDMYCLOUDMIRROR. - If this works but the name does not, the issue is name resolution rather than connectivity.
- In File Explorer, enter
- Turn on network discovery and file sharing (Windows 11/10)
- Open Settings → in the Find a setting box type manage advanced sharing settings → select Manage advanced sharing settings.
- Under Private networks, turn on Network discovery and File and printer sharing.
- Under All Networks, temporarily turn off Password protected sharing to test.
- Ensure the network is set to Private
- In Settings, go to Network & Internet → select the active connection (Wi‑Fi or Ethernet).
- Make sure the network profile is set to Private.
- Start required sharing services
- Press Windows key + R, type
services.msc, press Enter. - For each of these services, right‑click → Properties → set Startup type to Automatic and start them if stopped:
- Function Discovery Provider Host
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
- Press Windows key + R, type
- Check SMB/guest access policies (if share uses guest/anonymous access)
- If the NAS is configured for guest (no‑password) access and Windows shows messages about guest access being blocked, enable insecure guest logons:
- Registry method (Home editions):
- Open Registry Editor (
regedit). - Go to
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation(create the key if it does not exist). - Create a DWORD (32‑bit) Value named
AllowInsecureGuestAuthand set Value data to1.
- Open Registry Editor (
- Or Local Group Policy (Pro/Enterprise):
- Run
gpedit.msc. - Go to Computer Configuration → Administrative Templates → Network → Lanman Workstation.
- Open Enable insecure guest logons, set to Enabled.
- Run
- Registry method (Home editions):
- Restart the PC and try
\\WDMYCLOUDMIRRORagain.
- If the NAS is configured for guest (no‑password) access and Windows shows messages about guest access being blocked, enable insecure guest logons:
- Check SMB protocol and security negotiation
- Some NAS devices use older SMB/security settings that newer Windows builds reject.
- Open Windows PowerShell (Admin) and run:
Set-SmbClientConfiguration -RequireSecuritySignature $false Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" RequireSecureNegotiate -Value 0 -Force - Restart the PC and test access.
- If still failing with 0x80070035
- Try again by IP (
\\<device-IP>). - If IP also fails, temporarily disable third‑party firewall/antivirus and test.
- If IP works but name does not, add a static entry for
WDMYCLOUDMIRRORin your router’s DNS or the Windowshostsfile (advanced) so the name resolves correctly.
- Try again by IP (
If the device is reachable by IP and the above Windows settings are applied,
0x80070035(network path not found) should be resolved in most home‑network scenarios.
References:
AI-generated content may be incorrect. Read our transparency notes for more information. - Verify the device and network
-
Hendrix-V 16,080 Reputation points Microsoft External Staff Moderator
2026-06-19T04:15:18.5133333+00:00 Hi Louis Caille,
Thank you for posting your question.
Network share issues can occur for a variety of reasons, including changes to network discovery, file sharing settings, stored credentials, or authentication policies after a Windows update. Based on the information provided, it would be helpful to first identify the exact error message you're receiving, as this can significantly narrow down the cause.
In the meantime, I recommend checking the following:
- Verify that both devices are connected to the same network and that the network profile is set to Private.
- Ensure Network Discovery and File and Printer Sharing are enabled on the devices involved.
- Remove any outdated entries for the shared device from Credential Manager and reconnect to the share.
- Try accessing the share using both the server's name (\ServerName\Share) and its IP address to determine whether the issue is related to name resolution.
- If the share previously allowed access without credentials, review any recent changes to sharing permissions or authentication settings.
I hope this helps point you in the right direction. Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.