Version 2.0.0 Page 47
beyond an acceptable range; check the
MFP's date and time.
minutes of each other.
Resolution: Verify the date and time on the MFP; see
section 3.1. Be sure the time zone and daylight
savings time settings are correct.
Kerberos configuration file has not
been uploaded.
Cause: The PKI/AD Authentication solution is
configured to use the MFP Kerberos setup but no
Kerberos file was uploaded.
Resolution: See section 4.1 If the Kerberos settings
are provided in the PKI/AD Authentication are
provided in the settings, uncheck the “Use MFP
Kerberos Setup” checkbox and click apply.
Resolution: If a Kerberos file really needs to be used,
click “Configuration | Security | Kerberos Setup”.
Browse to the Kerberos file and click submit. A
reboot will be required.
The Domain Controller Issuing
Certificate has not been installed.
Cause: No certificate has been installed on the MFP.
Resolution: See section 3.6. If you install the wrong
certificate, the error message on the device will
provide the name of the certificate needed.
The Domain Controller Issuing
Certificate (“name of certificate”) has
not been installed.
Cause: The certificate specified in the error message
is needed to validate the domain controller.
Resolution: See the PKI Pre-Installation Guide for
information on obtaining the certificate. See
section 3.6 for information on installing the
certificate.
The KDC did not respond within the
required time.
Cause: The hostname or IP address of the KDC is not
correct.
Resolution: Verify the hostname or IP address and
check against the value in the PKI/AD
Authentication solution or Kerberos file.
Cause: The KDC is not currently available.
Resolution: Multiple KDCs can be specified in the
PKI/AD Authentication solution or Kerberos file;
this will typically resolve this issue.
Cause: Port 88 is blocked by a firewall.
Resolution: This is the Kerberos Port and is used by
the MFP to communicate with the KDC. The port
must be opened between the MFP and KDC in
order for authentication to work.
User's Realm was not found in the
Kerberos Configuration File.
Cause: This error occurs during a manual login and
indicates the Windows domain is not specified in
the Kerberos Configuration file.
Resolution: If using the PKI/AD Authentication
solution for the Kerberos settings, add the
To Next Page
Loading...
