AIX Open Source

 View Only
Expand all | Collapse all

SAMBA prompts for Useid and Password after upgrade to AIX 7200-05-04-2220 from 7100-05-05-1939

  • 1.  SAMBA prompts for Useid and Password after upgrade to AIX 7200-05-04-2220 from 7100-05-05-1939

    Posted Tue November 29, 2022 01:27 AM
    Edited by Ayappan P Wed November 30, 2022 05:36 AM
    After upgrade to AIX 7200-05-04-2220 from 7100-05-05-1939 SAMBA 4.14.4 now prompts for userid and password from Windows 10 and Windows 11 clients attempting to map a drive. This was not required by SAMBA before the upgrade. Two other systems that have AIX 7.2 upgrades with SAMBA 4.14.4 are functioning correctly and do not prompt for userid and password.. The method used to perform the upgrades for all 3 systems was the same (NIM Alternate Disk Migration), Also, the smb.conf on all 3 systems is the same. In the log I see the following failure:

    [2022/11/28 16:48:30.181656, 1] ../../source3/librpc/crypto/gse.c:666(gse_get_server_auth_token)
    gss_accept_sec_context failed with [ Miscellaneous failure (see text): Failed to find cifs/xxxx@YYYYY.COM(kvno 4) in keytab MEMORY:cifs_srv_keytab (aes256-cts-hmac-sha1-96)]

    [global]
    workgroup = ZZZ
    realm = YYYYY.COM
    interfaces = 10.150.129.6
    netbios name = xxxx
    security = ADS
    log file = /var/samba/log/log.%m
    log level = 3 passdb:5 auth:5
    wins server = corp-inm-dc2.inmar.com
    password server = corp-inm-dc2.inmar.com
    socket address = 10.150.129.6
    server min protocol = SMB2
    server signing = mandatory
    create mask = 0666
    follow symlinks = yes
    unix extensions = no



    (the xxxx, YYYYY and ZZZ are redactions of the actual system name for security reasons)


    Any assistance would be greatly appreciated!


    ------------------------------
    Philip Cunio
    ------------------------------


  • 2.  RE: SAMBA prompts for Useid and Password after upgrade to AIX 7200-05-04-2220 from 7100-05-05-1939

    Posted Thu December 01, 2022 07:50 AM
    From the log message , looks like it has something to do with keytab. Check whether the Kerberos ticket got expired or check whether having "winbind refresh tickets = Yes" in smb.conf helps.

    ------------------------------
    Ayappan P
    ------------------------------

    Original Message