SMS 2.9 and Samba > 3.0.26

[pastito]

Hi folks!

I upgraded my server to Ubuntu 8.10 (AMD 64 bit version by the way).

The problem is that it has Samba version 3.2.3.

SMS did not like it and it took me a lot of work to try to debug... finally I found out that changing the security = user for security = share in /etc/samba/smb.conf, made SMS work... but it is a very poor solution as my windows clients will not work properly with that setting.

Any ideas?

Here are the contents of SMS.smb:

192.168.0.20
PANCHA
PLAYSTATION2
pastito
some_passwd
PS2

And here is the /etc/samba/smb.conf share:

[ps2]
comment = Shared directory for PS2
writable = no
locking = no
path = /home/pastito/movies
public = yes



Best Regards

[pastito]

[2009/01/01 23:45:30, 3] libsmb/ntlm_check.c:ntlm_password_check(370)
ntlm_password_check: Lanman passwords NOT PERMITTED for user pastito
[2009/01/01 23:45:30, 4] libsmb/ntlm_check.c:ntlm_password_check(401)
ntlm_password_check: Checking LMv2 password with domain WORKGROUP
[2009/01/01 23:45:30, 4] libsmb/ntlm_check.c:ntlm_password_check(411)
ntlm_password_check: Checking LMv2 password with upper-cased version of domain WORKGROUP
[2009/01/01 23:45:30, 4] libsmb/ntlm_check.c:ntlm_password_check(421)
ntlm_password_check: Checking LMv2 password without a domain
[2009/01/01 23:45:30, 4] libsmb/ntlm_check.c:ntlm_password_check(434)
ntlm_password_check: Checking NT MD4 password in LM field
[2009/01/01 23:45:30, 3] libsmb/ntlm_check.c:ntlm_password_check(457)
ntlm_password_check: LM password, NT MD4 password in LM field and LMv2 failed for user pastito
[2009/01/01 23:45:30, 5] auth/auth.c:check_ntlm_password(272)
check_ntlm_password: sam authentication for user [pastito] FAILED with error NT_STATUS_WRONG_PASSWORD
[2009/01/01 23:45:30, 2] auth/auth.c:check_ntlm_password(318)
check_ntlm_password: Authentication for user [pastito] -> [pastito] FAILED with error NT_STATUS_WRONG_PASSWORD
[2009/01/01 23:45:30, 5] auth/auth_util.c:free_user_info(1985)
attempting to free (and zero) a user_info structure

[pastito]

By changing security = share in samba what I did was to enable login to the share without password. This is why it is working.

So the basic problem remains and is: SMS is no longer beign able to authenticate with user/password.

Also by doing the following:

[global]
security = SHARE
msdfs root = Yes
guest account = nobody

[ps2]
comment = Shared directory for PS2
path = /home/pastito/movies
read only = No
guest ok = Yes
locking = No

# chmod 777 /home/pastito/movies

Makes that directory writable from my PC.

It is insecure but the only workaround I have found.


Best Regards

[theedgede]

Hi,

I'm trying to use sms 2.9rev2 with my samba share for two days now without any success.

I have the feeling, that sms don't even try to connect to samba. There are no samba log entries, no network device icons and even there are no error messages in sms.

I'm using Ubuntu 8.10 with Samba 3.2.3. My network consist of a switch, a router, ubuntu-server, ps2 and a windows machine.
Connection to the samba share through Windows works as it should.

The ps2 has a network connection, because I can ping it and access it through ftp.

In the sms configuration I have selected the SMB/CIFS network protocol, operation mode: auto-negotiation.
IPCONFTIG.DAT:
IP: 192.168.178.10
Mask: 255.255.255.0
Gateway: 192.168.178.1

My SMS.smb:
192.168.178.5
Ubuntu
PS2
marek
passwd

I have tried different variations of the SMS.smb file (with and without user information, different usernames (ipusername, ip@username)).

My /etc/samba/smb.conf after several changes and tryouts:

[global]
workgroup = WORKGROUP
netbios name = UBUNTU
interfaces = eth0
security = share
guest account = nobody
encrypt passwords = false
msdfs root = yes

[share]
path = /home/marek/share
read only = no
guest ok = yes
locking = no

Finally I have also tried to use a Windows Shared Folder……no success.

Any Ideas/suggestions?

Are there any linux tools like RadHostClient witch I can use throw a command line?

Best Regards

[chimpin]

I found the solution in this page, but it's written in spanish, perfect for me but not for many other people. I'll try to explain the whole thing with my poor english

At some point the samba guys changed some default settings in smb.conf. If you have Ubuntu like me you experienced the problem updating from 7.10 to 8.04 (at this point the samba library changed this defaults in smb.conf)

Before
lanman auth = yes
Now
lanman auth = no

You have to put back lanman auth to yes and then restart the samba daemon /etc/init.d/samba restart

The problem is that the sms access samba shares in the same way as the win9x systems. If you search solutions for people trying to access win9x systems to samba servers you'll get it.


I'll try to make it easy.

1) check lanman auth option state with testparm -vs | grep lanman
2) if it's set to no
3) change /etc/samba/smb.conf (make a backup) adding or modifying the line lanman auth = yes
4) restart samba with /etc/init.d/samba restart (in my Ubuntu works like that)
5) check the password of the user that you use in your SMS.smb with this command: pdbedit -w username -d0 If you see something like this

username:1002:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:ADE C9EDC3A6A794D691E6DFAFCFAEE85:[U
> ]:LCT-481B6630:
With lots of XX you must re-add the user to smbpasswd. Retype the password.

6) Retype pdbedit -w username -d0 . Now the X's are transformed in Hex codes.

In my case this was enough to work. In my SMS.smb the user is written alone. If this solution don't work you could try two different things for the username in this file.

username
or
username@nameofserver (the same used in the archive SMS.smb)
or
xxx.xxx.xxx.xxxusername (the x are the ip address of the server, yes without @)


Obviously the samba guys changed this default because is more unsecure. But if you stayed with this settings for years, I don't think that I would a problem maintain that configuration.

The best solution would be that the sms access samba shares with the "modern" system. Obviously I don't think that this is a priority.

Sorry for that big explanation, but I had serious problems trying to fix this simple question and I want that other people can find the solution.