Ricoh IM C5510A - LDAP Server Unavailable Messages

8. Troubleshooting
278
8
Message
Cause
Solution and reference
"Authentication has
failed."
B/W/L0913-023
Auto-registration of
a user on the server
machine has failed
when
authentication
was performed on
the client machine
using Central
Management.
• Check the network communication
between the client and server
machines.
• Registration cannot be performed
while the address book of the server
machine is being edited.
*1 When obtaining user groups, check the following:
• The user account that can obtain user groups is sAMAccountName (user). Do not use
UserPrincipalName (user@domain.XXX.co.jp) as the user name.
• Check whether the name in "Group" is correctly specified including the case-
sensitivity in [Settings] [System Settings] [Settings for Administrator]
[Authentication/Charge] [Administrator Authentication/User Authentication/App
Auth.] [User Authentication Management] [Windows Authentication].
• Select the user in the address book, press [Edit], and then check that [Unavailable] is
specified for each function under the [User Management / Other] tab [User
Management] [Available Functions / Applications].
• Check whether "Global Scope" is specified as the scope of the group in a property
for the user group created in DC, and the group type specified in "Security". Also
check whether an account is registered to the user group that has been created. If
more than one DC exists, check whether a trust relationship between DCs is
established.
*2 To resolve the domain name, see the following:
• Check whether [Domain Name Configuration] and [DNS Configuration] or [WINS
Configuration] is specified correctly in [Settings] [System Settings]
[Network/Interface].
• Enter the IP address in [Domain Name Configuration] to check the connection. If
authentication can be performed using the IP address, check [DNS Configuration] or
[WINS Configuration] again.
• If authentication by IP address is not possible, check whether LM/NTLM is set to be
denied in the domain controller security policy or domain security policy. Also check
that the port is not closed in the firewall between the device and the domain
controller or in the firewall settings of the domain controller. When the Windows
firewall is enabled, create a new rule that allows communication on port 137 and
port 139 in "Advanced" of the Windows firewall. Open the TCP/IP properties from
the network connection properties, select the "Enable NetBIOS Over TCP/IP" check
box on [Advanced] [WINS] tab, and open port 137.