I have no problem with using bridging, the issue I am running into is in gnome boxes there isn’t a networking option. I can create networks via virt-manager, but not sure how to put my VM into them.
I haven’t had the need to use Gnome Boxes; I’ve only used VirtualBox and KVM regularly. I did some quick Googling and found this post that looks relevant:
How to use bridged network on a Gnome Boxes VM
The important point is that the bridge is external to the VM. So the only difference inside the VM is that you are on an external IP address instead of a NAT one.
Is this Windoze 11 Pro or Home? Networking works differently between the 2. Home can only connect as a workgroup, Pro as an AD member or Workgroup. If it is Pro, you should make sure it’s networking is setup as Workgroup. Also make sure your samba config has the same workgroup name set as Windoze does.
I also don’t use gnome boxes, but if I’m now mistaken it is based on KVM/QEMU as well, so you can probably also set up bridging there somehow. I might just have to do some manual editing of some configuration file.
This was the exact post I was following. I have no problem with using bridging, the issue I am running into is in gnome boxes there isn’t a networking option. I can create networks via virt-manager, but not sure how to put my VM into them.
11 Pro, I’ll try the workgroup! Thanks
I wonder if this is just a formatting problem ?
I noticed that the OP was trying to connect a network folder using ‘\\resolve.lan\share’. Now the backslash is an escape character and under Linux it would have to be ‘\\\\resolve.lan\\share’ to work.
I suggest he tries it like this: //resolve.lan/share
Why did you enable this protocol?
Unless you enabled SMB 1.0 on Rocky in your smb.conf file it is disabled by default. Rocky, windows and most other distros only support SMB 2.x and SMB 3.x by default. But I don’t think this is your problem yet as I would think you would get a more samba specific error message.
I’m confused as to how your network is setup. Are all your machines and vm’s addresses hardcoded in the same ip subnet?
PS C:\Users\moksh> nslookup resolve
Server: UnKnown
Address: 192.168.122.1
Name: resolve
Address: 192.168.1.141
So 192.168.122 and 192.168.1 are different subnets and in my experience would not communicate between each other w/o some bonding which is beyond my understanding.
It is possible, if the CIDR is /16 (network mask 255.255.0.0).
Yup, I knew that too, but not at the moment when I hit reply. I wonder if the OP has actually set it up that way because the default is /24? Something is not working network wise here that has nothing to do with samba.
Just wondering if the OP solved the issue or not and if so what was the solution?
Not yet, I think boxes is actually the problem and I’ll need to use a different application for my VM.
From a wikipedia article on gnomeboxes I found this comment:
As of version 40, the remote connection functionality has been moved to the separate application, GNOME Connections.
So before you give up your investment in boxes take a look at the connections app.
1 Like
I pulled my hair out trying to get Samba working, Windows 10 and Windows11 to a Rocky 9 machine. This just would-not-work, until I changed one SELinux setting on the Rocky machine.
sudo setsebool -P samba_export_all_rw 1
I believe that I then restarted smb and I was immediately able to access the Samba share from Windows.
2 Likes