Differences between version 10 and predecessor to the previous major change of SambaErrorMessages.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 10 | Last edited on Thursday, August 25, 2005 1:31:09 pm | by CraigBox | Revert |
| Older page: | version 6 | Last edited on Wednesday, June 23, 2004 11:24:47 pm | by RaulYo | Revert |
@@ -1,27 +1,38 @@
-!
!!Incorrect Parameter
+!!Incorrect Parameter
When logging into a Samba 2.2 or 3.0 PDC from a windows desktop, you can sometimes get the error message "Incorrect Parameter". We've found two reasons for this:
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
-
+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 ".
-!
!!Password has expired
+!!Password has expired
This normally means your password has expired. However, it may not always be obvious why..
-I have a Samba 3.0a PDC setup, authenticating out of LDAP. My LDAP entities have posixAccount, shadowAccount, and
-
+I have a Samba 3.0a PDC setup, authenticating out of LDAP. My LDAP entities have posixAccount, shadowAccount, and sambaAccount objetclasses, amongst others. If you have 'obey pam restrictions = yes' in your smb.conf (version 3.x and later 2.2 only) then if pam thinks your shadow passwords have expired, samba will insist you need to change your password - even if your samba password expiry is correct.
suggested solutions:
-# Tell samba
to not obey pam restrictions
-# reset
your unix
password at the same time you reset your samba
password
-# disable
forced password changes in pam.
+# Tell Samba
to not obey pam restrictions
+# Reset
your [UNIX]
password at the same time you reset your Samba
password
+# Disable
forced password changes in pam(7)
.
!!Another password has expired problem
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
-Using
the command:
-
pdbedit username -c "[
[X ]"
-This
set that the password of username should not expire
.
+Use
the command <tt>
pdbedit username -c "~
[X ]"</tt> to
set password expiry off for the user.
+
+!! 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
+
+!!make_server_info_info3: pdb_init_sam failed!
+
+According to Google this is a very common error, usually overlooked on the Samba mailing list. I gather, from reading the few posts that do have replies, that this error could be due to various things; the reason I was getting it was that I hadn't included the following in /etc/nsswitch.conf:
+
+ passwd: compat winbind
+ group: compat winbind
+
+[This post|http://lists.samba.org/archive/samba/2005-January/098470.html] helped a bit.
+
+!!error code was NT_STATUS_PIPE_NOT_AVAILABLE (0xc00000ac)
+
+If you get this error running wbinfo -t, try setting <tt>client schannel = no</tt> in your smb.conf
.
