Re: windows can not access samba share - username case senitivity issue [xenial]
On Wed, Feb 17, 2016 at 11:52 PM, Doug Smythies wrote: > > I now think the case sensitivity thing was a red herring. > I now believe my issues stem from there no longer being a > libpam-smbpass package (that was definitely present and > installed with samba in earlier server daily ISO's). > Anyway, I gave up on "classic primary domain controller" > and changed to "standalone server" and it works fine, so far. Removed upstream: https://lists.samba.org/archive/samba-cvs/2015-October/111473.html -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
RE: windows can not access samba share - username case senitivity issue [xenial]
Hi all, I now think the case sensitivity thing was a red herring. I now believe my issues stem from there no longer being a libpam-smbpass package (that was definitely present and installed with samba in earlier server daily ISO's). Anyway, I gave up on "classic primary domain controller" and changed to "standalone server" and it works fine, so far. On 2106.02.16 20:52 Doug Smythies wrote: > Does anyone have some ideas about my samba problems? On 2016.02.06 12:22 Doug Smythies wrote. Thanks for the replies. On 2016.02.06 09:51 Tom H wrote: > On Sat, Feb 6, 2016 at 4:41 PM, Doug Smythies wrote: >> On 2016.02.06 Tom H wrote: >>> On Sat, Feb 6, 2016 at 1:17 AM, Doug Smythies wrote: I have been attempting to make samba work on an Ubuntu amd64 server 16.04 I am building. My windows user account name is "Doug". My Ubuntu user account name is "doug". This appears to be the root issue. On my 14.04 server: check_ntlm_password: authentication for user [Doug] -> [Doug] -> [doug] succeeded On my 16.04 server: check_ntlm_password: sam authentication for user [Doug] FAILED with error NT_STATUS_NO_SUCH_USER check_ntlm_password: Authentication for user [Doug] -> [Doug] FAILED with error NT_STATUS_NO_SUCH_USER >>> >>> Can you logon as "doug" from a Linux box? >> >> I can login as "doug" locally and from other boxes via ssh or whatever. >> If you mean via samba from a different Linux box, then I have never done >> that. > Yes to the latter. > Can you list the shares with: > smbclient -L //smb_srv-ip_address -U doug > Can you log into doug's home share with: > smbclient //smb_srv-ip_address/doug -U doug 1.) from 16.04 server (smythies.com) to 14.04 server (s15.smythies.com): doug@DOUG-64:~$ smbclient -L //s15 -U doug Enter doug's password: Domain=[SHOME] OS=[Unix] Server=[Samba 4.1.6-Ubuntu] Sharename Type Comment - --- IPC$IPC IPC Service (s15 server (Samba, Ubuntu)) share Disk Smythies.com main server share netlogonDisk Network Logon Service homes Disk Home Directories dougDisk Home Directories Domain=[SHOME] OS=[Unix] Server=[Samba 4.1.6-Ubuntu] Server Comment ---- DOUG-64 doug-64 server (Samba, Ubuntu) S15 s15 server (Samba, Ubuntu) WorkgroupMaster ---- SHOMEDOUG-64 2.) from 14.04 server (s15) to 16.04 server (smythies.com): doug@s15:~$ smbclient -L //smythies.com -U doug WARNING: no network interfaces found Enter doug's password: session setup failed: NT_STATUS_LOGON_FAILURE >>> Did you create machine accounts? >> >> Just me, so far. The account "doug" was created during installation. >> And that is the same as my 14.04 test server. >> I have never used the samba username name stuff, and not needing >> to is the whole point of the way I configure samba. > AFAIK, you need machine accounts when you set "domain logons = yes" > because the samba server acts as a DC; and you have both "domain > logons = yes" and the "server role = classic primary domain > controller" set. > > What's the output of "pdbedit -L" on 14.04 and 16.04? Are machine > accounts (ending with "$") listed? 1.) On the 14.04 server (s15.smythies.com) doug@s15:~$ sudo pdbedit -L INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 doing parameter max log size = 1 doing parameter panic action = /usr/share/samba/panic-action %d doing parameter log level = 2 doug:1000:Doug Smythies 2.) On the 16.04 server (smythies.com) doug@DOUG-64:~$ sudo pdbedit -L INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 doing parameter max log size = 1000 doing parameter panic action = /usr/share/samba/panic-action %d doing parameter server role = classic primary domain controller doing parameter security = user doing parameter encrypt passwords = true doing parameter passdb backend = tdbsam doing parameter obey pam restrictions = yes doing parameter unix password sync = yes doing parameter passwd program = /usr/bin/passwd %u doing parameter passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . doing parameter pam password change = yes doing pa
RE: windows can not access samba share - username case senitivity issue [xenial]
Does anyone have some ideas about my samba problems? On 2016.02.06 12:22 Doug Smythies wrote. Thanks for the replies. On 2016.02.06 09:51 Tom H wrote: > On Sat, Feb 6, 2016 at 4:41 PM, Doug Smythies wrote: >> On 2016.02.06 Tom H wrote: >>> On Sat, Feb 6, 2016 at 1:17 AM, Doug Smythies wrote: I have been attempting to make samba work on an Ubuntu amd64 server 16.04 I am building. My windows user account name is "Doug". My Ubuntu user account name is "doug". This appears to be the root issue. On my 14.04 server: check_ntlm_password: authentication for user [Doug] -> [Doug] -> [doug] succeeded On my 16.04 server: check_ntlm_password: sam authentication for user [Doug] FAILED with error NT_STATUS_NO_SUCH_USER check_ntlm_password: Authentication for user [Doug] -> [Doug] FAILED with error NT_STATUS_NO_SUCH_USER >>> >>> Can you logon as "doug" from a Linux box? >> >> I can login as "doug" locally and from other boxes via ssh or whatever. >> If you mean via samba from a different Linux box, then I have never done >> that. > Yes to the latter. > Can you list the shares with: > smbclient -L //smb_srv-ip_address -U doug > Can you log into doug's home share with: > smbclient //smb_srv-ip_address/doug -U doug 1.) from 16.04 server (smythies.com) to 14.04 server (s15.smythies.com): doug@DOUG-64:~$ smbclient -L //s15 -U doug Enter doug's password: Domain=[SHOME] OS=[Unix] Server=[Samba 4.1.6-Ubuntu] Sharename Type Comment - --- IPC$IPC IPC Service (s15 server (Samba, Ubuntu)) share Disk Smythies.com main server share netlogonDisk Network Logon Service homes Disk Home Directories dougDisk Home Directories Domain=[SHOME] OS=[Unix] Server=[Samba 4.1.6-Ubuntu] Server Comment ---- DOUG-64 doug-64 server (Samba, Ubuntu) S15 s15 server (Samba, Ubuntu) WorkgroupMaster ---- SHOMEDOUG-64 2.) from 14.04 server (s15) to 16.04 server (smythies.com): doug@s15:~$ smbclient -L //smythies.com -U doug WARNING: no network interfaces found Enter doug's password: session setup failed: NT_STATUS_LOGON_FAILURE >>> Did you create machine accounts? >> >> Just me, so far. The account "doug" was created during installation. >> And that is the same as my 14.04 test server. >> I have never used the samba username name stuff, and not needing >> to is the whole point of the way I configure samba. > AFAIK, you need machine accounts when you set "domain logons = yes" > because the samba server acts as a DC; and you have both "domain > logons = yes" and the "server role = classic primary domain > controller" set. > > What's the output of "pdbedit -L" on 14.04 and 16.04? Are machine > accounts (ending with "$") listed? 1.) On the 14.04 server (s15.smythies.com) doug@s15:~$ sudo pdbedit -L INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 doing parameter max log size = 1 doing parameter panic action = /usr/share/samba/panic-action %d doing parameter log level = 2 doug:1000:Doug Smythies 2.) On the 16.04 server (smythies.com) doug@DOUG-64:~$ sudo pdbedit -L INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 doing parameter max log size = 1000 doing parameter panic action = /usr/share/samba/panic-action %d doing parameter server role = classic primary domain controller doing parameter security = user doing parameter encrypt passwords = true doing parameter passdb backend = tdbsam doing parameter obey pam restrictions = yes doing parameter unix password sync = yes doing parameter passwd program = /usr/bin/passwd %u doing parameter passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . doing parameter pam password change = yes doing parameter username level = 5 doing parameter domain logons = yes doing parameter logon path = \\%N\%U\profile doing parameter logon drive = U: doing parameter logon home = \\%N\%U doing parameter logon script = logon.cmd doing parameter add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u doing parameter domain master = yes doing parameter
RE: windows can not access samba share - username case senitivity issue [xenial]
On 2015.02.06 08:04 Jason Sauders wrote: Thanks for the reply. > One thing to keep in mind is that each samba user must > be a local system user on the box hosting the samba shares. Yes, agreed. > So if you have an Ubuntu box and this Ubuntu box is going to host the > samba shares, and overall you'd like to have a total of 5 samba users, > those 5 samba users must also have a local system account on the Ubuntu > system. Yes, agreed. > Keep in mind if you have 5 Ubuntu system users, but have configured 0 > users for samba, you effectively have 0 users who can access samba. They > are not one in the same and are configured independently (though samba > users require local users to exist to complete the creation process). No. Disagree. As far as I recall, I have never set up separate samba users. > I do not believe the password of Doug on the Windows box has anything to > do with the password of Doug on the Linux box. Yes, but I force them to be the same on my LAN. > I have noticed Windows seemingly tries to use the local user + local > password (local to the Windows box) first as credentials for samba > shares. So if the Windows box is "Doug" with "password123" as the > password to log in to Windows, and you *also* have "Doug" with > "password123" as the samba credentials on the Linux box, the Windows box > will seemingly just "let you in", appearing to use no authentication in > the process, though it actually did authenticate you in that process via > assuming to use the local (to Windows) credentials first. Yes, exactly. And that is what I have been doing for many many years. > The above is of course just my understanding/experience in the past > (which may be gray at this point) of it all. Mine also, because I have had to think about this since as far back as I can remember. Migration from 10.10 to 12.04 to 14.04 all just worked without much (O.K. any) thought. > I encourage other folks > reading this message to correct me if this information isn't correct. Yes, pelase. > Typically I'll add all of my local users to the Ubuntu box first. > Following that, I add them to samba via 'sudo smb passwd -a username'. Yes, I have never done the second step (as far as I recall). Which Is the whole point of the way I have my smb.conf file setup. > Hope this helps! Keep us updated. I will. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
RE: windows can not access samba share - username case senitivity issue [xenial]
Thanks for the replies. On 2016.02.06 09:51 Tom H wrote: > On Sat, Feb 6, 2016 at 4:41 PM, Doug Smythies wrote: >> On 2016.02.06 Tom H wrote: >>> On Sat, Feb 6, 2016 at 1:17 AM, Doug Smythies wrote: I have been attempting to make samba work on an Ubuntu amd64 server 16.04 I am building. My windows user account name is "Doug". My Ubuntu user account name is "doug". This appears to be the root issue. On my 14.04 server: check_ntlm_password: authentication for user [Doug] -> [Doug] -> [doug] succeeded On my 16.04 server: check_ntlm_password: sam authentication for user [Doug] FAILED with error NT_STATUS_NO_SUCH_USER check_ntlm_password: Authentication for user [Doug] -> [Doug] FAILED with error NT_STATUS_NO_SUCH_USER >>> >>> Can you logon as "doug" from a Linux box? >> >> I can login as "doug" locally and from other boxes via ssh or whatever. >> If you mean via samba from a different Linux box, then I have never done >> that. > Yes to the latter. > Can you list the shares with: > smbclient -L //smb_srv-ip_address -U doug > Can you log into doug's home share with: > smbclient //smb_srv-ip_address/doug -U doug 1.) from 16.04 server (smythies.com) to 14.04 server (s15.smythies.com): doug@DOUG-64:~$ smbclient -L //s15 -U doug Enter doug's password: Domain=[SHOME] OS=[Unix] Server=[Samba 4.1.6-Ubuntu] Sharename Type Comment - --- IPC$IPC IPC Service (s15 server (Samba, Ubuntu)) share Disk Smythies.com main server share netlogonDisk Network Logon Service homes Disk Home Directories dougDisk Home Directories Domain=[SHOME] OS=[Unix] Server=[Samba 4.1.6-Ubuntu] Server Comment ---- DOUG-64 doug-64 server (Samba, Ubuntu) S15 s15 server (Samba, Ubuntu) WorkgroupMaster ---- SHOMEDOUG-64 2.) from 14.04 server (s15) to 16.04 server (smythies.com): doug@s15:~$ smbclient -L //smythies.com -U doug WARNING: no network interfaces found Enter doug's password: session setup failed: NT_STATUS_LOGON_FAILURE >>> Did you create machine accounts? >> >> Just me, so far. The account "doug" was created during installation. >> And that is the same as my 14.04 test server. >> I have never used the samba username name stuff, and not needing >> to is the whole point of the way I configure samba. > AFAIK, you need machine accounts when you set "domain logons = yes" > because the samba server acts as a DC; and you have both "domain > logons = yes" and the "server role = classic primary domain > controller" set. > > What's the output of "pdbedit -L" on 14.04 and 16.04? Are machine > accounts (ending with "$") listed? 1.) On the 14.04 server (s15.smythies.com) doug@s15:~$ sudo pdbedit -L INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 doing parameter max log size = 1 doing parameter panic action = /usr/share/samba/panic-action %d doing parameter log level = 2 doug:1000:Doug Smythies 2.) On the 16.04 server (smythies.com) doug@DOUG-64:~$ sudo pdbedit -L INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10 rpc_cli: 10 passdb: 10 sam: 10 auth: 10 winbind: 10 vfs: 10 idmap: 10 quota: 10 acls: 10 locking: 10 msdfs: 10 dmapi: 10 registry: 10 scavenger: 10 dns: 10 ldb: 10 tevent: 10 doing parameter max log size = 1000 doing parameter panic action = /usr/share/samba/panic-action %d doing parameter server role = classic primary domain controller doing parameter security = user doing parameter encrypt passwords = true doing parameter passdb backend = tdbsam doing parameter obey pam restrictions = yes doing parameter unix password sync = yes doing parameter passwd program = /usr/bin/passwd %u doing parameter passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . doing parameter pam password change = yes doing parameter username level = 5 doing parameter domain logons = yes doing parameter logon path = \\%N\%U\profile doing parameter logon drive = U: doing parameter logon home = \\%N\%U doing parameter logon script = logon.cmd doing parameter add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u doing parameter domain master = yes doing parameter template shell = /bin/bash doing parameter usershare max shares = 100 doing parameter usershare
Re: windows can not access samba share - username case senitivity issue [xenial]
On Sat, Feb 6, 2016 at 4:41 PM, Doug Smythies wrote: > On 2016.02.06 Tom H wrote: >> On Sat, Feb 6, 2016 at 1:17 AM, Doug Smythies wrote: >>> I have been attempting to make samba work on an Ubuntu amd64 server 16.04 I >>> am building. >>> My windows user account name is "Doug". My Ubuntu user account name is >>> "doug". This appears to be the root issue. >>> >>> On my 14.04 server: >>> check_ntlm_password: authentication for user [Doug] -> [Doug] -> [doug] >>> succeeded >>> >>> On my 16.04 server: >>> check_ntlm_password: sam authentication for user [Doug] FAILED with error >>> NT_STATUS_NO_SUCH_USER >>> check_ntlm_password: Authentication for user [Doug] -> [Doug] FAILED with >>> error NT_STATUS_NO_SUCH_USER >> >> Can you logon as "doug" from a Linux box? > > I can login as "doug" locally and from other boxes via ssh or whatever. > If you mean via samba from a different Linux box, then I have never done that. Yes to the latter. Can you list the shares with: smbclient -L //smb_srv-ip_address -U doug Can you log into doug's home share with: smbclient //smb_srv-ip_address/doug -U doug >> Did you create machine accounts? > > Just me, so far. The account "doug" was created during installation. > And that is the same as my 14.04 test server. > I have never used the samba username name stuff, and not needing > to is the whole point of the way I configure samba. AFAIK, you need machine accounts when you set "domain logons = yes" because the samba server acts as a DC; and you have both "domain logons = yes" and the "server role = classic primary domain controller" set. What's the output of "pdbedit -L" on 14.04 and 16.04? Are machine accounts (ending with "$") listed? You have "add machine script = ..." in your smb.conf to create a unix machine account automatically if it already has a samba machine account so you must (?) have some. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: windows can not access samba share - username case senitivity issue [xenial]
Hi there, Doug. One thing to keep in mind is that each samba user must be a local system user on the box hosting the samba shares. So if you have an Ubuntu box and this Ubuntu box is going to host the samba shares, and overall you'd like to have a total of 5 samba users, those 5 samba users must also have a local system account on the Ubuntu system. Keep in mind if you have 5 Ubuntu system users, but have configured 0 users for samba, you effectively have 0 users who can access samba. They are not one in the same and are configured independently (though samba users require local users to exist to complete the creation process). I do not believe the password of Doug on the Windows box has anything to do with the password of Doug on the Linux box. It all boils down to the samba password you configured for Doug. Keep in mind you can have Doug on the Linux box with password123 as the password, yet Doug the samba user may have password789 as their actual samba password (which would be used for file sharing connectivity purposes). I have noticed Windows seemingly tries to use the local user + local password (local to the Windows box) first as credentials for samba shares. So if the Windows box is "Doug" with "password123" as the password to log in to Windows, and you *also* have "Doug" with "password123" as the samba credentials on the Linux box, the Windows box will seemingly just "let you in", appearing to use no authentication in the process, though it actually did authenticate you in that process via assuming to use the local (to Windows) credentials first. The above is of course just my understanding/experience in the past (which may be gray at this point) of it all. I encourage other folks reading this message to correct me if this information isn't correct. Typically I'll add all of my local users to the Ubuntu box first. Following that, I add them to samba via 'sudo smb passwd -a username'. You'll notice the prompt say "New SMB Password" following. Since my wife, myself, etc are always using the same user to log in to our NAS (Ubuntu Server 14.04 with samba installed), I'll log in via the file manager and do 1) save password forever, 2) bookmark it, 3) rename it in an obvious fashion and retain it on the left side of the file manager. This creates a 1 click link to hit my NAS in the future. Hope this helps! Keep us updated. -J On 02/06/2016 10:41 AM, Doug Smythies wrote: On 2016.02.06 Tom H wrote: On Sat, Feb 6, 2016 at 1:17 AM, Doug Smythies wrote: I have been attempting to make samba work on an Ubuntu amd64 server 16.04 I am building. My windows user account name is "Doug". My Ubuntu user account name is "doug". This appears to be the root issue. On my 14.04 server: check_ntlm_password: authentication for user [Doug] -> [Doug] -> [doug] succeeded On my 16.04 server: check_ntlm_password: sam authentication for user [Doug] FAILED with error NT_STATUS_NO_SUCH_USER check_ntlm_password: Authentication for user [Doug] -> [Doug] FAILED with error NT_STATUS_NO_SUCH_USER Can you logon as "doug" from a Linux box? I can login as "doug" locally and from other boxes via ssh or whatever. If you mean via samba from a different Linux box, then I have never done that. Did you create machine accounts? Just me, so far. The account "doug" was created during installation. And that is the same as my 14.04 test server. I have never used the samba username name stuff, and not needing to is the whole point of the way I configure samba. ... Doug -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
RE: windows can not access samba share - username case senitivity issue [xenial]
On 2016.02.06 Tom H wrote: > On Sat, Feb 6, 2016 at 1:17 AM, Doug Smythies wrote: >> I have been attempting to make samba work on an Ubuntu amd64 server 16.04 I >> am building. >> My windows user account name is "Doug". My Ubuntu user account name is >> "doug". This appears to be the root issue. >> >> On my 14.04 server: >> check_ntlm_password: authentication for user [Doug] -> [Doug] -> [doug] >> succeeded >> >> On my 16.04 server: >> check_ntlm_password: sam authentication for user [Doug] FAILED with error >> NT_STATUS_NO_SUCH_USER >> check_ntlm_password: Authentication for user [Doug] -> [Doug] FAILED with >> error NT_STATUS_NO_SUCH_USER > Can you logon as "doug" from a Linux box? I can login as "doug" locally and from other boxes via ssh or whatever. If you mean via samba from a different Linux box, then I have never done that. > Did you create machine accounts? Just me, so far. The account "doug" was created during installation. And that is the same as my 14.04 test server. I have never used the samba username name stuff, and not needing to is the whole point of the way I configure samba. ... Doug -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: windows can not access samba share - username case senitivity issue [xenial]
On Sat, Feb 6, 2016 at 1:17 AM, Doug Smythies wrote: > > I have been attempting to make samba work on an Ubuntu amd64 server 16.04 I > am building. > > My windows user account name is "Doug". My Ubuntu user account name is > "doug". This appears to be the root issue. > > On my 14.04 server: > check_ntlm_password: authentication for user [Doug] -> [Doug] -> [doug] > succeeded > > On my 16.04 server: > check_ntlm_password: sam authentication for user [Doug] FAILED with error > NT_STATUS_NO_SUCH_USER > check_ntlm_password: Authentication for user [Doug] -> [Doug] FAILED with > error NT_STATUS_NO_SUCH_USER Can you logon as "doug" from a Linux box? Did you create machine accounts? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
