Hello,

 

hope you guys can help me out here.

i got my Oppo today and it cant connect to my SMB Share, it always tells me the Account is wrong. 

What i have done without success:

-adding "ntlm auth = yes" to SMB extras

-adding "server min protocol = CORE" to SMB extras, but "removed" it with an # right now

-enabling NetBios (SMB v1?!)

 

SMB is working fine all my other devices..

Find a support forum for your Oppo 203 and ask your question there...

But it is working if i connect to a smb Share on my Windows Machine. So it must be something with the Share on unraid.

What is the security level on the Unraid share?

 

Is the Oppo asking for a login and password?

 

If you have a password on the Unraid Share, does that password contain any characters besides numbers and letters? 

i tried all 3 settings, but right now it is on Public.

yes, i can see the share and after entering my Password it tells me, it is wrong.

no, i have a 4 digits password, only numbers. Also tried a test Account Name "a" and password "a", no luck here, always wrong password..

 

i found a lot that had to activate smb v1, but it didnt helped for me.

also found some with Linux Server and they had to to add "ntlm auth = yes" to smb.conf (which is smb extras here as far as i know)

 

what someone with debian Server needed, was that in smb.conf:

server min protocol = NT1

ntlm auth = ntlmv1-permitted

 

but i dont know how to write it right in unraid

32 minutes ago, Meannekes said:

server min protocol = NT1

 

According my notes, this is the only thing you need to restore SMBv1.

 

IF you are using the NETBIOS name to access the server, try the IP address of the server in its place.

 

Many devices only allow one SMB connection to each server.  Once a client (your Oppo) is logged onto the server, it probably won't permit a second SMB connection to the same server and often (for example, Windows) the error message is not indicative of the true problem.   You often have to completely shutdown the client to knock down the connection.   BTW, it is good advice anytime you make a change to make sure that what you think you are trying is actually the cause of the failure and not the residue effect of an earlier action. 

 

56 minutes ago, Meannekes said:

yes, i can see the share and after entering my Password it tells me, it is wrong.

 

If you can see the share, this would indicate to me that you already have logged unto the server as a "guest" which would only give you public access.   IF you are being prompted for a user  name and password, try hitting the <enter> key for each prompt if the share security is 'Public'.

My tests with a Windows Share wasnt working until i deactivated Password Protected Sharing in Windows Sharing Konfigurations.

Before that, i had the same issues on Windows with the wrong Account Password.

Now i have to find out, how to get that working on unraid. (again it is already on "public")

 

I suspect that the latest version of SAMBA has tighten up security on guest access.  (Just as Windows has...)   I would suggest that you google 'adding guest access in samba' and see if there might be a solution that will work there. 

 

I did have a look at the Samba configuration files (found in    /etc/samba   ) and I did not see that they had anything about adding public access.  But all of my shares are 'Private' and guest type access is out of the question by definition. 

 

As a bit of information, I had some old Netgear NTV550 media players (from 2011) that only had SMBv1 support.  I suspect that SAMBA security updates were coming and I replaced with them with mini Windows PC's with KODI installed earlier this year.   They do work fine and have features that the NTV550 lacked.   (One thing is that I can use a common database for all of my media data  that is managed by mysql Docker on my Unraid server.) 

 

The Windows mini PC (~$200US) may be overkill as folks are running KODI on Raspberry Pi's!

If you need to see how SAMBA is setup on your server after the entire smb.conf (including the the include files) has been executed, open the GUI terminal (the   >_    icon on the toolbar)  and type the following:

testparm -s

 

Problem solved..

but i dont know why 😅

i missclicked and opened the "isos" Share from unraid.. and it just worked.

My "media" Share still does not work.. dont know why, maybe some error or so because i renamed it once.. everything else is set up the same way like "isos" right now.

Created a new Share for my media Stuff, and it works.. will transfer my Files over and delete the old Share

 

Not solved..

after i moved 5-6 isos Files and my Music Flac Files, i get the same error on the new share..

Maybe some Sh** with äüö or so.. cant think of anything else right now, before moving i had access to the new Share, will investigate further

after moving it back again i still have no access with the Oppo. (Moving everything with "Dynamix File Manager".

after deleting the share and creating a new one i copied the Movies with my Windows VM on unraid and i have access, cant understand why a share is not accessable anymore after using "Dynamix File Manager" on it. i checked ownership and rights on every File and everything looked fine. 

Edited June 10, 20224 yr by Meannekes