CIFS does not continue to run after starting

  • 7009704
  • 07-Nov-2011
  • 15-Aug-2015

Environment

Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3
Novell Open Enterprise Server 11 (OES 11) Linux
Novell CIFS

Situation

After installing CIFS onto a functioning OES2sp3 server, it would appear that novell-cifs started but checking its status indicated it was "unused" (or not running). 

The /var/log/cifs/cifs.log indicated:

Oct 31 06:00:02 svr01 CIFS: EVENT: ENTRY:  ********** CIFS server started ************
Oct 31 06:00:03 svr01 CIFS[12961]: WARNING: ENTRY: Auditing interface not initialized.
Oct 31 06:00:07 svr01 CIFS[12961]: ERROR: ENTRY: DDCLogin() failed Error: -223
Oct 31 06:00:16 svr01 CIFS[12961]: ERROR: ENTRY: DDCLogin() failed Error: -222
Oct 31 06:00:25 svr01 CIFS[12961]: ERROR: ENTRY: DDCLogin() failed Error: -222
Oct 31 06:00:34 svr01 CIFS[12961]: ERROR: ENTRY: DDCLogin() failed Error: -197
Oct 31 06:00:44 svr01 CIFS[12961]: ERROR: ENTRY: DDCLogin() failed Error: -197
Oct 31 06:00:53 svr01 CIFS[12961]: ERROR: ENTRY: DDCLogin() failed Error: -197
Oct 31 06:00:53 svr01 CIFS[12961]: ERROR: ENTRY: CIFSNDSResolveName failed with error = -197
Oct 31 06:00:53 svr01 CIFS[12961]: ERROR: ENTRY: Schema not extended. Errorcode  =  -197


Resolution

In iManager, for the proxy user check that:
  • the password has not expired
  • the password is not forced to be changed
  • the number of grace logins have not been depleted

Additional Information

The error messages returned indicate:

-223 = password expired
As it indicates, the password has expired and needs to be changed or "unexpired" (see resolution above).
NOTE: If you only see -223 errors, it is an indication that the password is out of password policy (age wise) within eDirectory.  The easiest way to get it up-to-date/back-into-sync with miCASA, is to force a reset of the proxy user password (see Change Proxy Passwords Automatically).

-222 = bad password
The credentials that CIFS was trying to authenticate with are invalid.  An expired password will cause this to occur as well as having bad credentials.  One way to check/resolve is above.

-197 = login lockout

If the resolution section above does not fix it, you likely have a password mismatch between your eDirectory object and the proxy user (stored in CASA).  A relatively easy way to get them into sync is to reconfigure CIFS with a new proxy user.  See Section 10.4.1 "CIFS Is Not Starting"  for further info on reconfiguring proxy user.


Alternative solution(s) include:

- increasing the expiration date of the password on the common proxy ID, and changing it by logging in as root and running:
     /opt/novell/proxymgmt/bin/change_proxy_pwd.sh -A yes

Feedback service temporarily unavailable. For content questions or problems, please contact Support.