[SOLVED] Can't connect from Windows to samba-4.6.7 on current. Same config works fine on SW14.1/samba-4.2.1-x86_64-1
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can't connect from Windows to samba-4.6.7 on current. Same config works fine on SW14.1/samba-4.2.1-x86_64-1
Hi,
I have installed current on my working partition and I find that I can no longer connect from my Windows PC's to the Linux server. Connection from Android still works fine though. The package is samba-4.6.7-x86_64-1. Of course I have the users added to samba, and I can connect from Android.
If I boot from an older partition running Slackware-14.1 with
samba-4.2.1-x86_64-1, then I can connect from Windows.
I tried to go back to older samba packages but that soon breaks other things (mplayer). I didn't succeed at rebuilding the samba-4.2.1 package on current.
Anyone knows if something special needs to be done when migrating.
Two quick questions: what version of Windows and how does the failure occur? That is, what message does Windows give, and what does the samba log file say? Most of these are authentication problems and are resolved with a trivial tweak to smb.conf. I vaguely recall having to deal with this issue last samba upgrade, but that was some time ago.
Two quick questions: what version of Windows and how does the failure occur? That is, what message does Windows give, and what does the samba log file say? Most of these are authentication problems and are resolved with a trivial tweak to smb.conf. I vaguely recall having to deal with this issue last samba upgrade, but that was some time ago.
Hi,
I am running Windows-7 on two older TabletPC's. The message I get from Windows after I have entered my credentials is "The specified network password is not correct." Obviously there is an issue in the communication of the credentials between Windows7 and Samba.
To answer your question, I first clear older log files from /var/log/samba then do "Map network drive" from the PC. Afterwards there is a single empty log file /var/log/samba/log.192.168.1.104 sitting in the log directory. I can confirm that the same procedure works fine when I boot the older Linux partition.
I tested with the initial smb.conf file copied from the older Linux partition. Then I edited that file to reflect information I found when googling on that problem and none of the suggested changes had any impact on the functionality. Here is the content of my current smb.conf.
Code:
[global]
workgroup = RLXNET
server string = pc3_ss
log file = /var/log/samba/log.%m
max log size = 50
security = user
passdb backend = tdbsam
hosts allow = 192.168.1.
hosts deny = ALL
dns proxy = No
# wins server = 192.168.1.100
# wins support = no
# smb ports = 139
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
usershare allow guests = no
# domain logons = yes
# domain master = yes
server signing = auto
[richard]
comment = Home
path = /
valid users = richard
force user = richard
force group = richard
read only = No
create mask = 0600
directory mask = 0700
[dan]
comment = Home
path = /home/dan
valid users = dan
force user = dan
force group = dan
create mask = 0600
directory mask = 0700
[printers]
comment = All Printers
path = /var/spool/samba
guest ok = Yes
printable = Yes
browseable = No
[ML-1710]
comment = Samsung ML-1710
path = /var/spool/samba
read only = No
guest ok = Yes
printable = Yes
printer name = ML-1710
[sa301]
path = /sa301
read only = No
create mask = 0600
directory mask = 0700
[root]
path = /
valid users = root
force user = root
force group = root
read only = No
directory mask = 0700
Agree with above, there should be *some* indication that permission was refused by samba, maybe in the syslog.
You mentioned fixes you found by googling, however I don't see any in smb.conf.
Did you try lanman auth = yes, for example? Yeah I know, probably not the issue.
I'd also check on smbpasswd; I seem to recall that you had to redo the password for the new samba install.
I'll check on my install when I get a chance to see if there's something else that comes to mind.
Last edited by mostlyharmless; 09-06-2017 at 02:51 PM.
Strangely there is no message recorded in either syslog, messages or /var/log/samba except that the files log.192.168.1.104 and log.pc4 are created empty.
Yes I have redone the password data base at one point; I thought maybe the new version of samba uses a different database so I re-made the database to make sure everything is upgraded. I first needed to correct smb.conf as follows to be able to change my password. I changed the password and still the password is not recognized from Windows.
Code:
hosts allow = 192.168.1. 127.0.0.1
I will try to make samba more verbose and report anything new. I did that a week ago but didn't find any clue.
Strangely there is no message recorded in either syslog, messages or /var/log/samba except that the files log.192.168.1.104 and log.pc4 are created empty.
Yes I have redone the password data base at one point; I thought maybe the new version of samba uses a different database so I re-made the database to make sure everything is upgraded. I first needed to correct smb.conf as follows to be able to change my password. I changed the password and still the password is not recognized from Windows.
Code:
hosts allow = 192.168.1. 127.0.0.1
I will try to make samba more verbose and report anything new. I did that a week ago but didn't find any clue.
Not sure if this matters, but my "hosts allow" line looks like:
(Edit) I checked in my PC using secpol.msc and the current setting of LAN manager authentification level is 'use NTLMv2 session security if negotiated'. If someone can make something out of that.
Last edited by rlx; 09-06-2017 at 07:40 PM.
Reason: Augmentation
I think I have the solution to this problem. The following line needs to be added to smb.conf. I got that tip from this site.
Code:
ntlm auth = yes
I believe that line is needed with the current Slackware build of Samba. The line was not needed with the earlier version of Samba I used on my old partition.
Thank's to every one on this thread for contributing.
Last edited by rlx; 09-06-2017 at 08:00 PM.
Reason: Corrected broken link
Additionally, the current build of Samba (or is it the newer version of Samba itself) breaks my symbolic links. Windows says "You do not have access to ..." where ... denotes the name of a symlinked directory. The symlink is within the tree of the path declared in smb.conf but is outside the user /home/user path.
Again that problem occurs only when I connect to my Samba running Linux PC from my windows7 tablet PC's. I don't have the problem when connecting from an Android phone.
So this is a Windows-Samba specific issue.
Quote:
[global]
workgroup = RLXNET
server string = pc3_ss
log file = /var/log/samba/log.%m
max log size = 50
security = user
follow symlinks = yes
wide links = yes
ntlm auth = yes
passdb backend = tdbsam
hosts allow = 192.168.1. 127.0.0.1
hosts deny = ALL
dns proxy = No
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
usershare allow guests = no
server signing = auto
[richard]
comment = Home
path = /
valid users = richard
force user = richard
force group = richard
read only = No
create mask = 0600
directory mask = 0700
(Edit) That problem is solved by adding the following line to the global section of smb.conf (above). At last I recovered the communication between Windows and Samba :-).
Thank you, adding "ntlm auth = yes" solved my problem with WinPE (based on Windows10) not connecting to samba server 4.7.6 with default settings in smb.conf.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.