Ricoh IM C530FB User Guide - Page 240

Check that Realm Name, KDC Server Name, Domain Name are specified correctly

Page 240 highlights

8. Troubleshooting • 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] 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] 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. *3 For Kerberos authentication, check the following: • Check that "Realm Name", "KDC Server Name", "Domain Name" are specified correctly in [Settings] [System Settings] [Settings for Administrator] [Authentication/Charge] [Administrator Authentication/User Authentication/App Auth.] [Register/Change/Delete Realm]. Enter "Realm Name" in upper case. • Configure the setting so that the difference in time between the clocks on KDC and device is less than five minutes. The clock on the machine can be adjusted in [Settings] [System Settings] [Date/Time/Timer] [Date/Time] [Set Time]. • Kerberos authentication fails if auto-obtaining of KDC in Windows authentication fails. When autoobtaining cannot be activated, switch to manual. *4 For LDAP settings, check the following: • Check whether the LDAP server is correctly specified in [Settings] [System Settings] [Settings for Administrator] [Authentication/Charge] [Administrator Authentication/User Authentication/App Auth.] [User Authentication Management] [Custom Authentication] and Login Name Attribute is registered correctly. • Select the server in [Settings] [System Settings] [Settings for Administrator] [Authentication/Charge] [Administrator Authentication/User Authentication/App Auth.] [Register/Change/Delete LDAP Server], press [Register/Change] and set "Authentication" to [Kerberos Authentication], and then execute [Connection Test]. • If the connection test fails, check whether [Domain Name Configuration] and [DNS Configuration] are specified correctly on [Settings] [System Settings] [Network/Interface]. 238

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288

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] 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] 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.
*3 For Kerberos authentication, check the following:
Check that "Realm Name", "KDC Server Name", "Domain Name" are specified correctly in
[Settings]
[System Settings]
[Settings for Administrator]
[Authentication/Charge]
[Administrator Authentication/User Authentication/App Auth.]
[Register/Change/Delete
Realm]. Enter "Realm Name" in upper case.
Configure the setting so that the difference in time between the clocks on KDC and device is less
than five minutes. The clock on the machine can be adjusted in [Settings]
[System Settings]
[Date/Time/Timer]
[Date/Time]
[Set Time].
Kerberos authentication fails if auto-obtaining of KDC in Windows authentication fails. When auto-
obtaining cannot be activated, switch to manual.
*4 For LDAP settings, check the following:
Check whether the LDAP server is correctly specified in [Settings]
[System Settings]
[Settings
for Administrator]
[Authentication/Charge]
[Administrator Authentication/User
Authentication/App Auth.]
[User Authentication Management]
[Custom Authentication] and
Login Name Attribute is registered correctly.
Select the server in [Settings]
[System Settings]
[Settings for Administrator]
[Authentication/Charge]
[Administrator Authentication/User Authentication/App Auth.]
[Register/Change/Delete LDAP Server], press [Register/Change] and set “Authentication” to
[Kerberos Authentication], and then execute [Connection Test].
If the connection test fails, check whether [Domain Name Configuration] and [DNS Configuration]
are specified correctly on [Settings]
[System Settings]
[Network/Interface].
8. Troubleshooting
238