Windows 10 smb share on new vero 4K

[Blardyslartfast]

I have a pi that has osmc and just got the new vero 4k.

I can’t add a source via videos/files/add videos/browse. …Nothing comes up.

I tried typing in the share location smb://DESKTOP/TV Shows …I get operation not permitted

Then I got - Couldnt retrieve directory info due to network not connected, add anyway?

I tried smb://192.168.1.4/TV Shows I get operation not permitted.

I have the folder shared to everyone and the W10 machine has a username and password.

I read sevearal threads here and i can’t find the answer

The vero is connected on to the intrenet and shows up as a device on my router.

The other thread said that smb shares no longer work due to wanna cry is this true? is there a way past this?

https://paste.osmc.tv/owelaqevay … if that helps

[fzinken]

@Blardyslartfast

The other thread said that smb shares no longer work due to wanna cry is this true? is there a way past this?

Well that is not correct in that way. SMB Browsing (a feature of SMB1) is not available anymore since a Wannacry security update.
But adding the sources manually should still work. I think the easiest for you would be either of these to steps:

1. Copy the sources.xml and passwords.xml files from your pi (folder .kodi/userdata) to the vero4k
2. As an alternative use fstab based samba mounts they are also more performant Configuring fstab based Samba share mounts

[fzinken]

@Blardyslartfast

https://paste.osmc.tv/owelqevay … if that helps

The logs seems empty

[Blardyslartfast]

https://paste.osmc.tv/owelqevay

[fzinken]

@Blardyslartfast

I edited it owelaqevay

Still it is empty. Anyhow do one of my suggestions.
And also remember this

Unable to access shares after 2016.04-1 update

Thanks fzinken. I had one last go before I started the log process and it worked. W10 shortened the username to four letters. I used this password/user combo earlier no luck. I must have got something right eventually.

[Blardyslartfast]

I tried the fstab instructions which resulted in no added sources. perhaps there is some detail I got wrong.

Can you tell me how to move the files?

[fzinken]

@Blardyslartfast

I tried the fstab instructions which resulted in no added sources. perhaps there is some detail I got wrong.

Well after mounting the shares via fstab you then need to add them as sources via Rootfolder → mnt → your share

@Blardyslartfast

Can you tell me how to get the xml files?

Well either you copy them via your PC (e.g. winscp) or the easiest directly from your pi to the vero. On the pi:
scp .kodi/userdata/sources.xml <IP-of-your-vero>:/home/osmc/.kodi/userdata/
scp .kodi/userdata/passwords.xml <IP-of-your-vero>:/home/osmc/.kodi/userdata/

[Blardyslartfast]

so I just enter those commands into putty while connected to the pi?

[fzinken]

@Blardyslartfast

so I just enter those commands into putty while connected to the pi?

Yes, while I still would suggest to use the fstab method especially if you already done the mounting part

[Blardyslartfast]

I tried transferring the files via putty but that didnt add access. The pi that has access to the folders does not come up with browse options when you try to add a source either.

I followed the fstab instructions up to:

At this point, your shares should just work. To test, simply try to go to the share:

$ cd /mnt/Server_Movies
$ ls

and it comes up

[fzinken]

@Blardyslartfast

I tried transferring the files via putty but that didnt add access

Did you restart Kodi?

@Blardyslartfast

At this point, your shares should just work. To test, simply try to go to the share:

$ cd /mnt/Server_Movies

$ ls

Post cat /etc/fstab | paste-log and dmesg | paste-log

[Blardyslartfast]

Thanks fzinken.

I’m sure the file transfer method is what worked. I understand that it may not be the most ideal.

heres the outcome of fstab method in putty.

I don’t think it worked. I’ll stick with the current setup

[fzinken]

@Blardyslartfast

I’m sure the file transfer method is what worked. I understand that it may not be the most ideal.

That’s OK, just your last message was it didn’t work.