i cant access the share on my unraid server from windows 10 error 0x80070035 tryd all the solutions on the forum but no joy as far as i got i has to do something whit authentication 

ftp-diagnostics-20191218-1520.zip

Edited December 18, 20196 yr by kocka

Are you referring to the share anonymized as F-P in your diagnostics? You have that one configured as private. Have you tried it as public?

yes same results 

ftp-diagnostics-20191218-1542.zip

Edited December 18, 20196 yr by kocka

18 minutes ago, kocka said:

tryd all the solutions on the forum

Can you be more specific about what you tried?

i activated the smb 1.0 and in windows edited the user groups, made a local account on windows added the server ip to the host file but to no success 

Have you enabled WSD in SMB Settings?

yes

In this post, there is an example of a situation which I am going to quote below:

               

Quote

 

Let me give you an operational example.  Let's say your windows PC netbios name is "mypc" and your windows login name is "larry".  Further let's say your server netbios name is "tower" and you have a single user defined on unRaid side named "curly".  Now you open Network and click on "tower" and a window opens showing all the shares.

 

In this state, if you now click on a "public" share, what happens behind the scenes is windows tries to authenticate with the server as user "mypc\larry".  On unRaid side, samba (linux smb protocol module) will check if "larry" exists.  In this case no, so samba will check if user "mypc" exists, in this case also no.  So samba will now see that "guest" access is enabled for the server, so it will reply to Windows with "success" but on the samba side, will associate any further access with the "nobody" user on the linux side.  Meanwhile, Windows stores the fact that it successfully connected with user "mypc\larry" in its own credentials cache.

 

Now, after above, you click on a Private share where the only unRaid user with access is "curly".  Samba will see the request to the share as user "larry" and tell Windows that the connection is unauthorized (because larry is not in the list of users for the Private share).  Windows sees this and presents you with a username/password dialog box.  So you enter "curly" as the user.  But now Windows sees that you already have a connection to the server as user "larry" and it DOES NOT ALLOW multiple connections to the same server via different user names.  This is a well-known limitation/bug in Windows.  Some people get around it, e.g., by connecting to the sever using the IP address in order to fool windows into thinking it's a different server.

 

 

even whit a local windows account i enter the user name and pass and it dos not let me see the shared folders it says user name or password is incorrect there are no multiple connections, just can see the share on windows 10 multiple pc`s it works on my phone    

Go into Windows Control Panel - Credential Manager and delete any credentials for Unraid so they can be renegotiated.

did not find any pertaining to unraid i did create one whit the server IP and correct login credentials but same error  

20 minutes ago, kocka said:

did not find any pertaining to unraid i did create one whit the server IP and correct login credentials but same error  

You don't need to create one. Delete it so it can be renegotiated when you try to access.

i did not find any for unraid

Then what did you mean by

30 minutes ago, kocka said:

i did create one whit the server IP and correct login credentials

 

these are the ones that i can see i made one windows and one generic one same results 

You don't need to make any. They will be made for you when you first try to access the share.

 

In any case, it shouldn't matter for a public share. Are you still trying it as a public share?

 

Can you post a screenshot of this "same result" you keep getting?

yes it is still on public 

Post up another diagnostics file in your next post.

 

as you asked 

ftp-diagnostics-20191218-2325.zip

Edited December 18, 20196 yr by kocka

Is your workgroup on WIN10 set to   WORKGROUP   ?

 

Is this computer (by any chance) a company computer? 

 

Did you do this:

 

 

 

no it`s my test rig. 

it was the firs thing that i found and tried 

I almost hate to suggest this but reboot both the server and the WIN10 computer.  (We are almost to the area of using witchcraft and incantations.   🙄  )

diag file after restart same error

ftp-diagnostics-20191219-0005.zip

Edited December 18, 20196 yr by kocka

access it by ip and to root and not any shares, i.e.

 

\\192.168.0.200\

 

if you get prompted for creds, use your unraid user/root. if share is public, try and access it.

same