[SPMC17] Problems with SMB3 or SMB1

[djstx2003]

Hi. until today I had shared folders that worked with SMB1 and SPMC until today. 1. today's build changed to SMB3 protocol by default. with this way I couldn't connect to my shared folders. so I went and change the setting "Maximum Protocol Version" of the SMB settings to "SMBv1". now comes the problem. I still cant connect to my shared folders. even if I try to manually set a shared folder in SMB1 I got a screen says Lock Preferences in SMB and asks me for a username and pass. I have to say that I don't have a username/password in Windows 10. in Sharing settings I have the username/password at off. how to make it work again at SMB1? any help?

2. I tried to work it with SMB3. in Windows feautures on and off I enabled the SMB Direct which is for SMB3.x protocols. then I tried to manually add a network location but it didn't worked. I got an error says Operation not permitted. what I do wrong? please mr.Koying can you help me? thank you. Spiros-Greece.

[djstx2003]

Can anyone help me with my problem? or the current build has problems and I have to wait for next build?

[djstx2003]

Please can anyone help me? i'm using Windows 10 Pro 15063.483 build and Nvidia Shield 16GB with latest firmware 5.2. what steps to do to make it working? thank u!!!

[99rook99]

I'm sure that @koying, wants logs with issues, since it works for him imagine or he wouldn't have released it.

[ziggy73701]

Whats your Windows setup? I use latest SPMC with windows 10 Pro with SMB shares no issues. Give us a bit more info.

[djstx2003]

I also used latest SPMC with windows 10 Pro. now i'm on 3rd july build. I have some shared folders from Windows 10 Pro pc that working fine until 3rd july build. with the change to SMB3 nothing worked. I changed to SMB1 but I got a screen says Lock Preferences in SMB with a username and a password. I never used a username and pass with my shared folders until now or in my Windows 10. what I do wrong? if I use SMB3 I only have to disable from Windows feautures On an Off the SMB 1.0/Cifs file sharing support right? or I have to enable SMB Direct from there to work with SMB3? these options in both SMB1 and SMB3 I tried with no success. any help what to do? thank you my friend!!!

[djstx2003]

I just tried new build. http://download.semperpax.com/spmc/android-arm/SPMC-spmc-krypton-1f5c175-armeabi-v7a.apk I have same problem. i was using 3rd July build and all worked fine. I installed this latest build and changed the setting "Maximum Protocol Version" of the SMB settings to "SMBv1". it doesn't work. mr.Koying how can I help you to fix this problem? please check this your self in Windows 10 to reproduce the problem so to understand and fix this. thank you!!!

[Schrotty74]

Same problem with latest Windows 10 Insider. SMB not working.

[Schrotty74]

With SPMC-spmc-krypton-3295bca-armeabi-v7a smb working, the latest 2 builds not working.

[ziggy73701]

OK this whole SMB thing seems to be confusing... sooo here is my setup.. and will see if this helps! It may seem a little convoluted BUT I use a Nvidia Shield with the LATEST ALPHA SPMC and get no issues.. also works with KODI... I have 2 Windows 10 Pro boxes.. with several shares on each. Obviously, you don't have to do this, but.. if it isn't working you may as well give it a punt!

Ok... On your WINDOWS 10 box create a new user called KODI (or what ever you like) and setup a password. Make sure you can logon to the PC with this account. Then log back on with your regular account. Make sure HOMEGROUP is disabled. Ensure your NETWORK LOCATION is set to PRIVATE NETWORK. Check your ADVANCED SHARING SETTINGS - Ensure TURN ON PASSWORD PROTECTED SHARING is on. (If you don't want to use a password... then I cant help you. Sorry.) Check your SHARE to ensure that EVERYONE has ACCESSS or if you have trust issues and don't want that.. at least make sure your NEW KODI account has access. LOG ON AS THAT ACCOUNT AND TEST IT... open Network and browse to the share \winpc\sharename IF it ask for a username and password then enter it in the format winpcname\kodi (or what ever name you used) IF THAT works... go to SPMC... if it doesn't.. fix the bit you did wrong. IN SPMC see if you can browse to your share.. you SOULD see username and password prompt. Again use the same format as on the PC winpcname\kodi then the password. IF THAT STILL doesn't work... Go to USERDATE and get your SOURCES.XML file. EDIT it.. and put in the shares manually.

<sources>
    <programs>
        <default pathversion="1"></default>
    </programs>
        <source>
            <name>Test Share</name>
            <path pathversion="1">smb://win10pc/sharename</path>
            <allowsharing>true</allowsharing>
        </source>
    <music>
        <default pathversion="1"></default>
    </music>
    <pictures>
        <default pathversion="1"></default>
    </pictures>
    <files>
        <default pathversion="1"></default>
        <source>
            <name>Test Share</name>
            <path pathversion="1">C:\Copy\</path>
            <allowsharing>true</allowsharing>
        </source>
    </files>
</sources>

```NOTE the format for a SMB share. 
Create a file on your desktop called passwords.xml
<passwords>
    <path>
        <from pathversion="1">smb://win10pc/testshare</from>
        <to pathversion="1">smb://username:password@win10pc/testshare/</to>
    </path>
</passwords>

Change the values to suit... you will only need 1 line for a PC regardless how many shares there are. You can have multiple PC entries in here.

Save it.. copy that... and your SOURCES.xml file to the USERDATA folder. 
RESTART SPMC... 
Be happy. 
If it doesn't work after that.. check everything. 

[djstx2003]

thank you ziggy73701 for the guide. but this is for SMB1 or SMB3? in Windows 10 did you enable or disable something from Windows feautures on and off like SMB 1.0/Cifs file sharing support if you are using SMB3?

[ziggy73701]

Nope I did nothing..... vanilla install... just share a folder. I think people worry to much about numbers.. whats more efficient etc. Some these share are accessed by 2 or 3 users at a time with some VERY big files in some cases and I have had no issues.

[djstx2003]

WOW!!!!!!!!!!! Thank you ziggy73701!!!! I finally made it working. I follow your steps and created another user with password. i check all the settings you told me and then went to SPMC. it asks me for a username and password when i browse for a share. i put them and voila all worked great!!! i also test it after that without the need for a password and also worked. i think the only that needed was the addition of a new user in Windows 10. i don't know why this. but i think the correct way is to not require a new user in Windows 10 to work right? mr. Koying he'll know better about this. lets hope he can make it to work without the need of a new user. thank you again my friend. you made me so so happy!!! Now SPMC working at SMB3 protocol. be well, Spiros!!!

[ziggy73701]

Personally.... good practise is to have a user account. MSoft ripped out a lot of the vulnerabilities and I can see more going in the future. Things like not mapping to $shares etc.

@koying is this worth a entry in the Wiki going forward?

[classicjazz]

I created a first draft of a Wiki entry here: https://github.com/koying/SPMC/wiki/Recommended-Network-Settings-for-Media-File-Serving-from-a-Network-Share

I don't run a Windows PC so I would appreciate Windows users confirming the guidance. Thanks @ziggy73701 for your recommendations, which I incorporated.

At this point it seems the potential problems are:

• FireTV wasn't working in initial build but should be now
• Windows 10 users aren't using user authentication
• Windows 10 users are trying to use SMBv1, which isn't enabled by default
• Pre-Windows 10 issues? (I didn't cover in the Wiki since Win10 has been out for years and all versions of Windows 7 and later were eligible for a free upgrade to Win10).

[Gertbucket]

As far as I'm concerned SMB is broken. Sharing works fine on SPMC 16, Kodi and MrMC, but not on SPMC 17.

[ziggy73701]

Works fine, it's something in your setup

More info

[Gertbucket]

@ziggy73701 If you have to use a workaround it's broken. It doesn't work out of the box.

[classicjazz]

@Gertbucket

In the spirit of helping us help you, perhaps you could tell us what is different about your setup than described in the Wiki. For example, Android hardware, server OS and configuration, etc. I assume you have enabled user authentication and SMBv3? What sort of logs can you supply to show the errors you are experiencing?

[Gertbucket]

@classicjazz The difference is I have not set up a user account.

The address I've set to access my Windows 10 shares is smb://host where host is the name of my server computer. This works fine in every other variation of Kodi.

Hardware: Fire TV 4K

If I set the client to SMBv3 (default) it gives the error "Operation Not Permitted" If I set the client to SMBv2 it gives the error "Operation Not Permitted" If I set the client to SMBv1 it returns a prompt for username and password.

Like I said, as far as I'm concerned if I have to set up a new user account for it to work (when it already works with Kodi 17) it's broken. Furthermore, it's broken out of the box because the client must be set to SMBv1 otherwise it returns an error.

No change in the latest alpha.

[koying]

Please try the latest alpha. I've re-added some settings for SMB1 that were gone

Oups, missed the last phrase

[koying]

Just did a test and it work in SMB1 with an untouched WIN10 as long as you have a user and password. Good enough for me, I must say...

For the tech guys, you can try various samba options by using a user.conf file, inside the .smbdirectory of the SPMC home. The actual smb.conf is overwritten at each start, so leave that one alone.

WARNING: the active .smbfolder is now inside /Android/data/com.semperpax.spmc17/files/.spmc. The one alongside .spmc is deprecated

[classicjazz]

@Gertbucket

Kodi17 and the other apps you mention doesn't support the newest protocols or security standards on Android. I recommend setting up a user account/password on your Win10 server per the Wiki and modifying your passwords.xml, accordingly. For example, see below:

`

smb://10.0.0.10/movies_hd/ smb://user:password@10.0.0.10/movies_hd/

`

If this still doesn't work (with SMBv3), please let us know. It's worth a little extra configuration effort for the faster performance and improved security.

[Gertbucket]

@classicjazz @koying Complete pain in the ass having to set up a user account and then undo all the crap that Windows opens up, and then set up all the shares again in every other network app, but yes, it does work. Can't say it's worth all the bother though, if you already have everything working without a password.

[classicjazz]

@Gertbucket

The Wiki already mentioned setting up a restricted local user account. If you are a Windows user you should always be using a restricted account rather than your administrator account, since this thwarts 90+% of security threats. I added a link in the Wiki to an external site that explains how to do this.

If you were using SMB shares before that only specifies the IP address, then it should have been a simple matter of editing your passwords.xml to add your new user/pass.

Not sure what you meant about plain text leaking but that assumes that an attacker had access to the password.xml file, then logged into your server on your home network. In which case, the worst thing they could do is read your media files if you followed the Wiki recommendations.