Windows Cannot Access a ZimaOS Shared Folder: Map It with Zima Client

The useful clue in this thread is that Windows could reach the ZimaOS host but not the named share. That separates basic IP connectivity from SMB discovery, authentication, and share mapping.

The Community Fix Was Zima Client Mapping

Zima support suggested using Zima Client to connect and map the shared folder, and the original poster confirmed that this solved the problem. The current Zima Client overview explains how Zima Client discovers the server and maps SMB access, while Zima device connectivity provides the broader current device-connectivity path.

Why an IP Address Can Work While a Share Name Fails

Opening the server address and opening a specific SMB service are different operations. Samba's Samba smbclient reference uses a service path of the form //server/share, which is useful for testing whether the share is actually being advertised and whether credentials work.

Check Windows Authentication Separately

Microsoft's Microsoft SMB guest policy documents current Windows restrictions around insecure SMB guest authentication. If ZimaOS is configured for member credentials, use those credentials rather than assuming anonymous guest access will be accepted.

The authenticated SMB access gives a current authenticated-share example, and the NAS file sharing basics explains how ZimaOS members and share permissions fit together.

A Practical Diagnostic Order

1. Confirm the ZimaOS dashboard or host IP is reachable.
2. Confirm the folder is actually shared in ZimaOS.
3. Use the intended ZimaOS member credentials.
4. Map the share through Zima Client when Windows discovery is unreliable.
5. Only then troubleshoot Windows SMB policy, cached credentials, firewall, or name resolution.

Bottom Line

In this case the network was not completely broken: the host was reachable, but the named SMB share was not being accessed correctly from Windows. Mapping it through Zima Client solved the problem. For similar cases, separate host reachability, share existence, authentication, and Windows discovery instead of reinstalling ZimaOS first.