issues with windows and my local network

Question

i purchased a WD Mycloud Home NAS. The set up for the machine went well except when i clicked the it would not open Several months have gone past and i have taken guidance from many sources. WD NORD my VPN provider mY firewall company and others as advised to do so. In the end all have concluded the problem lies with windows. I can access the mycloud via the IP address it can be clearly seen on the router. However even if i try to permanently map it to the drive it still fails I need help form somebody who knows great deal more about this than i do. Please rest assured all steps have been taken to ensure the system should not be experiencing these issues. Vic Chaffey

Answer 1

Hello Vic Chaffey, thank you for posting in the Microsoft Q&A community.

This behavior typically occurs due to security policies in modern releases of Windows. Windows default security baselines disable unauthenticated guest logons over SMB2 and SMB3, which many consumer NAS appliances rely on for initial share access [1]. Additionally, if your active network profile is categorized as Public, Windows Defender Firewall automatically blocks local file-sharing traffic and NetBIOS name resolution. VPN software like NordVPN can also intercept local subnet traffic if local network discovery settings or split tunneling features are turned off [1].

To resolve this issue, you can start with standard network configuration adjustments followed by an explicit CLI drive mapping workaround.

First, verify that your active network connection is categorized as private. Navigate to Settings > Network & internet > Ethernet (or Wi-Fi), select your connected network, and set the Network profile type to Private network. This opens the necessary firewall ports for local SMB file sharing.

Next, enable SMB guest access in Windows. Many WD NAS appliances require guest authentication for local file access [1]. You can allow guest logons by running the following command in Command Prompt as an Administrator:

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

Note: This setting allows unauthenticated SMB guest access on your local network [1]. Ensure your local network environment is secure before applying this change.

If File Explorer's graphical interface continues to fail when mapping the drive, map the share directly via Command Prompt using its IP address:

net use Z: \\<NAS_IP_Address>\<ShareName> /persistent:yes

Replace <NAS_IP_Address> with your NAS IP address and <ShareName> with the target share folder name on the device. To ensure Windows retains these credentials across system restarts, open Control Panel > Credential Manager > Windows Credentials, click Add a Windows credential, and enter the NAS IP address alongside your NAS user credentials.

If you are using VPN, check the application settings to verify that Invisibility on LAN is disabled. When enabled, this feature prevents your computer from communicating with other local devices on your network range (such as 192.168.x.x).

For official documentation on SMB and network drive troubleshooting, refer to:

• Guest access in SMB2 and SMB3 is disabled by default in Windows
• Troubleshoot SMB file sharing visibility issues in Windows
• Mapped network drive may fail to reconnect in Windows

Answer 2

Try this in order:

1. Confirm the share can be reached directly.
   • Open File Explorer.
   • In the address bar, enter the NAS by IP address, for example \\192.168.1.50.
   • If that opens, the device is reachable and the issue is with discovery or how Windows is reconnecting the mapped drive.
2. Map the drive manually in File Explorer.
   • Open File Explorer > This PC.
   • Select Map network drive.
   • Choose a drive letter.
   • In Folder, enter the share path.
   • Select Reconnect at sign-in.
   • Select Finish.
   • If Windows still cannot reconnect later, that matches a known mapped-drive reconnect issue.
3. If the drive maps but shows disconnected after sign-in, use a scheduled task workaround.
   • Open Task Scheduler.
   • Select Action > Create Task.
   • On General, give it a name such as Map Network Drives.
   • Select Change User or Group, choose a local user or group such as LocalComputer\Users, then select OK.
   • On Triggers, select New > At log on.
   • On Actions, select New > Start a program.
   • In Program/script, enter Powershell.exe.
   • In Add arguments (optional), enter -windowstyle hidden -command .\MapDrives.ps1 >> %TEMP%\StartupLog.txt 2>&1.
   • In Start in (optional), enter %SystemDrive%\Scripts\.
   • On Conditions, select Start only if the following network connection is available and choose Any connection.
   • Sign out and sign back in.
4. Check whether a firewall is blocking file sharing.
   • SMB file sharing uses UDP/TCP ports 135 through 139 and TCP/UDP 445.
   • If a firewall is configured to block these, browsing and file sharing can fail.
   • Do not open these ports to the Internet. That is a security risk.
5. If this is a mapped web share rather than standard SMB, check for the specific WebDAV authentication issue.
   • A mapped web share can fail after restart with: "The operation being requested was not performed because the user has not been authenticated".
   • In that case, the documented fix involves configuring the WebClient URL list and then restarting the WebClient service.
   • Warning: this requires a registry change, and incorrect registry edits can cause system problems.
6. If the share still does not open, verify basic Windows sharing access.
   • The target device may be off, or the account being used may not have the correct permissions.

The most likely paths from the documented Windows behavior are:

• direct access by IP works, but mapped-drive reconnect fails after sign-in
• firewall rules are interfering with SMB traffic
• the device is being treated as a web share and hitting the WebClient authentication issue

---

• File sharing over a network in Windows
• Mapped network drive may fail to reconnect in Windows 10, version 1809
• Internet firewalls can prevent browsing and file sharing
• Error when you try to access a network drive that's mapped to a web share: User has not been authenticated
• Error when you try to access a network drive that's mapped to a web share: User has not been authenticated