Samba shares at Win 10 VM

English Virtualization
1

I have a tumbleweed host with Samba and a qemu/kvm Win10 VM
The VM is working with a Debian Buster host without any problems. so I do not want to fix the VM …

If I am clicking at th VM at the Tumbleweed Host:

net use x: \ip-SamaServer\sambaShare /user:Samba-user pw
Systemerror 53
network path not found

Firewall off:
net use x: \ip-SamaServer\sambaShare /user:Samba-user pw -> OK
but Internet access denied completely

Firewall on:
Internet access again allowed
all other shares OK like:
net use Y: \ip-SamaServer\sambaShare2 /user:Samba-user pw -> OK

The zone is shown at the yast samba page as exterenal
If I set the external firewal zone to allow all and set all ports as open, it is still not working (independend whether it makes any sense … )

Any hint what windows is asking for the first time, when connecting Samba shares? if possible with settings via konsole.

2

The Tumblweed host has the ip 192.168.1.100

​The Win10 VM has the ip 192.168.122.100​
​With firewall wireshark is reporting there are ​


19 7.397312792 192.168.122.100 192.168.122.255 NBNS 92 Name query NB Host-LINUX<20>

and no connections to the Samba afterwards
​
​without firewall Wireshark is reporting

 
19 7.397312792 192.168.122.100 192.168.122.255 NBNS 92 Name query NB Host-LINUX<20>
20    7.674809902    192.168.122.100    192.168.122.1    TCP    66    49908 → 445 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM=1
22    7.675347382    192.168.122.100    192.168.122.1    TCP    54    49908 → 445 [ACK] Seq=1 Ack=1 Win=2102272 Len=0
26    5.277677    192.168.122.100    192.168.122.1    SMB    213    Negotiate Protocol Request
27    5.278974    192.168.122.1    192.168.122.100    TCP    60    445 → 49937 [ACK] Seq=1 Ack=160 Win=64128 Len=0
28    5.311548    192.168.122.1    192.168.122.100    SMB2    260    Negotiate Protocol Response
3

A bit more info would be useful. Which VM system are you using … QEMU or VirtualBox or something else? Also how have you set the networking up … bridged or NATed etc?

4

If your machines are using the default subnet mask 255.255.255.0 (or /24),
Your machines are on different networks and probably won’t see each other.
Solution 1
Change the 3rd octet number of one of your machines so it’s the same as all other machines on your netowrk.
Solution 2
Change the subnet mask to 255.255.0.0 (or /16).

TSU

5

QEMU/KVM

networking bridged - The system is using network manager - so I am feeling a little blind especially i am not familiar with opensuse network configuration.
I am familiar with debian console network configuration and I do not find the configuration files at Tumbleweed

the configuration with virsh net-list --all

**<network>**
  **<name>**default**</name>**
  **<uuid>**a75cb599-c293-4b97-85cc-53018da98d9b**</uuid>**
  **<forward **mode='nat'**/>**
  **<bridge **name='virbr0'stp='on'delay='0'**/>**
  **<mac **address='52:54:00:59:4e:92'**/>**
  **<ip **address='192.168.122.1'netmask='255.255.255.0'**>**
    **<dhcp>**
      **<range **start='192.168.122.2'end='192.168.122.254'**/>**
      **<host **mac='52:54:00:3b:1d:8f'name='win10'ip='192.168.122.100'**/>**
      **<host **mac='52:54:00:b7:40:8b'name='Debian'ip='192.168.122.110'**/>**
    **</dhcp>**
  **</ip>**
**</network>**
6

A question about that:
If it is a network configuration problem, why does it work after switching the firewall off connect (click at) at least one share and switching firewall on again?

7

sorry …
virsh net-dumpxml default

8

Possibly caching.
Possibly initial recognition.

But,
Bottom line is that that if you don’t fix the submask problem, it will haunt you continuously… You won’t know when you’ll lose connectivity until you fix the problem.

If you want to learn some valid reasons for doing what you’re doing… Look up and read the topics of subnetting and supernetting… The first splits networks up, and the other allows your machine to have access to a larger network then you’d have by default while groups of machines retain their own network “groups.”

TSU

9

With Firewall on
I can ping from Win10 192.168.122.100 to the host 192.168.1.100
I can ping from Win10 192.168.122.100 to the gateway 192.168.122.1
I can ping from Win10 192.168.122.100 to another VM 192.168.122.130
I can ping to any internet iP

but with firewall off i can not ping to the internet.

so … where is there a basic subnet problem? Am I completely on the wrong way ?

In my opinion it would be helpful to check the system systematically.
But there I need help - without or with network manger off. The config files are different to Debian where I am familiar with - as i wrote before.

And with network manger shouldn’t it automatically working?