Unable to Access Samba Shared Folder from Windows 10 Guest in virt-manager/QEMU Setup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux