Oh, if it's not a samba bug, then great! I should probably explain how I got here, though, since I think I may not be the only person.
1) The password-nanny in provision (or whatever it's calling) is very hard to satisfy, so instead of using a simple password for testing I ended up omitting --adminpass and letting provision generate the password. 2) But there seemed to be some kind of BASH escape character in many of the auto-generated passwords, because pasting the password onto the end of smbclient //localhost/netlogon -d 5 -Uadministrator% in my PuTTY window would cause the smbclient logon to fail and bash to spit back about half the password with 'command not found'. Rather than digging into what bash was doing, an (apparently) easy workaround was just to omit the % and give the password interactively. 3) When I saw smbclient //localhost/netlogon -d 5 -Uadministrator fail despite getting the correct password, it was natural to assume that something was wrong with the samba setup - it's ... not intuitive for smbclient to behave differently depending on whether it was given the identical password interactively or on the command line. And while the HOWTO tells you to give the password on the command line, it doesn't say that giving it interactively won't work. 4) Eventually I cobbled together a password which provision would accept, and which I could pass to smbclient either interactively or in the command line. But by this time I 'knew' there was something wrong with samba's install/provision, so I was running smbclient with -d to try and find out why it was sometimes failing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976137 Title: samba4 testing with smbclient fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/976137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
