Nmas Error 1660
Favorite Rating: -1660 Error is reported to CIFS service on OES using NMAS Login Method(cifslinlsm)This document (7009224) is provided subject to the disclaimer at the end of this document. Environment Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3Novell Open Enterprise Server 11 (OES 11) Linux Support Pack 1Novell Open Enterprise Server 11 (OES 11) Linux Support Pack 2 Novell Common Internet File System (CIFS) Novell Modular Authentication Service(NMAS) Situation When a user tries to login against CIFS on OES in the cifs.log a -1660 error will be logged.On the OES server the NMAS Login Method (cifslinlsm) has been defined. Resolution Novell CIFS on OES uses an NMAS Login Method for user authentication.The NMAS method libraries for CIFS are ( these must be synced to the server holding the replica of a user):32-bit: /var/opt/novell/eDirectory/data/nmas-methods/CIFSLINLSM64-bit: /var/opt/novell/eDirectory/data/nmas-methods/CIFSLINLSM_X64 To verify the CIFS login method libraries on a server, perform the following actions:Check existence of the library on a server in the path specified above.The following command should return a line with the library method name: # lsof -p `pgrep ndsd` | grep CIFSLINLSM[_X64]The login method has to be synced manually if any of the above fails.CIFS login methods can be verified and synced to a server using either ndstrace or iMonitor tool.Please use the following steps:Using ndstrace:Run backlinker to sync the login methods to local security:# ndstraceNDSTrace:set ndstrace=nodebugNDSTrace: dstrace tags blnkNDSTrace: set ndstrace=*B (This may take a while to complete depending on the tree size)NDSTrace: quitRestart eDirectory service (not mandatory) # rcndsd restartVerify if CIFS login works from a Windows/Linux workstation by mounting a CIFS share.using iMonitor:Log in to iMonitor, https://IPAddress:8030/nds , and select tree at the top.Go to Security(Entry Record)->Authorized Login Methods->cifslinlsmCheck for the Flags of sasLoginServerMethodLinux and sasLoginServerMethodLinuxX64 Attribute. These flags have to be Present, otherwise sync the attribute using ndstrace method.Another thing that you can try is to delete the /var/opt/novell/eDirectory/data/nmas-methods/CIFSLINLSM_64or CIFSLINLSMfile andrestart eDir. (rcndsd restart)The login method will be read into memory from the local copy of the security container in eDir and the CIFSLINLSM_64 or CIFSLNLSM file will be recreated. Cause The problem is usually related to the local eDir process not being able to read the security conta
fact Novell NetWare 5.1 Novell NetWare 6.0 Novell NetWare 6.5 Native File Access for Windows Native File Access for Macintosh note There is one more possible scenario when this error may be returned. When connecting to a CIFS/AFP server that does not hold a replica of the user requesting a connection,NMAS on that server will find anotherserverrunning NMAS that does hold a replica of that user. Once it finds that other NMAS server it will request the remote NMAS server to resolve and authenticate the user. In order to do that successfully the remote NMAS server must be able to load the login method from DS. In the event that the remote NMAS server is a https://www.novell.com/support/kb/doc.php?id=7009224 non-NetWare server, such as eDirectoryfor Windows, the login will fail with a -1660 Login Sequence Invalid error. This will happen because the Windows server, although running eDirectory and NMAS, cannot load the lsmcifs.nlm. This issue is being addressed in a new release of NMAS that is expected to be available in the NetWare 6.5 SP2 time frame. One other thing to check that will cause this error is to make sure the NW 6.5 http://support.novell.com/docs/Tids/Solutions/10091495.html server isNOT running CIFS version 1.x, or in otherwords NW 6.5 should not be running CIFS modules from NW 5.1/6.0. If the NW 6.5 server is running CIFS modules from NW 5.1/6.0 (unsupported) AND the only login method loaded in the tree is lsmcifs2.nlm then attempts to login will fail with a -1660 error. The reason for that is that the NW 6.0 modules will be looking for the lsmcifs login method and it will not exist...thus the "invalid login method" error. CIFS modules from NW 6.0 are unaware and unable to use the lsmcifs2.nlm (Windows Native File Access login method for NW 6.5) and will never ask to use it. Running CIFS version 1.x modules on a NW 6.5 server is unsupported and not recommended although it may work it will also definitely cause UNICODE problems. fix When failing to login to a NetWare server via CIFS or AFP (NFAP) with a bad username or password error, one of the first steps in troubleshooting the issue is to obtain an NMAS log (nmasmon * SYS:\ETC\NMAS.txt trunc). That log will envariably let you know what the exact error is. This document is dedicated to troubleshooting problems that can cause the server to return an NMAS error -1660. -1660 0xFFFFF984 NMAS_E_SEQUENCE_NOT_FOUND The specified NMAS logi
Favorite Rating: -1660 http://www.novell.com/support/kb/doc.php?id=7015624 NMAS error trying to use Forgotten Password / Challenge ResponseThis document (7015624) is provided subject to the disclaimer at the end https://groups.google.com/d/topic/novell.support.netware.client.winnt-2x-xp/OotAy8HVRKY of this document. Environment NetIQ eDirectory 8.8.x Situation When when using the forgotten password portal a message is received that the nmas error challenge response questions have not been setup. However, they have previously been populated.Enabling a LDAP / NMAS trace showed the following -1660 NMAS error on the Challenge Response login sequence.1145546496 NMAS: [2014/08/28 19:24:18.203] 19923014: Login Sequence Challenge Response not valid.1145546496 NMAS: [2014/08/28 19:24:18.203] nmas error 1660 19923014: Login Sequence NDS is valid.1145546496 NMAS: [2014/08/28 19:24:18.203] 19923014: Login Sequence Simple Password is valid.1145546496 NMAS: [2014/08/28 19:24:18.203] 19923014: Login Sequence DIGEST-MD5 is valid.1145546496 NMAS: [2014/08/28 19:24:18.203] 19923014: Login Sequence GSSAPI is valid.1145546496 NMAS: [2014/08/28 19:24:18.203] 19923014: Login Sequence cifslinlsm is valid.1145546496 NMAS: [2014/08/28 19:24:18.203] 19923014: ERROR: -1660 Client can not do requested login sequence "Challenge Response"1145546496 NMAS: [2014/08/28 19:24:18.203] 19923014: ERROR: -1660 CanDo1145546496 NMAS: [2014/08/28 19:24:18.203] 19923014: Password Failure Time Attribute value count: 11494079232 LDAP: [2014/08/28 19:24:18.203] DoBind on connection 0x19bb2e001494079232 LDAP: [2014/08/28 19:24:18.203] Bind (cont) name:NULL, version:3, authentication:NMAS_LOGIN1145546496 NMAS: [2014/08/28 19:24:18.209] 19923014: Failed login delay 3 seconds1081337600 LDAP: [2014/08/28 19:24:18.733] DoUnbind on connection 0x197320001138943744 LDAP: [2014/08/28 19:24:18.734] Monitor 0x43e2e700 found connection 0x19732000 ending TLS sessionThe Challenge Response Login Method and Sequence was prese
GoogleВойтиСкрытые поляПоиск групп или сообщений