
6.3 Network Connection Troubleshooting
The following outcomes are possible:
Message | Connection | Action | |
status | |||
|
| ||
|
|
| |
System time has been | OK | None | |
successfully synchronized. |
|
| |
|
|
| |
System time synchronization | NG | Try the following: | |
failed. |
| • Check the NTP server name and address settings | |
Sending resync command to |
| for errors. | |
local computer... |
| • Check the network path between to the NTP | |
The computer did not resync |
| server for problems. | |
because no time data was |
| • The NTP server may be busy. Wait a short time | |
available. |
| before trying again to synchronize the system | |
| time. If that does not work, the specified server | ||
|
| ||
System time synchronization |
| ||
| may not be an NTP server, so try a different NTP | ||
failed. |
| server. | |
Sending resync command to |
| • The specified NTP server cannot provide a | |
local computer... |
| trusted date and time. It attempted to acquire the | |
| date and time from a higher level NTP server, | ||
The computer did not resync |
| ||
| but failed. Try a different NTP server or have the | ||
because only stale time data |
| ||
| network administrator investigate. | ||
was available. |
| ||
|
| ||
|
|
| |
System time synchronization | NG | ||
failed. |
| adjust the date/time, and try again. | |
Sending resync command to |
|
| |
local computer... |
|
| |
The computer did not resync |
|
| |
because the required time |
|
| |
change was too big. |
|
| |
|
|
|
Troubleshooting
6
Network Scanner |
| 239 |
| ||
|
|
|