I have some problems with my Samba Server in connection with the SMS Player on my PS2. Before I use Samba on Suse 9.0, last days I install suse 11.0 and start the new samba with the old config file. everithing runs windows clients can connect to the new domain all released works. Only my PS2 cant connect. The username and the password is correct if i connect anonymously I can see the folders but i cant go inside i need a login.
can somebody help me?
my smb.conf is:
pumukel.lipton Domain Controler Settings
[global]
load printers = no
netbios name = pumukel
socket options = TCP_NODELAY
logon script = %U.bat
logon path = \%L\pro-%U%U
workgroup = lipton
os level = 20
username map = /etc/samba/smbusers
encrypt passwords = yes
time server = yes
hosts allow = 192.168.13.
security = user
wins support = true
domain logons = yes
[netlogon]
path = /users/
browseable = no
force directory mode = 400
allow hosts = 192.168.
writeable = yes
create mode = 400
directory mode = 400
force create mode = 400
write list = @admin
>
> I have some problems with my Samba Server in connection with the SMS
> Player on my PS2. Before I use Samba on Suse 9.0, last days I install
> suse 11.0 and start the new samba with the old config file. everithing
> runs windows clients can connect to the new domain all released works.
> Only my PS2 cant connect. The username and the password is correct if i
> connect anonymously I can see the folders but i cant go inside i need a
> login.
>
> can somebody help me?
>
> my smb.conf is:
>
> # pumukel.lipton Domain Controler Settings
>
>
>
> [global]
> load printers = no
> netbios name = pumukel
> socket options = TCP_NODELAY
> logon script = %U.bat
> logon path = \%L\pro-%U%U
> workgroup = lipton
> os level = 20
> username map = /etc/samba/smbusers
> encrypt passwords = yes
> time server = yes
> hosts allow = 192.168.13.
> security = user
> wins support = true
> domain logons = yes
>
>
>
> [netlogon]
> path = /users/
> browseable = no
> force directory mode = 400
> allow hosts = 192.168.
> writeable = yes
> create mode = 400
> directory mode = 400
> force create mode = 400
> write list = @admin
>
> # Profil Ordner
> [pro-%U]
> path = /users/
> browseable = no
> force directory mode = 700
> allow hosts = 192.168.
> writeable = yes
> create mode = 700
> directory mode = 700
> force create mode = 700
>
> [ps2]
> path = /mldonkey
> user = ps2
> valid users = ps2
> write list = ps2
> force directory mode = 440
> create mode = 440
> force create mode = 440
> directory mode = 440
> browseable = yes
>
>
> thanks for help
>
>
Have you added your user & password to the samba password file? If not,
execute as root:
smbpasswd -a <UserName>
and supply a password when requested.
The UserName must be a valid Linux user name but the password does not need
to be.
Alternatively, change permissions on the PS2 share to give “Others” read
access.
> fio2100 wrote:
>
>>
>> I have some problems with my Samba Server in connection with the SMS
>> Player on my PS2. Before I use Samba on Suse 9.0, last days I install
>> suse 11.0 and start the new samba with the old config file. everithing
>> runs windows clients can connect to the new domain all released works.
>> Only my PS2 cant connect. The username and the password is correct if i
>> connect anonymously I can see the folders but i cant go inside i need a
>> login.
<snip PV>
>>
>>
>> thanks for help
>>
>>
> Have you added your user & password to the samba password file? If not,
> execute as root:
>
> smbpasswd -a <UserName>
>
> and supply a password when requested.
>
> The UserName must be a valid Linux user name but the password does not
> need to be.
>
> Alternatively, change permissions on the PS2 share to give “Others” read
> access.
fio;
One additional thought. I have no idea how sophisticated a PS2 is, it is
possible that it uses older Lanman method of sending passwords. So if you
have added the user/password with smbpasswd and it still does not work; try
adding (as root)
lanman auth = yes
to your /etc/samba/smb.conf.
If this still does not work, remove the above, Lanman is not very secure.
Keep in mind that I am 65+ and, as such, know almost nothing about PS2s.
My only experience is getting my grand-daughter’s PSP to access the
Internet. (As an aside, a PSP is way to small for someone of my age.)
first a ps2 is a playstation 2 in the first versions you can install a network card and with some tricks you can use it like a pc.
now to my problem. i have added all users on the server the domain contoler runs and all win clients can connect. all rights are setted good i have everything tested.
with lanman auth = yes it does not run. also login error.
>
> i habe some informations vom error log of smb.
>
> [2008/07/27 17:42:53, 0] lib/util_sock.c:matchname(1669)
> matchname: host name/address mismatch: 192.168.13.10 != localhost
> [2008/07/27 17:42:53, 0] lib/util_sock.c:get_peer_name(1790)
> Matchname failed on localhost 192.168.13.10
> [2008/07/27 17:43:49, 0] lib/util_sock.c:matchname(1669)
> matchname: host name/address mismatch: 192.168.13.18 != localhost
> [2008/07/27 17:43:49, 0] lib/util_sock.c:get_peer_name(1790)
> Matchname failed on localhost 192.168.13.18
> [2008/07/27 17:44:32, 0] lib/util_sock.c:matchname(1669)
> matchname: host name/address mismatch: 192.168.13.10 != localhost
> [2008/07/27 17:44:32, 0] lib/util_sock.c:get_peer_name(1790)
> Matchname failed on localhost 192.168.13.10
>
> i dont know what that has to tell me.
>
>
fio;
Just which machines do these IP’s belong to? For testing at least, comment
out all the “hosts allow”. What is the user name being supplied by the
PS2? If you have not added the PS2 to the domain, and I’m not sure you
can, you probably need to allow guest users. Do you really need a Domain
versus a simple Workgroup?
In the logs you provided, I do not even see an attempt by the PS2 to log in.
>
> first a ps2 is a playstation 2 in the first versions you can install a
> network card and with some tricks you can use it like a pc.
>
> now to my problem. i have added all users on the server the domain
> contoler runs and all win clients can connect. all rights are setted
> good i have everything tested.
>
> with lanman auth = yes it does not run. also login error.
>
>
Did you restart samba after the change?
If you can not get the PS2 to login, allowing guest access to the share PS2
and setting permissions as I suggested, should allow your game access. (For
this to work you also need “map to guest = Bad User” in the global
section.)
Thats not a problem like no user added wrong rights or something like no restarting server i have checked all the simple thinks i thing thats a autification problem maybe the old samba accept some kind of autentification that the new one do not accept.
The IP form the ps2 is 192.168.13.10 I have tested it with many users and the domain accept access from clients who dont are in the domain. so that cant be the problem. Thats the think why a simple workgroup will not solve the problem. the ps2 is only one client of the network i need the domain and i need the ps2 to play avi’s directly from the server on my tv screen.
the option “map to guest = Bad User” i will test later. i report the result.
thanks for all help and i hope the problem will be solved.
>
> Thats not a problem like no user added wrong rights or something like no
> restarting server i have checked all the simple thinks i thing thats a
> autification problem maybe the old samba accept some kind of
> autentification that the new one do not accept.
>
> The IP form the ps2 is 192.168.13.10 I have tested it with many users
> and the domain accept access from clients who dont are in the domain.
> so that cant be the problem. Thats the think why a simple workgroup
> will not solve the problem. the ps2 is only one client of the network i
> need the domain and i need the ps2 to play avi’s directly from the
> server on my tv screen.
>
> the option “map to guest = Bad User” i will test later. i report the
> result.
Be sure to add guest ok = Yes to the PS2 share.
>
> thanks for all help and i hope the problem will be solved.
>
>
You have hosts allow set in multiple places, but not are all are the same
subnet, I think that explains the errors in your logs, not sure though.
This probably has nothing to do with your PS2, but the logs do show some
configuration problem.
If you increase your log level for authorization you should see your PS2 try
to login.
In your smb.conf try:
log level = 1 auth:3
or just
log level = 3
Then in var/log/samba/log.smbd, you can see what is failing. Once you have
this solved, be sure to remove the above. Otherwise your logs will get big
real fast. If you see nothing at log level 3 you could try for full
debugging, log level 10. (At 10 logs get extremely large and it is hard to
spot just what is wrong because of the size.)
The reason I think lanman may yet prove to be the answer, is that it is the
style of the older DOS Win9x passwords. I’m not sure SONY would spend a
lot of time on enabling NT1. Of course they may be using some SAMBA
derivative.
>
> The subnet is not the problem all network clients had the subnet
> 255.255.255.0 the ps2 too.
The host allow statement in your shares has 192.168. but the global is
192.168.13. If you have the global hosts allow, you do not need it in the
shares. Some day this is going to bite you in the south end when your
going north.
>
> but i have put the loglevel 3 and now i found that:
>
> [2008/07/30 11:43:19, 3] libsmb/ntlm_check.c:ntlm_password_check(370)
> ntlm_password_check: Lanman passwords NOT PERMITTED for user fio
> [2008/07/30 11:43:19, 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 fio
> [2008/07/30 11:43:19, 3]
<snip by PV>
> Server exit (normal exit)
>
> and spacaly this: Lanman passwords NOT PERMITTED for user fio how i can
> change a user to be permitted for lanman auth.
>
>
To allow lanman logins. Add this,as root, to your /etc/samba/smb.conf
Global section:
lanman auth = yes
You must now restart samba so that it reads the configuration file. In a
terminal window su to root and issue the command:
rcsmb restart
You will have solved your login problem. As far as I know, you can not do
this on a per user or per share basis. Either you allow lanman logins or
you do not!
I see you are trying to login as fio, after you allow lanman logins, fio
will not be able to access the ps2 share. The valid user is ps2 not fio. I
do not think username does what you think it does. Look at the manual for
this and for valid users.
For now try:
[ps2]
path = /mldonkey
user = ps2
valid users = ps2
write list = ps2
force directory mode = 440
create mode = 440
force create mode = 440
directory mode = 440
guest ok = yes
browseable = yes
You can add the ones I’ve commented out after you get it working and remove
the guest ok, add/remove them one at a time until it breaks, then figure
out why.
In addition to this for testing purposes, add to your Global section
map to guest = Bad User
Remember that any changes to /etc/samba/smb.conf will not take place until
smbd is restarted!
Thanks for all help. The problem was simple form the wild testing I change the pw once time with webmin because i want to test with no pw and webmin saves the password wrong. now I improve it. lenman auth was the hole time on.
so for the future my config files:
smb.conf (on suse 11.0)
[global]
load printers = no
netbios name = pumukel
socket options = TCP_NODELAY
logon script = %U.bat
logon path = \%L\pro-%U%U
workgroup = lipton
os level = 20
username map = /etc/samba/smbusers
encrypt passwords = yes
time server = yes
hosts allow = 192.168.13.
security = user
wins support = true
domain logons = yes
lanman auth = Yes
client lanman auth = Yes
[ps2]
path = /mldonkey
user = ps2
valid users = ps2
write list = ps2
force directory mode = 440
create mode = 440
force create mode = 440
directory mode = 440
browseable = yes
writeable = no
and the sms.smb on the ps2
192.168.13.11
pumukel
ps2
ps2
password
meens:
ip from samba server
hostname from samba server
hostname from ps2
username
password