Open first a command line with cmd
and the use net view
system error 53
network path didnt found
always a french translate…
system error 53
network path didnt found
Suggest we go back to OSMC to check what we get there.
Install smbclient via sudo apt-get install smbclient
and then run smbclient -L 192.168.1.13
@Carlito I think you need to use the network name of the Vero instead of the ip address in the explorer of Windows 10, but first let’s get some more information. Could you provide the output of the following
- Windows 10, open
cmd
windows:
ping 192.168.1.13
- Windows 10, open
cmd
windows:
nslookup 192.168.1.13
(if reverse DNS is working fine, you see the full qualified name your router has mapped to 192.168.1.13; from now, use this name)
Example:
C:\>nslookup 192.168.178.30
Server: fritz.box
Address: 192.168.178.1
Name: osmc-vero4k.fritz.box
Address: 192.168.178.30
- Windows 10, open
cmd
windows:
net view \\<the full qualified name of the Vero you got in point 2.>
(example: net view \\osmc-vero4k.fritz.box
)
- Windows 10, open
cmd
windows:
nbtstat -a 192.168.1.13
- Now, try to enter in the address field of your Windows
explorer
\\<the full qualified name you got in point 2.>
(example: \\osmc-vero4k.fritz.box
)
- if that doesn’t work, please, also provide the links (URLs !) from the following two commands if your logged into the Vero via SSH:
paste-log /etc/samba/smb.conf
sudo systemctl status -l samba|paste-log
Samba 4.5.12-Debian
i made a mistake typing net view in fact
this command finally works
Nom du partage Type Utilisé comme Commentaire
osmc Disque OSMC Home Directory
WD 320 IDE Disque Auto-mount Volume
La commande s’est terminée correctement.
OK, we are getting there. So how about in file manager now \\192.168.1.13\osmc
?
ok
point 2
server : unknown
name : osmc.home
so i made point 3/4/5
and type osmc.home in the field on windows explorer
and finally see my vero and usb drive !!
great thanks
i put the link in fast access
thanks a lot you rocks !!!
it works
great thanks for your help !!
Great news, so just for my learnings \\192.168.1.13\
still giving you an error if you put it in file manager?
no
But have you an idea why network file manager doesn t see my osmc without typing the address
??
That might be “normal” as I don’t have a Win10 machine to test I wasn’t sure. But as long as it works if you do \\192.168.1.13\osmc\
ok
you are right
Thanks a lot !!
Graceful to you, a french guy is happy tonight !!!
Hi I thought I might share this information it my help I’ve had my Vero 4k for about 8 months now with no problems enabled samba share on my Vero to transfer files from my Windows 10 pc to the 2 connected HDDs. Then I could not see the Vero on my Windows 10 pc could not figure it out thought it was the Vero. After going round in circles and reading loads of posts the answer was dead simple apparently after a Windows 10 update the Windows 10 smb client box had been unticked. Control panel all control panel items programs and features turn Windows features on or off SMB 1.0/cif client tick the box and you are connected again.
Good to know, but I’ve gone through two fairly major updates without having to reset that switch (or NFS support). Could have something to do with ‘SMB 1.0/CIFS Automatic Removal’ which appears in Win10 Home but not in Win10 Pro.
Hi
OK you are right !
with smb ticked i can see vero and my usb hdd.
The problem is : apparently smb ticked seem to be less secure …
What do you think ?
Thanks for your information
Less secure within your LAN. So the question is, do you trust your router to firewall you from the outside?