Lexmark MS517 Embedded Web Server Administrator s Guide - Page 72
Cannot find realm on card in the Kerberos configuration file
View all Lexmark MS517 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 72 highlights
Troubleshooting 72 Make sure that Port 88 is not blocked by a firewall Port 88 must be opened between the printer and the KDC for authentication to work. User realm not found in the Kerberos configuration file Make sure that the Windows Domain is specified in the Kerberos settings 1 From the Embedded Web Server, click Settings > Apps > Apps Management > Smart Card Authentication > Configure. 2 Under Simple Kerberos Setup, add the WindowsTM domain in lowercase to the Domain setting. For example, if the Domain setting is mil,.mil and the Windows domain is x.y.z, then change the Domain setting to mil,.mil,x.y.z. 3 If you are using a krb5.conf file, then add an entry to the domain_realm section. Map the lowercase Windows Domain to the uppercase realm (similar to the existing mapping for the "mil" domain). Cannot find realm on card in the Kerberos configuration file This error occurs during smart card login. Upload a Kerberos configuration file and make sure that the realm has been added to the file The Smart Card Authentication settings do not support multiple Kerberos Realm entries. If multiple realms are needed, then create and upload a krbf5.conf file containing the needed realms. If you are already using a Kerberos configuration file, then make sure that the missing realm is added to the file correctly. Client is unknown This error indicates that the KDC being used to authenticate the user does not recognize the User Principal Name specified in the error message. Make sure that the Domain Controller information is correct 1 From the Embedded Web Server, click Settings > Apps > Apps Management > Smart Card Authentication > Configure. 2 For Simple Kerberos Setup, make sure that the IP address or host name of the Domain Controller is correct. 3 If you are using a Kerberos configuration file, then make sure that the Domain Controller entry is correct. Login does not respond at "Getting User Info" For information on LDAP‑related issues, see"LDAP troubleshooting" on page 73.