If a ZimaOS VM can browse “Network” but cannot ping the ZimaOS host or open its SMB shares, start with VM routing and host reachability rather than Samba credentials. The December 2025 thread initially blamed NAT/isolation, but a later April 2026 reply reported that even the newer bridge path could still prevent a VM from pinging the ZimaOS host.
That later report matters: switching to “bridged” networking is a useful test, not a guaranteed fix for every ZVM version and network backend.
What the Original Thread Actually Proved
The VM initially lacked the Samba client stack. After installing it, the VM could see its own print$ share, which showed that Samba software inside the guest was working. The stronger clue was that ping ZIMAOS_IP returned host unreachable.
The VM could ping another LAN host, so the failure was specifically between the guest and its ZimaOS host rather than a total guest-network outage.
Test the ZimaOS Host by IP Before Network Browsing
Inside the VM, test ping ZIMAOS_IP and then open smb://ZIMAOS_IP or the equivalent Windows UNC path. Network discovery can fail even when direct SMB access works, so browsing icons are a poor first health check.
The current ZimaOS SMB help also recommends direct address and credential checks when SMB access is slow or fails.
Bridge Mode Can Still Have Host-Isolation Behavior
An early community reply said bridged mode would solve the problem. A later user reported that the newest update still had a bridge state where the VM could not ping the ZimaOS host. That means the original “just use bridge” conclusion is too strong.
If the VM reaches other LAN devices but not the ZimaOS host, compare the behavior with the ZimaOS network access guide and collect the VM network mode, guest IP, host IP, subnet, and route table before changing Samba again.
Do Not Use SMB Discovery as the Only Success Test
Minimal Linux guests may not run Avahi, WS-Discovery or other browsing services. That can hide shares from the graphical “Network” view while direct SMB by IP still succeeds.
Once ping works, test TCP 445 and authenticate directly. Only after that should you troubleshoot service discovery.
Bottom Line
The source thread narrowed the fault below Samba: the VM could not reach its ZimaOS host. Bridged networking is still a reasonable configuration to test, but the later report shows that host isolation may persist in some ZVM builds. Prove IP reachability first, then SMB, then discovery.
