Fujitsu 6010N Operator's Guide - Page 389

Network Connection Troubleshooting, change the [Link Speed/Duplex Mode] from Auto

Page 389 highlights

8.3 Network Connection Troubleshooting When checking the network connection status of a server by its IP address, the following results are possible. Result "Ping statistics" shows "Lost=0 (0% loss)" "Ping statistics" shows "Lost=4 (100% loss)" "Ping statistics" shows "Lost=N (1 to 99% loss)" "Hardware error" None Action Check that the ping target IP address is correct. If the ping target IP address is correct, refer to "Failure to connect to a server using its IP address" (page 359) for further solutions. There may be a quality problem with the LAN cable. Replace the LAN cable and try again. In "4.6.17 Checking the Network Operating Status" (page 125), change the [Link Speed/Duplex Mode] from "AutoNegotiation" to a fixed mode. The LAN cable may have become disconnected during the Ping test. Check the status of the LAN cable and try again. When checking the network connection status of a server with an FQDN, the following results are possible. Result Action "Ping statistics" shows "Lost=0 (0% loss)" None Troubleshooting "Ping request could not find host xxxxxxxxx. Please check the name and try again." Check that the ping target server name is correct. Check that the DNS server or WINS server settings are correct. If the ping target server name is correct, refer to "Failure to connect to a server by name" (page 361) for further solutions. "Ping statistics" shows Check that the ping target server name is correct. "Lost=4 (100% loss)" In "4.6.17 Checking the Network Operating Status" (page 125), change the [Link Speed/Duplex Mode] from "Auto- "Ping statistics" shows Negotiation" to a fixed mode. There may be a quality problem with the LAN cable. 8 "Lost=N (1 to 99% loss)" Replace the LAN cable and try again. In "4.6.17 Checking the Network Operating Status" (page 125), change the [Link Speed/Duplex Mode] from "AutoNegotiation" to a fixed mode. "Hardware error" The LAN cable may have become disconnected during the Ping test. Check the status of the LAN cable and try again. Network Scanner fi-6010N Operator's Guide 355

  • 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
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452
  • 453
  • 454
  • 455
  • 456
  • 457
  • 458
  • 459
  • 460
  • 461
  • 462
  • 463
  • 464
  • 465
  • 466
  • 467
  • 468
  • 469
  • 470
  • 471
  • 472
  • 473
  • 474
  • 475
  • 476
  • 477
  • 478
  • 479
  • 480
  • 481
  • 482
  • 483
  • 484
  • 485
  • 486
  • 487

8.3 Network Connection Troubleshooting
Network Scanner fi-6010N Operator's Guide
355
Troubleshooting
8
When checking the network connection status of a server by its IP address, the following results
are possible.
When checking the network connection status of a server with an FQDN, the following results are
possible.
Result
Action
"Ping statistics" shows
"Lost=0 (0% loss)"
None
"Ping statistics" shows
"Lost=4 (100% loss)"
Check that the ping target IP address is correct.
If the ping target IP address is correct, refer to
"Failure to
connect to a server using its IP address" (page 359)
for fur-
ther solutions.
"Ping statistics" shows
"Lost=N (1 to 99% loss)"
There may be a quality problem with the LAN cable.
Replace the LAN cable and try again.
In
"4.6.17 Checking the Network Operating Status" (page
125)
, change the [Link Speed/Duplex Mode] from "Auto-
Negotiation" to a fixed mode.
"Hardware error"
The LAN cable may have become disconnected during the
Ping test. Check the status of the LAN cable and try again.
Result
Action
"Ping statistics" shows
"Lost=0 (0% loss)"
None
"Ping request could not find
host xxxxxxxxx. Please
check the name and try
again."
Check that the ping target server name is correct.
Check that the DNS server or WINS server settings are cor-
rect.
If the ping target server name is correct, refer to
"Failure to
connect to a server by name" (page 361)
for further solutions.
"Ping statistics" shows
"Lost=4 (100% loss)"
Check that the ping target server name is correct.
In
"4.6.17 Checking the Network Operating Status" (page
125)
, change the [Link Speed/Duplex Mode] from "Auto-
Negotiation" to a fixed mode.
"Ping statistics" shows
"Lost=N (1 to 99% loss)"
There may be a quality problem with the LAN cable.
Replace the LAN cable and try again.
In
"4.6.17 Checking the Network Operating Status" (page
125)
, change the [Link Speed/Duplex Mode] from "Auto-
Negotiation" to a fixed mode.
"Hardware error"
The LAN cable may have become disconnected during the
Ping test. Check the status of the LAN cable and try again.