Defender firewall could be a cause, but it is only one of several possible reasons why access to a WD Cloud (network) storage device might stop working.
To check whether firewall is the cause, verify that the network ports and protocols used by the device are not being blocked. Windows Defender Firewall controls inbound and outbound network traffic based on rules and profiles (Domain, Private, Public). If the WD Cloud is on the local network and the PC’s active network profile is set to a more restrictive type (for example, Public), firewall rules might block file-sharing protocols such as SMB.
If SMB-based access is used, blocking TCP port 445 (and, in some environments, legacy NetBIOS ports 137–139) on the local or perimeter firewall will prevent browsing or connecting to network shares. The guidance for securing SMB recommends blocking these ports at the perimeter and tightening them on endpoints, which can unintentionally affect access to network storage if rules are too strict.
Recommended checks:
- Confirm that the WD Cloud device is powered on and reachable on the network (for example, it appears in the router’s device list or responds to a basic connectivity test).
- In Windows Security → Firewall & network protection, confirm that file and printer sharing or SMB-related rules are allowed for the active network profile (typically Private for home networks).
- If a router or hardware firewall is in use, ensure it is not blocking SMB traffic on the local network. Perimeter firewalls should block SMB to/from the internet, but should not normally block SMB between devices inside the home network.
If SMB ports are blocked or file-sharing rules are disabled, re-enabling them for the trusted home network can restore access, while still keeping SMB blocked from the internet.
References: