Troubleshooting - Canon imageRUNNER 2530 Service Manual

2
Technology > Embedded RDS > Troubleshooting > Troubleshooting

Troubleshooting

Troubleshooting
When the communication test with UGW is NG, trouble shooting is performed according to
the following steps.
No.1 A communication test (COM-TEST) results NG
Causes: Initial settings or network conditions is incomplete.
Remedy1:
1) Check network connections
Is the status indicator LED for the HUB port to which the main unit is connected ON?
YES: Proceed to Step 2).
NO: Check that the network cable is properly connected.
2) Confirm loop back address
a) Settings/ Registration > System Settings > Network Settings > TCP/ IP Settings > IPv4
Settings > PING Command. Input 127.0.0.1, and touch the Start button.
Is the response from the host displayed?
YES: Proceed to Step 3).
NO: There is a possibility that the main unit's network settings are wrong. Check the
details of the IPv4 settings once more.
2 Technology > Embedded RDS > Troubleshooting > Troubleshooting
3) Confirmation from another PC connected to same network.
a) Request the user to ping the main unit from a PC connected to same network.
Does the main unit respond?
4) Confirm DNS connection
a) Settings/ Registration > System Settings > Network Settings > TCP/ IP Settings > IPv4
Settings > DNS Server > DNS Server Address Settings, and note down both the primary
and secondary DNS server addresses.
b) Press Reset key.
c) Settings/ Registration > System Settings > Network Settings > TCP/ IP Settings > IPv4
Settings > PING command. Input the primary DNS server noted down in step a) as the IP
address, and then touch Start.
Is the response from the host displayed?
Is the response from the host displayed?
Remedy2: Troubleshooting using communication log
a) Enter Servicemode > #E-RDS > COM-LOG, and the following communication log will be
F-2-110 F-2-110
displayed. Maximum 5 records are logged.
b) Select a log line and touch OK, then move on to log details.
YES: Proceed to Step 4).
NO: Confirm the details of the main unit's IP address and subnet mask settings.
YES: Proceed to Remedy2.
NO: Input the secondary DNS server noted down in step a) as the IP address, and
then touch Start.
YES: Proceed to Remedy2.
NO: There is a possibility that the DNS server address is wrong. Reconfirm the
address with the user's system administrator.
No:1 Ecode:840F2003
2009 01/09 17:27
*Network is not rea
dy , try later : get
2-78
2-78