as the last entries on the screen. Then leave that window untouched and run ls -lah /mnt/avoir in the other window. Then the first window should show additional lines as I showed above.
I change and i have something on the first screen :
master_do_mount: mounting /-
automount_path_to_fifo: fifo name /var/run/autofs.fifo–
lookup_nss_read_map: reading map file /etc/auto.smb.shares
do_init: parse(sun): init gathered global options: (null)
mounted direct on /mnt/avoir with timeout 15, freq 4 seconds
do_mount_autofs_direct: mounted trigger /mnt/avoir
st_ready: st_ready(): state = 0 path /-
handle_packet: type = 5
handle_packet_missing_direct: token 63, name /mnt/avoir, request pid 16837
attempting to mount entry /mnt/avoir
lookup_mount: lookup(file): looking up /mnt/avoir
lookup_mount: lookup(file): /mnt/avoir → -fstype=cifs,username=bibi2,password=zz,iocharset=utf8,uid=osmc,gid=osmc ://192.168.xx/avoir
parse_mount: parse(sun): expanded entry: -fstype=cifs,username=bibi2,password=zz,iocharset=utf8,uid=osmc,gid=osmc ://192.168.1xx/avoir
parse_mount: parse(sun): gathered options: fstype=cifs,username=bibi2,password=zz,iocharset=utf8,uid=osmc,gid=osmc
parse_mount: parse(sun): dequote(“://192.168.xx/avoir”) → ://192.168.xx/avoir
parse_mount: parse(sun): core of entry: options=fstype=cifs,username=bibi2,password=zz,iocharset=utf8,uid=osmc,gid=osmc, loc=://192.168.1xx/avoir
sun_mount: parse(sun): mounting root /mnt/avoir, mountpoint /mnt/avoir, what //192.168.xx0/avoir, fstype cifs, options username=bibi2,password=zz,iocharset=utf8,uid=osmc,gid=osmc
do_mount: //192.168.xx/avoir /mnt/avoir type cifs options username=bibi2,password=zz,iocharset=utf8,uid=osmc,gid=osmc using module generic
mount_mount: mount(generic): calling mkdir_path /mnt/avoir
mount(generic): calling mount -t cifs -o username=bibi2,password=xxx,iocharset=utf8,uid=osmc,gid=osmc //192.168.xx/avoir /mnt/avoir
mount error: Server abruptly closed the connection.
This can happen if the server does not support the SMB version you are trying to use.
The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
mount(generic): failed to mount //192.168.xxx/avoir (type cifs) on /mnt/avoir
dev_ioctl_send_fail: token = 63
failed to mount /mnt/avoir
I think we are back to square one that there is some kind of network issue as I doubt that it’s a SMB version issue unless you manually changed the SMB version on your Windows machine.
Maybe open a 3rd ssh session and have a ping 192.168.xxx running in parallel.
BTW there is no safety gain or whatsoever by hiding your private IP addresses. These are private and therefore it doesn’t make a difference if the world knows if you use 192.168.1.1 or 192.168.100.123
Strange !! the OMSC and my PC are only at 3 meters and only separate by a switch… The iperf you told me to do was correct…
The ping on a 3 ssh session have always 0.900 ms response (same when ssh1 and ssh 2 are running with a " sudo automount -f -v -d" on ssh 1 and a “ls -lah /mnt/avoir” on ssh 2…
osmc@osmcvero5:~$ osmc@osmcvero5:~$ smbclient -L 192.168.1.50 -U XXX
Enter WORKGROUP\XXX’s password:
Sharename Type Comment
--------- ---- -------
ADMIN$ Disk Administration à distance
AVOIR Disk
C$ Disk Partage par défaut
D$ Disk Partage par défaut
DevelopmentFiles Disk SMB Share For DevelopmentFiles path
E$ Disk Partage par défaut
F$ Disk Partage par défaut
IPC$ IPC IPC distant
print$ Disk Pilotes d’imprimantes
Starting Nmap 7.80 ( https://nmap.org ) at 2025-04-17 16:41 CEST
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.96 seconds
osmc@osmcvero5:~$
This is really confusing. Do you have a firewall running on the Windows machine that might be blocking?
Normally you should see something like
Host is up (0.0023s latency).
Not shown: 993 closed tcp ports (conn-refused)
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
2049/tcp open nfs
5357/tcp open wsdapi
Host script results:
| smb-protocols:
| dialects:
| 2:0:2
| 2:1:0
| 3:0:0
| 3:0:2
|_ 3:1:1
Nmap done: 1 IP address (1 host up) scanned in 0.34 seconds
Yesss! if i cut all the firewal (and the public one i have :
Starting Nmap 7.80 ( https://nmap.org ) at 2025-04-17 16:49 CEST
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.97 seconds
osmc@osmcvero5:~$ nmap --script smb-protocols 192.168.1.50
Starting Nmap 7.80 ( https://nmap.org ) at 2025-04-17 16:49 CEST
Nmap scan report for ordi-salon.home (192.168.1.50)
Host is up (0.69s latency).
Not shown: 994 closed ports
PORT STATE SERVICE
22/tcp open ssh
135/tcp open msrpc
139/tcp open netbios-ssn
445/tcp open microsoft-ds
1236/tcp open bvcontrol
5357/tcp open wsdapi
