Penguin
Diff: SambaErrorMessages
EditPageHistoryDiffInfoLikePages

Differences between version 16 and predecessor to the previous major change of SambaErrorMessages.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 16 Last edited on Monday, June 26, 2006 12:50:15 pm by DanielLawson Revert
Older page: version 15 Last edited on Monday, March 13, 2006 1:51:02 pm by ChrisLucas Revert
@@ -3,8 +3,14 @@
  
 Samba 2.2, affects all users. This error message can occur if the permissions on your login script are incorrect. 
  
 Samba 3.0alpha, affects one machine only. Not really a Samba issue, as much as that type of problem classifed as [PEBKAC]. Check that your "domain" field in the login prompt is actually correct and doesn't, for example, contain extra spaces after the domain name. "Foo" is slightly different to "Foo ". 
+  
+!! Cannot change password - "Permission denied" error  
+!! smbd/chgpasswd.c:findpty(73): findpty: Unable to create master/slave pty pair  
+  
+Make sure that /dev/pts is mounted properly. This will vary depending on your server distribution  
+  
  
 !!Password has expired 
 This normally means your password has expired. However, it may not always be obvious why.. 
  
@@ -19,8 +25,11 @@
 I have a Samba 3.0.1 PDC setup, authenticating with tdbsam. When I exported to XML, erased the database, and imported from the database, suddenly all my passwords had expired, with a kick date at the beginning of Unix time - somewhere in 1970. I had to recreate all of the accounts. So beware of using the XML format as a backup of your password database until this bug is corrected. 
  
 !!Check the user account status 
 Use the command <tt>pdbedit username -c "~[X ]"</tt> to set password expiry off for the user. 
+  
+!!Account disabled  
+If an account is locked after too many failed login attempts, use <tt>pdbedit username -z</tt> to unlock the account.  
  
 !! smbclient -L host says 'protocol negotiation failed' 
 Check that the host you are trying to connect to has its loopback interface (lo) correctly configured and up