NWLoginToFileServer(3nw)

NWLoginToFileServer -- attempts to log an object in to the specified NetWare server

Synopsis

   #include <nwserver.h> 
   #include <nwbindry.h> 
   or 
   #include <nwcalls.h> 
    
   NWCCODE N_API NWLoginToFileServer 
     (NWCONN_HANDLE   conn, 
      pnstr8          objName, 
      nuint16         objType, 
      pnstr8          password);

Description

The parameters are as follows:

conn: (IN) Specifies the NetWare server connection handle.
objName: (IN) Points to the bindery object name of the object logging in to the NetWare server object name.
objType: (IN) Specifies the Bindery object type of the object logging in to the NetWare server.
password: (IN) Points to the password of the bindery object logging in to the NetWare server. If no password is required, pass in a zero-length string.

Return values

0x0000: SUCCESSFUL
0x8800: ALREADY_ATTACHED
0x8801: INVALID_CONNECTION
0x8996: SERVER_OUT_OF_MEMORY
0x89C1: LOGIN_DENIED_NO_ACCOUNT_BALANCE
0x89C2: LOGIN_DENIED_NO_CREDIT
0x89C5: INTRUDER_DETECTION_LOCK
0x89D9: ERR_MAX_SERVERS
0x89DA: UNAUTHORIZED_LOGIN_TIME
0x89DB: UNAUTHORIZED_LOGIN_STATION
0x89DC: ACCOUNT_DISABLED
0x89DE: PASSWORD_HAS_EXPIRED_NO_GRACE
0x89DF: PASSWORD_EXPIRED
0x89FE: BINDERY_LOCKED
0x89FF: NO_SUCH_OBJECT_OR_BAD_PASSWORD

Notices

If a Directory Services attachment exists, NWLoginToFileServer fails with 0x8800.

Before calling NWLoginToFileServer, call NWGetConnectionStatus and check CONNECTION_NDS. If it is set, NWLoginToFileServer cannot be used to log in. NWDetachFromFileServer will also be prevented from being called. Call Directory Services functions to continue the operation.

If the encryption key is not available, it attempts an unencrypted login. If the key is available, the password is encrypted and an encrypted login is attempted.

NWLoginToFileServer performs only the login, not the attach. Clients must be previously attached to call NWLoginToFileServer. Attaching to a NetWare server is not the same as logging in. A workstation attaches to a NetWare server to obtain a connection number. The workstation can then log in to the NetWare server using that connection number. NWLoginToFileServer does not, however, interpret the login script.

Valid Bindery object types for OT_ constants follow:

   OT_WILD                   0xFFFF 
   OT_UNKNOWN                0x0000 
   OT_USER                   0x0100 
   OT_USER_GROUP             0x0200 
   OT_PRINT_QUEUE            0x0300 
   OT_FILE_SERVER            0x0400 
   OT_JOB_SERVER             0x0500 
   OT_GATEWAY                0x0600 
   OT_PRINT_SERVER           0x0700 
   OT_ARCHIVE_QUEUE          0x0800 
   OT_ARCHIVE_SERVER         0x0900 
   OT_JOB_QUEUE              0x0A00 
   OT_ADMINISTRATION         0x0B00 
   OT_NAS_SNA_GATEWAY        0x2100 
   OT_REMOTE_BRIDGE_SERVER   0x2600 
   OT_TCPIP_GATEWAY          0x2700

Extended bindery object types follow:

   OT_TIME_SYNCHRONIZATION_SERVER   0x2D00 
   OT_ARCHIVE_SERVER_DYNAMIC_SAP    0x2E00 
   OT_ADVERTISING_PRINT_SERVER      0x4700 
   OT_PRINT_QUEUE_USER              0x5300

Services

File Server Environment

NCP calls

0x2222 23 24: Keyed Object Login
0x2222 23 53: Get Bindery Object ID