I have the Vero 4k+ and it was working very well. Went to use it today and could no longer access anything on my library. Library is via SMB to my desktop on the same network, I tried opening it back up to SMB 1 protocal, tons of other troubleshooting options as well. SMB protocol to None etc. it gives me connection timed out even if I used computer IP address/ username/pwd.
Any other suggestions, starting to think I am going crazy here as the VERO doesnt even see the smb network anymore.
Hello sorry. let me add some more detail- Currently running windows 10 Pro. Connecting from a Vero4k+. Static IP on both the Vero and the Desktop. Latest change was maybe 2 weeks ago I went from Wired to wireless on the desktop but it was working fine post change.
I tried creating a new user etc just to see what was up but that didnt fix it. When I go to connect it says connection timed out (if I go by my desktops IP) if I try by desktop name I get connection refused- I have triple checked the login ID and pwd that I always have had. I also deleted my video sources and started from scratch but it doesn’t connect/ see anything
I would assume a recent Win10 update disabled smb1.
Suggest to start investigation from command line.
Connect to OSMC by ssh and install smbclient. sudo apt-get install smbclient smbclient -L <IP of desktop>
I did the IPCONFIG on command prompt and checked that it is still correct static IP. Also went in and confirmed there are drives being shared and it is setup for “everyone” on network to see shared drives
So I created an admin level user for kodi. Added it to shared drives as well just to do eliminate that as possible issue
It went from working perfect to not, there must have been a windows update that has messed up a setting that I’m not seeing. It’s almost as if the computer isn’t allowing anything to jump on it
I would also add I can still Remote Desktop into my desktop so it is allowing other connections and plex is still streaming (other side note- not sure if relevant- under upnp plex was visible on the network from the vero
Edit- so I can’t add any more replies for 22 hours because I’m new but I pinged and got
PING 192.168.1.161 (192.168.1.161): 56 Data bytes
Edit 2: Nmap scan report for 192.168.1.161
Host is up.
All 421 scanned ports on 192.168.1.161 a
Edit 3: Connecting to 192.168.1.161 at port 445
Connecting to 192.168.1.161 at port 139
Connection to 192.168.1.161 failed (Erro
Edit 4- weird still cannot make new post but I tried the ip addr and ip ro
IP ro-osmc@lvngrm:~$ ip ro
default via 192.168.1.1 dev eth0
192.168.1.0/24 dev eth0 proto kernel sco
pe link src 192.168.1.152
192.168.1.1 dev eth0 scope link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 4096 q
disc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft f
inet6 ::1/128 scope host
valid_lft forever preferred_lft f
2: eth0: <BROADCAST,MULTICAST,DYNAMIC,UP
,LOWER_UP> mtu 1500 qdisc pfifo_fast sta
te UP group default qlen 1000
nk/ether 10:d0:7a:b1:c0:00 brd ff:
osmc@lvngrm:~$ osmc@lvngrm:~$ ip ro
-bash: osmc@lvngrm:~$: command not found
osmc@lvngrm:~$ default via 192.168.1.1 d
-bash: default: command not found
osmc@lvngrm:~$ 192.168.1.0/24 dev eth0 p
roto kernel sco
-bash: 192.168.1.0/24: No such file or d
osmc@lvngrm:~$ pe link src 192.168.1
I’ve never had to open a port internally before on my network to access smb drives I am sharing from desktop- is that something I need to do? Such an odd thing to have it go so haywire