SAMBA:NT_STATUS_LOGON_FAILURE on linux

Tyir · 12-02-2003, 10:56 PM

Ok, I have been trying to get this on my own/using samba documentation/other posts

Trying to get samba to connect my slack9.1 box and win2k

Ok, i can connect to my windows box from linux (using smbclient and nautlius)
On win2k, the box shows up in network neibourhood, if I double-click, says bad username and password, and nothing I put in will connect me..
Sounds normal, right? Here's the funny part
I was goign through the troubleshooing

in thewin2k box, i did ftp server, and was about to connect and go through the linux box
SO the connects are all right it seems
I was doign more troubleshooting tests:
This is on linuxbox:

Code:

robert@MOFETTE:~$ smbclient \\\\BESSIE\\Alias
Password: 
smb: \>

SO i can connect to win2k box!
Now,

Code:

robert@MOFETTE:~$ smbclient \\\\MOFETTE\\Video
Password: 
session setup failed: NT_STATUS_LOGON_FAILURE
robert@MOFETTE:~$

Now, this is me on the linuxbox trying to connect to the linuxbox!
Not sure what this means!

heres my smb.conf

Code:

# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2003/12/02 23:31:59

# Global parameters
[global]
        workgroup = KAPLOW
        server string = Robert
        log file = /var/log/samba.%m
        max log size = 50
        dns proxy = No
        hosts allow = 192.168.
        browsable = yes
        local master = yes

[homes]
        comment = Home Directories
        read only = No

[printers]
        comment = All Printers
        path = /var/spool/samba
        printable = Yes
        browseable = No

[Video]
        comment = Video
        path = /mnt/fatnonvital/Multimedia/Video

Thanks!

binkybuckle · 12-03-2003, 12:08 AM

The smb.conf file you have is extremely basic, it may be worth you while to read the samba how-to collection and man pages available at http://us1.samba.org/samba/docs/

binkybuckle · 12-03-2003, 12:31 AM

Sorry, disregard my last post, I didn't mean to post that yet.

The smb.conf file you have is extremely basic, it may be worth you while to read the samba how-to collection and man pages available at http://us1.samba.org/samba/docs/

when you try to login to a file share on the linux box (even if you are logging in from the linux box) you must provide a valid username and password that is contained on the linuxbox (/etc/passwd). So if you try 'smbclient \\\\MOFETTE\\Video -U <USERNAME>', this might work (I think from memory that samba requires the username to be in capitials but I could be wrong). See if this works. You may not be able to use the root account of the linux box to login by samba.

It always a good idea to set samba up manually (not by SWAT or WEBMIN) the first time. This way it will be easier in the future because you will know what all the configuration settings mean, an example is the absence of the setting 'secuirty = <option>' in your smb.conf.

P.S. Their is a samba forum that is very good, the creators of samba are often actively involved with it, to subscribe goto http://lists.samba.org/ , note: you will recieve over 1000 emails a month by subscribing, a alternative is to post your question by emailing them to samba@lists.samba.org and then goto http://us1.samba.org/samba/archives.html to view any responses.

Tyir · 12-03-2003, 09:46 PM

You were perfectly right!

Someone new to samba should NOT use SWAT
They should write their own, either by following the sample or by help of the forums

SWAT will only confuse and befuddle you...

Thanks again!

zaphraud · 12-22-2003, 11:24 PM

Actually, I think this is a problem with RedHat's recent "security rollup" ''upgrade'' to samba.

I offer as further evidence for this fact, that neither of the two responces noted any errors in the guys config, nor did they suggest a fix other than the standard "RTFM" approach (gee, that helps! not!)

The only clue I've been able to find is a suggestion that the meatballs at RH who released the package changed the name from "Samba" to some absurd string with "security rollup" in the name, and that this name itself violates the standard, thus triggering the error.. I can't validate that since I haven't actually SEEN where you can change the VERSION other than by recompiling the bastard.

Which, I think I am going to do, since I am sick of this error myself. NO ONE SEEMS TO HAVE A FIX.