LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 08-07-2018, 08:29 AM   #1
road hazard
Member
 
Registered: Nov 2015
Posts: 145

Rep: Reputation: Disabled
Question SMB share keeps asking for password on Win 7 machine


I have a few Guest access SMB shares setup in Antergos. Other Linux boxes and a Windows 10 machine can access them without being prompted for a password but my Windows 7 box, not so much. I keep getting prompted for a password when it tries to hit the SMB share.

I looked at the guide ( https://antergos.com/wiki/desktops/g...initive-guide/ ) and didn’t see anything about dealing with password prompts.

I looked at the Arch wiki on SMB and what they recommended to fix the password prompts, I already have in there.

Here’s my smb.conf file, what am I missing?

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 (perhaps too
many!) most of which are not shown in this example
For a step to step guide on installing, configuring and using samba,
read the Samba-HOWTO-Collection. This may be obtained from:
http://www.samba.org/samba/docs/Samb...Collection.pdf
Many working examples of smb.conf files can be found in the
Samba-Guide which is generated daily and can be downloaded from:
http://www.samba.org/samba/docs/Samba-Guide.pdf
Any line which starts with a ; (semi-colon) or a # (hash)
is a comment and is ignored. In this example we will use a
for commentry and a ; for parts of the config file that you
may wish to enable
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]

socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=131072 SO_SNDBUF=131072
strict allocate = Yes
read raw = Yes
server signing = No
write raw = Yes
strict locking = No

min receivefile size = 16384
use sendfile = Yes
domain master = yes
preferred master = yes
local master = yes
os level = 255
force user = gene
force group = sambashare
security = user
map to = Bad User

usershare path = /var/lib/samba/usershares
usershare max shares = 100
usershare allow guests = yes
usershare owner only = yes

workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = WORKGROUP

server string is the equivalent of the NT Description field
server string = Samba Server

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 server” 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

This option is important for security. It allows you to restrict
connections to machines which are on your local network. The
following example restricts access to two C class networks and
the “loopback” interface. For more examples of the syntax see
the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.

Uncomment this if you want a guest account, you must add this to /etc/passwd
otherwise the user “nobody” is used
; guest account = pcguest

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

Put a capping on the size of the log files (in Kb).
max log size = 50

Specifies the Kerberos or Active Directory realm the host is part of
; realm = MY_REALM

Backend to store user information in. New installations should
use either tdbsam or ldapsam. smbpasswd is available for backwards
compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam

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.
Note: Consider carefully the location in the configuration file of
this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m

Configure Samba to use multiple interfaces
If you have multiple network interfaces then you must list them
here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24

Where to store roving profiles (only for Win95 and WinNT)
%L substitutes for this servers netbios name, %U is username
You must uncomment the [Profiles] share below
; logon path = \%L\Profiles%U

Windows Internet Name Serving Support Section:
WINS Support - Tells the NMBD component of Samba to enable it’s WINS Server
; wins support = yes

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

WINS Proxy - Tells Samba to answer name resolution queries on
behalf of a non WINS capable client, for this to work there must be
at least one WINS Server on the network. The default is NO.
; wins proxy = yes

DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
via DNS nslookups. The default is NO.
dns proxy = no

These scripts are used on a domain controller or stand-alone
machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g

#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writable = yes

Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no

Un-comment the following to provide a specific roving profile share
the default is to use the user’s home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes

NOTE: If you have a BSD-style print system there is no need to
specifically define each individual printer
[printers]
comment = All Printers
path = /usr/spool/samba
browseable = no

Set public = yes to allow user ‘guest account’ to print
guest ok = no
writable = no
printable = yes

This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes

A publicly accessible directory, but read only, except for people in
the “staff” group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = no
; printable = no
; write list = @staff

Other examples.
A private printer, usable only by fred. Spool data will be placed in fred’s
home directory. Note that fred must have write access to the spool directory,
wherever it is.
;[fredsprn]
; comment = Fred’s Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes

A private directory, usable only by fred. Note that fred requires write
access to the directory.
;[fredsdir]
; comment = Fred’s Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no

a service which has a different directory for each machine that connects
this allows you to tailor configurations to incoming machines. You could
also use the %U option to tailor it by user name.
The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes

A publicly accessible directory, read/write to all users. Note that all files
created in the directory by users will be owned by the default user, so
any user with access can delete any other user’s files. Obviously this
directory must be writable by the default user. Another user could of course
be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no

The following two entries demonstrate how to share a directory so that two
users can place files there that will be owned by the specific users. In this
setup, the directory should be writable by both users and should have the
sticky bit set on it to prevent abuse. Obviously this could be extended to
as many users as required.
;[myshare]
; comment = Mary’s and Fred’s stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
 
Old 08-07-2018, 04:07 PM   #2
Rickkkk
Senior Member
 
Registered: Dec 2014
Location: Montreal, Quebec, CANADA
Distribution: Arch
Posts: 1,104

Rep: Reputation: 417Reputation: 417Reputation: 417Reputation: 417Reputation: 417
Hey again road_hazard,

Before getting into micro-analyzing your smb conf files, something in your situation is leading me to wonder if this isn't a problem I myself have come across ...

You say you are able to connect correctly with all of your clients (other linux machines and a Win10 computer) without issues ? The only one giving you problems is the Win7 computer ? When you get asked for a password are you still able to log in after providing one ?

The possible cause I would look into and eliminate first would be the mismatch of smb protocol versions. This hit me not long ago and required the proper options to work around. When updating your various systems, you may have ended up, as I did, with implementations of the smb protocol on your various linux and windows boxes that are using a different version by default (1.0, 2.0 or 3.0 ...). This can lead to connectivity issues.

Troubleshooting involves specifying the specific version of smb to use on the client and server and finding which combination works for all of your systems.

Another option would be to upgrade the W7 box to W10. I believe this is a free upgrade path with Microsoft. This would guarantee that this computer would be using the most recent default version of smb.

Hope this helps - please don't hesitate if it wasn't clear enough.

Last edited by Rickkkk; 08-07-2018 at 04:09 PM.
 
Old 08-07-2018, 04:29 PM   #3
road hazard
Member
 
Registered: Nov 2015
Posts: 145

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Rickkkk View Post
Hey again road_hazard,

Before getting into micro-analyzing your smb conf files, something in your situation is leading me to wonder if this isn't a problem I myself have come across ...

You say you are able to connect correctly with all of your clients (other linux machines and a Win10 computer) without issues ? The only one giving you problems is the Win7 computer ? When you get asked for a password are you still able to log in after providing one ?

The possible cause I would look into and eliminate first would be the mismatch of smb protocol versions. This hit me not long ago and required the proper options to work around. When updating your various systems, you may have ended up, as I did, with implementations of the smb protocol on your various linux and windows boxes that are using a different version by default (1.0, 2.0 or 3.0 ...). This can lead to connectivity issues.

Troubleshooting involves specifying the specific version of smb to use on the client and server and finding which combination works for all of your systems.

Another option would be to upgrade the W7 box to W10. I believe this is a free upgrade path with Microsoft. This would guarantee that this computer would be using the most recent default version of smb.

Hope this helps - please don't hesitate if it wasn't clear enough.
Thanks for the info! I'll look into the SMB versions.

Because of some specialized software on my Win 7 box, upgrading to Win 10 isn't an option. It has to stay on 7.
 
  


Reply

Tags
password, smb.conf


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
smb set to "share", xp login asking for password creznedmick Linux - Networking 10 05-17-2007 04:18 AM
Suse 10 smb asking for password when security = share therapist Linux - Networking 5 05-19-2006 04:52 AM
How do I remount a network SMB share (on reboot) requiring a username & password BuckRogers01 Linux - Networking 1 07-09-2005 11:53 AM
Share Redhat 9 Printer with Win 2000 Machine Paul Mon Linux - Hardware 2 10-31-2003 11:31 AM
printing to <SMB Share> win printer bbaley Linux - General 0 05-28-2003 12:46 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 03:31 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration