On 1/17/25 5:33 AM, Paul Smith wrote:
Dear Fedora Users,
I’m encountering an issue where I cannot access a Samba shared folder from a Windows 10 guest running on a host configured with virt-manager
- QEMU/KVM. Here are the details of the situation:
--> Host Configuration and Status
The Samba shared folder is accessible from the host itself:
$ smbclient //192.168.122.1/intercambio -U x Password for [SAMBA\x]: Try "help" to get a list of possible commands. smb: > ls . D 0 Mon May 31 22:30:19 2021 .. D 0 Mon May 31 22:30:19 2021
This confirms that Samba is running and the share is functional locally.
SELinux is set to permissive mode using:
sudo setenforce 0
However, the problem persists.
The host firewall has the Samba service and port 445 explicitly allowed:
sudo firewall-cmd --add-service=samba --permanent sudo firewall-cmd --reload
--> Guest Configuration and Symptoms
The guest Windows 10 machine can successfully ping the host:
ping 192.168.122.1
However, attempts to connect to the shared folder fail. For example:
Test-NetConnection -ComputerName 192.168.122.1 -Port 445
Output:
WARNING: TCP connect to (192.168.122.1 : 445) failed
ComputerName : 192.168.122.1 RemoteAddress : 192.168.122.1 RemotePort : 445 InterfaceAlias : Ethernet Instance 0 SourceAddress : 192.168.122.155 PingSucceeded : True PingReplyDetails (RTT) : 0 ms TcpTestSucceeded : False
Disabling the Windows Firewall on the guest did not resolve the issue.
--> What I've Tried So Far
Verified Samba functionality locally on the host (smbclient works). Set SELinux to permissive mode (setenforce 0). Ensured the host’s firewall allows Samba traffic. Tested guest-host connectivity (successful ping but failed Test-NetConnection to port 445).
--> Additional Information
Host: Fedora Guest: Windows 10 Virtualization: virt-manager + QEMU/KVM Virtual network: NAT (default virbr0, host IP 192.168.122.1)
--> Request for Assistance
What could be causing the failure to access the Samba shared folder from the Windows guest? Are there specific configurations or troubleshooting steps I should try in this setup?
Any guidance would be greatly appreciated.
Thank you!
Paul
Hi Paul,
Your troubleshoot is very thorough. I kept scratching my head trying to figure out was was going wrong, then I remembered. Public/private networking on Windows.
M$ has a bizarre way of stating such:
Private: a hazardous environment with lots of potential bad guys on the same network. You are a network island and can see no network resources except your Internet router
Public: you trust everyone on the network.
It is intuitively backwards. Almost every customer I have come across gets it backwards.
The easiest way I know to figure it out is to <win><R> cmd arp -a
If the only computer that show up is you, then you are a network island (private network).
Since every version of Windows is like someone broke into your house and rearranged your furniture, I like to switch to a public network with:
W-Nein: Public / Private network switch from the Registry:
In the registry, first identiry the {xxxx} from [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles\
Then switch "catagory" to the type of network you want. For example: if {xxxx} was {162BD447-E88F-4AC3-90B6-0E064CE044E0}
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles{xxxx}] "Category"=dword:00000000 ; 0 = Public ; 1 = Private
You can also look public/private up on the web.
Let us know,
HTH, -T