Good idea. I didn’t think of that.
I attempted to access my mounts from the file manager like you mentioned and received a “Couldn’t connect to network server” error, so I assume that means that when I play content from my Vero that it’s not accessing the files via FSTAB mounts like I want it to?
Since you setup FSTAB, I assume you know how to use SSH?
From ssh what happens if you try:
cd /mnt/Server_MoviesI’m very much a novice with Linux but did my best to follow the guide at Configuring fstab based NFS share mounts to get everything set up.
If I connect to the Vero through SSH and try the command you mentioned, I get “No such device”
The “cd /mnt/Server_Movies” command was always the point that I couldn’t get past when I was trying to properly configure everything through that guide. Since most of the time my movies worked, I assumed that I did everything correctly but now I’m realizing that probably wasn’t the case.
You are confusing things. The link you are using is for NFS mounts. You would use those from another linux server and rarely from Windows servers. You are use Samba (or SMB) mounts in your fstab.
Have your tried:
smbclient -L 192.168.1.110 -U <my_username>
Oh okay, so because I’m sharing my files on a windows machine, you’d actually recommend I do it via SMB shares but still through configuring FSTAB?
If I type in the command that you referenced, here’s what I get back:
osmc@osmc:~$ smbclient -L 192.168.1.110 -U Brian
WARNING: The “syslog” option is deprecated
Enter Brian’s password:
Connection to 192.168.1.110 failed (Error NT_STATUS_IO_TIMEOUT)
Once again, thanks for walking me through all of this. Most of it is clearly over my head, if that wasn’t readily apparent.
First you need to verify your WIndows system IP. Is it really 192.168.1.110?
Yep, can definitely confirm that.
What happens if you try
smbclient -m SMB3 -L 192.168.1.110 -U brianI get the same error message. I assume when it asks me to “enter brian’s password” that I provide the same password as to when I login to the vero through SSH?
osmc@osmc:~$ smbclient -m SMB3 -L 192.168.1.110 -U brian
WARNING: The “syslog” option is deprecated
Enter brian’s password:
Connection to 192.168.1.110 failed (Error NT_STATUS_IO_TIMEOUT)
That tells me that you have a problem with your Windows system then. Can you ping it?
ping 192.168.1.110
Can you ping it by name? Most likely the computer name followed with .local, so:
ping mywindowscomputer.localC:\Users\Brian>ping 192.168.1.110
Pinging 192.168.1.110 with 32 bytes of data:
Reply from 192.168.1.110: bytes=32 time<1ms TTL=128
Reply from 192.168.1.110: bytes=32 time<1ms TTL=128
Reply from 192.168.1.110: bytes=32 time<1ms TTL=128
Reply from 192.168.1.110: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Can ping it by name as well.
That was from the Windows system, how about from the Vero? (ping will keep running until you type CTRL-C)
1 Like
Didn’t work.
osmc@osmc:~$ ping 192.168.1.110
PING 192.168.1.110 (192.168.1.110): 56 data bytes
— 192.168.1.110 ping statistics —
94 packets transmitted, 0 packets received, 100% packet loss
osmc@osmc:~$
Ok, now we are getting somewhere… You can’t ping the Windows machine. Did you try by name?
Just tried. Same issue. 100% packet loss.
Well then, you have a network issue. From the Windows PC can you ping the Vero?
On the Vero what do you get from:
ifconfig