session setup failed: NT_STATUS_LOGON_FAILURE

[hack3rcon]

Hello.
I'm using Debian 8.9 x64 and it is updated. when I use "smbclient" then I got "session setup failed: NT_STATUS_LOGON_FAILURE" error.

Code: Select all

$ smbclient -L \\172.30.11.51 -U username\\domain
Enter username\domain's password:
session setup failed: NT_STATUS_LOGON_FAILURE


How can I solve it?

Thank you.

[debiman]

and none of these was of any help?
please elaborate.

[hack3rcon]

and none of these was of any help?
please elaborate.

I guess here is a wrong place for you. Don't show me search engine. When I ask a question here then its mean I searched and not take any result.

[dilberts_left_nut]

You must supply correct credentials.
That error is from your windows machine, rejecting what you have supplied.

[kopper]

I guess here is a wrong place for you. Don't show me search engine. When I ask a question here then its mean I searched and not take any result.

How rude of him to assume you didn't do your research before creating this thread.

Maybe tell us what have you tried already? Maybe tell what/why suggestions you have researched do not work for you? Maybe share us your configuration? Has it worked before or has it never worked? Does it work on other machines or with other users? Have you added user to Samba? Are you sure you're typing your password correctly? Do you like apples more than bananas?

Or would you like people here to attempt to guess what you already haven't found out from search engines?

EDIT: Typos.

[hack3rcon]

I guess here is a wrong place for you. Don't show me search engine. When I ask a question here then its mean I searched and not take any result.

How rude of him to assume you didn't do your research before creating this thread.

Maybe tell us what have you tried already? Maybe tell what/why suggestions you have researched do not work for you? Maybe share us your configuration? Has it worked before or has it never worked? Does it work on other machines or with other users? Have you added user to Samba? Are you sure you're typing your password correctly? Do you like apples more than bananas?

Or would you like people here to attempt to guess what you already haven't found out from search engines?

EDIT: Typos.

I searched "session setup failed: NT_STATUS_LOGON_FAILURE" in Google and did suggestions that I saw but not matter. For example "https://askubuntu.com/questions/109507/smbclient-getting-nt-status-logon-failure-connecting-to-windows-box" or "http://linux-training.be/storage/ch22.html" or "https://serverfault.com/questions/266903/samba-session-setup-failed-nt-status-logon-failure".
My "smb.conf" is:

Code: Select all

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# 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 most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# 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]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = mydomain.xyz
   name resolve order = host wins bcast
 
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# 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

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

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

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# 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 sever" 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

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using. 
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe. 
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe. 
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# 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
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

[homes]
   comment = Home Directories
   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin


[kopper]

I searched "session setup failed: NT_STATUS_LOGON_FAILURE" in Google and did suggestions that I saw but not matter. For example "https://askubuntu.com/questions/109507/smbclient-getting-nt-status-logon-failure-connecting-to-windows-box" or "http://linux-training.be/storage/ch22.html" or "https://serverfault.com/questions/266903/samba-session-setup-failed-nt-status-logon-failure".

Like dln already replied, error message has to do with wrong credentials. To be absolutely clear, before getting into your smb.conf answer these.

1) Are you trying to access shared folder on Windows machine? Same than in this thread of yours? viewtopic.php?f=5&t=134290
2a) If yes, you have little use for samba server on your Debian. Configure your credentials on your Windows machine and look for answers on how to configure Samba on Windows server. I refuse to believe your problem of wrongly configured credentials is as unique as you make it to be.
2b) If not, answer the rest of the questions. Unless you're trolling, which it very much seems like.

[debiman]

I refuse to believe your problem of wrongly configured credentials is as unique as you make it to be.

well put.

If not, answer the rest of the questions. Unless you're trolling, which it very much seems like.

it is a form of trolling i guess.
you can look up this user at LQ; they've been doing pretty much the same over there for years. But LQ have a strict policy about staying polite, helpful and on topic, which makes it hard for people to give hackercon the spanking they deserve.
not that this user is getting more help there, but they seem to get some sense of being entitled to just go on and on and on asking question after question, ignoring requests for more detail or own research, sometimes providing a morsel of detail after a dozen posts or so, etc. etc...
it is a form of trolling i guess.

[dasein]

it is a form of trolling i guess.

Maybe let's just call it what it is: lying.

This OP has a long history of not being able to configure samba correctly. Instead of learning what he needs to learn, he posts here and expects to be spoonfed. When he gets pushback, he simply lies.

As kopper so correctly implies, anyone who has actually searched can say "When I tried X based on <URL>, Y happened." In such cases, both X and Y are specific

But people who have not searched have to resort to pasting random URLs from the "first 10" hits and then claim "[I] did suggestions that I saw but not matter"

It's a sad commentary that some people find it morally acceptable to lie to strangers in order to obtain gratis help under fraudulent pretenses.

[hack3rcon]

I searched "session setup failed: NT_STATUS_LOGON_FAILURE" in Google and did suggestions that I saw but not matter. For example "https://askubuntu.com/questions/109507/smbclient-getting-nt-status-logon-failure-connecting-to-windows-box" or "http://linux-training.be/storage/ch22.html" or "https://serverfault.com/questions/266903/samba-session-setup-failed-nt-status-logon-failure".

Like dln already replied, error message has to do with wrong credentials. To be absolutely clear, before getting into your smb.conf answer these.

1) Are you trying to access shared folder on Windows machine? Same than in this thread of yours? viewtopic.php?f=5&t=134290
2a) If yes, you have little use for samba server on your Debian. Configure your credentials on your Windows machine and look for answers on how to configure Samba on Windows server. I refuse to believe your problem of wrongly configured credentials is as unique as you make it to be.
2b) If not, answer the rest of the questions. Unless you're trolling, which it very much seems like.

[hack3rcon]

I searched "session setup failed: NT_STATUS_LOGON_FAILURE" in Google and did suggestions that I saw but not matter. For example "https://askubuntu.com/questions/109507/smbclient-getting-nt-status-logon-failure-connecting-to-windows-box" or "http://linux-training.be/storage/ch22.html" or "https://serverfault.com/questions/266903/samba-session-setup-failed-nt-status-logon-failure".

Like dln already replied, error message has to do with wrong credentials. To be absolutely clear, before getting into your smb.conf answer these.

1) Are you trying to access shared folder on Windows machine? Same than in this thread of yours? viewtopic.php?f=5&t=134290
2a) If yes, you have little use for samba server on your Debian. Configure your credentials on your Windows machine and look for answers on how to configure Samba on Windows server. I refuse to believe your problem of wrongly configured credentials is as unique as you make it to be.
2b) If not, answer the rest of the questions. Unless you're trolling, which it very much seems like.

Yes. Configure samba in Windows? I never configured any credentials!!!

[hack3rcon]

I refuse to believe your problem of wrongly configured credentials is as unique as you make it to be.

well put.

If not, answer the rest of the questions. Unless you're trolling, which it very much seems like.

it is a form of trolling i guess.
you can look up this user at LQ; they've been doing pretty much the same over there for years. But LQ have a strict policy about staying polite, helpful and on topic, which makes it hard for people to give hackercon the spanking they deserve.
not that this user is getting more help there, but they seem to get some sense of being entitled to just go on and on and on asking question after question, ignoring requests for more detail or own research, sometimes providing a morsel of detail after a dozen posts or so, etc. etc...
it is a form of trolling i guess.

Are just here for show others your are Live? OK, We understood you are live. here is not a good place for write bullshit text. Please leave it.

[hack3rcon]

it is a form of trolling i guess.

Maybe let's just call it what it is: lying.

This OP has a long history of not being able to configure samba correctly. Instead of learning what he needs to learn, he posts here and expects to be spoonfed. When he gets pushback, he simply lies.

As kopper so correctly implies, anyone who has actually searched can say "When I tried X based on <URL>, Y happened." In such cases, both X and Y are specific

But people who have not searched have to resort to pasting random URLs from the "first 10" hits and then claim "[I] did suggestions that I saw but not matter"

It's a sad commentary that some people find it morally acceptable to lie to strangers in order to obtain gratis help under fraudulent pretenses.

I don't know why you and your friends are here for show me...
I bet you can't fix this problem. I searched but most of problems that are fixed was for Ubuntu not debian.