User avatar
Fieel
Posts: 10
Joined: Thu Dec 21, 2017 4:18 pm

Windows 10 cannot access samba share

Thu Dec 21, 2017 5:17 pm

Hello,

i have a problem with samba: i configured Raspbian to share a folder over my LAN, i can access the folder through my two android devices but my Windows 10 desktop PC won't allow me.

I tried everything! Tried to follow a lot of similar threads i found googling but nothing worked. It's probably my windows computer because i can access the folder with other devices!

i can see the raspberry pi with windows explorer like this:
Image



but when i try to access the raspberry i get this message (error code: 0x80070035):
Image



Even if i try to access directly using the ip, i get this message: (error code: 0x80004005):
Image

This happens both if i access the /share/ or /share/folder path.

This is my smb.conf file, sorry about the endless comments:

Code: Select all


#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.

#======================= Global Settings =======================

[global]


## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP


# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

[homes]
   comment = Home Directories
   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

[web_server]
        path = /var/www/dai-gurren
        writable = yes
        browsable = yes
        guest ok = yes
        public = yes


What could be the problem? I really don't know what else to do.

User avatar
Fieel
Posts: 10
Joined: Thu Dec 21, 2017 4:18 pm

Re: Windows 10 cannot access samba share

Sat Dec 23, 2017 1:09 pm

Guys nobody can really help me? I've been stuck for some days now..

User avatar
DougieLawson
Posts: 35581
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Windows 10 cannot access samba share

Sat Dec 23, 2017 3:14 pm

Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

akisg
Posts: 3
Joined: Sat Dec 16, 2017 4:57 pm

Re: Windows 10 cannot access samba share

Sat Dec 23, 2017 4:21 pm

Fieel wrote:
Sat Dec 23, 2017 1:09 pm
Guys nobody can really help me? I've been stuck for some days now..
Trying myself to make a shared folder from a rpi3 to my network (windows and linux), i used this guide https://raspberrypihq.com/how-to-share- ... pberry-pi/
I can now access the share folder that i created through my network. With my little knowledge so far, i can see that you haven't created any shared path into the smb.conf file, maybe that's the prob. Also, i could see the rpi in the first place into my windows 10 pc network, but it then disappeared, although i can still access the shared folders if i just type the ip address of my rpi into the explorer.

User avatar
Fieel
Posts: 10
Joined: Thu Dec 21, 2017 4:18 pm

Re: Windows 10 cannot access samba share

Sun Dec 24, 2017 11:48 am

akisg wrote:
Sat Dec 23, 2017 4:21 pm
With my little knowledge so far, i can see that you haven't created any shared path into the smb.conf file, maybe that's the prob.
What you mean? My shared folder is at the bottom of the smb.conf file:
[web_server]
path = /var/www/dai-gurren
writable = yes
browsable = yes
guest ok = yes
public = yes

User avatar
Fieel
Posts: 10
Joined: Thu Dec 21, 2017 4:18 pm

Re: Windows 10 cannot access samba share

Sun Dec 24, 2017 3:00 pm

Nice interesting article about the problems of SMBv1! Thank you for sharing.

Added
min protocol = SMB2
to my smb.conf file for safety but that didn't fix my issue.

In case someone stumbled upon this thread looking for a solution, i found one. Basically the Error 0x80004005 means "you can't access this shared folder because your organization's security policies block unauthenticated guest access." I noticed my shared folder (as you can see from my smb.conf file i pasted on my first post) was enabled for guests and had no security at all. That wasn't an error, i wasn't interested in security, but i had to change it because apparently windows doesn't appreciate it:

Code: Select all

	[global]
		security = user
	
	[web_server]
	        path = /var/www/website_folder
	        read only = no
 	       writable = yes
 	       browsable = yes
 	       valid users =  *username1*
 	       force user = *username1*
  	      create mask = 0640
  	      directory mask = 0750
Stuff didn't work yet so i tried setting the psw again for my user:

Code: Select all

smbpasswd -a *username1*
Now i can access the folder and stuff works correctly.

diman82
Posts: 1
Joined: Mon Nov 05, 2018 11:32 pm

Re: Windows 10 cannot access samba share

Mon Nov 05, 2018 11:33 pm

Set the following registry value to 1

HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth

If its not there create the value as a DWORD

plugs
Posts: 8
Joined: Thu Feb 01, 2018 3:09 pm

Re: Windows 10 cannot access samba share

Tue Jan 22, 2019 11:00 pm

THANKS the regfistry change worked a treat on WIndows 10 1809

subtlenv
Posts: 3
Joined: Sat Sep 15, 2018 3:04 pm

Re: Windows 10 cannot access samba share

Sat Jun 29, 2019 12:35 pm

thanks to diman82 for the fix.

here's my gist for exported reg entry; created this is mainly because I don't have pretty good memory #lol

hope this saves some time -> https://gist.github.com/xyznaveen/850a6 ... f3bea728d7

tengotengo
Posts: 2
Joined: Mon Oct 15, 2018 4:21 am

Re: Windows 10 cannot access samba share

Wed Aug 21, 2019 6:16 am

diman82 wrote:
Mon Nov 05, 2018 11:33 pm
Set the following registry value to 1

HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth

If its not there create the value as a DWORD
this worked! tried everything, finally

Return to “Raspbian”