Problem with Active Directory authentication

Sumit Bose sbose at
Fri Jun 10 08:44:49 UTC 2016

On Wed, Jun 08, 2016 at 07:46:00PM +0000, Kaplan, Andrew H. wrote:
> Hello --
> We are running the 14.04.3 LTS 64-bit release as a virtual machine on a Vmware appliance. The goal of the installation is to create a Samba server that utilizes Active Directory authentication. To that end I utilized the following procedure:
> Afterwards, I referenced the following documentation to confirm that all configuration files had the appropriate entries:

The sssd-users list
might be more appropriate for your question.

As a general comment, the PAM configuration is important here. Please
check the system logs which PAM module was consulted during the login
attempt and which cause the rejection.



> The problem is the following: I am unable to log into the server from the console or via SSH using my Active Directory user account. The syntax that I use when doing an SSH connection is the following:
> ssh -v -l <username>@<domainname> <fully qualified domain name>
> The output that was generated is the following:
> OpenSSH_6.0p1 Debian-4, OpenSSL 1.0.1e 11 Feb 2013
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: Applying options for *
> debug1: Connecting to <fully qualified domain name> [<ip address>] port 22.
> debug1: Connection established.
> debug1: identity file /home/knoppix/.ssh/id_rsa type -1
> debug1: identity file /home/knoppix/.ssh/id_rsa-cert type -1
> debug1: identity file /home/knoppix/.ssh/id_dsa type -1
> debug1: identity file /home/knoppix/.ssh/id_dsa-cert type -1
> debug1: identity file /home/knoppix/.ssh/id_ecdsa type -1
> debug1: identity file /home/knoppix/.ssh/id_ecdsa-cert type -1
> debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7
> debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7 pat OpenSSH*
> debug1: Enabling compatibility mode for protocol 2.0
> debug1: Local version string SSH-2.0-OpenSSH_6.0p1 Debian-4
> debug1: SSH2_MSG_KEXINIT sent
> debug1: SSH2_MSG_KEXINIT received
> debug1: kex: server->client aes128-ctr hmac-md5 none
> debug1: kex: client->server aes128-ctr hmac-md5 none
> debug1: sending SSH2_MSG_KEX_ECDH_INIT
> debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
> debug1: Server host key: ECDSA ec:09:c1:bc:d0:11:f3:8c:45:3f:dd:3a:96:ba:2a:17
> debug1: Host '<fully qualified domain name>' is known and matches the ECDSA host key.
> debug1: Found key in /home/knoppix/.ssh/known_hosts:29
> debug1: ssh_ecdsa_verify: signature correct
> debug1: SSH2_MSG_NEWKEYS sent
> debug1: expecting SSH2_MSG_NEWKEYS
> debug1: SSH2_MSG_NEWKEYS received
> debug1: Roaming not allowed by server
> debug1: SSH2_MSG_SERVICE_ACCEPT received
> debug1: Authentications that can continue: publickey,password
> debug1: Next authentication method: publickey
> debug1: Trying private key: /home/knoppix/.ssh/id_rsa
> debug1: Trying private key: /home/knoppix/.ssh/id_dsa
> debug1: Trying private key: /home/knoppix/.ssh/id_ecdsa
> debug1: Next authentication method: password
> <username>@<domainname>@<fully qualified domain name>'s password:
> Connection closed by <ip address>
> Does anyone have thoughts on this?
> Thanks.
> The information in this e-mail is intended only for the person to whom it is
> addressed. If you believe this e-mail was sent to you in error and the e-mail
> contains patient information, please contact the Partners Compliance HelpLine at
> . If the e-mail was sent to you in error
> but does not contain patient information, please contact the sender and properly
> dispose of the e-mail.

More information about the samba-technical mailing list