Cause
|
The document could not be sent because there was insufficient memory available.
|
Remedy 1
|
Lower the resolution or divide the document into two or more parts, and then try sending the document again.
|
Remedy 2
|
Check the TX Document and RX Document memory, and delete unnecessary documents and documents with errors from memory. (See "Checking the Detailed Information for/Deleting a File in the Memory RX Inbox.")
|
Remedy 3
|
If this problem occurs frequently, contact your local authorized Canon dealer.
|
Cause
|
You cannot browse the network. There is a lack of TCP/IP resources because a series of documents have just been sent, or are continuously being sent via FTP or Windows (SMB).
|
Remedy
|
Wait for a while, and then try browsing again.
|
Cause
|
This machine is not set with an IP address.
|
Remedy
|
Specify the IP Address Settings, turn the machine's main power OFF, and then back ON. (See "Protocol Settings.")
|
Cause
|
The specified server settings are incorrect, or the server is not turned ON. Alternatively, the machine's TCP/IP resources may be low.
|
Remedy
|
Wait for a while, and then try browsing again. If there is still no response from the server, try selecting another server.
|
Cause
|
You have exceeded the maximum number of subdirectory levels allowed.
|
Remedy
|
You cannot specify the current subdirectory. Specify another destination.
|
Cause 1
|
The server was not running when you tried to send.
|
Remedy
|
Make sure that the server is ON, and check the destination.
|
Cause 2
|
The network connection was lost when you tried to send. (The server may be unable to connect to the network, or it may have lost the connection.)
|
Remedy
|
Check the status of the network.
|
Cause 3
|
A TCP/IP error occurred when you tried to send an e-mail message or I-fax.
|
Remedy
|
Check that the network cables and connectors are properly connected.
|
Cause
|
The machine's TCP/IP connection is not operating.
|
Remedy
|
Check the IP Address Settings (IP Address, DHCP, RARP, BOOTP) in [TCP/IP Settings]. (See "Protocol Settings.")
|
Cause 1
|
The IP address that the machine should connect to cannot be determined.
|
Remedy 1
|
Check the DNS settings. (See "Protocol Settings.")
|
Remedy 2
|
Check whether the DNS data settings are correct on the DNS server.
|
Cause 2
|
If <Authentication Information> in Register LDAP Server is set to [Use (Security Auth.)] for the LDAP server, the machine will not be able to determine the host name.
|
Remedy
|
Check the DNS settings for TCP/IP. (See "Protocol Settings.")
|
Cause
|
The machine cannot connect to the specified IP address/port.
|
Remedy 1
|
Check the IP Gateway Address Settings in [TCP/IP Settings]. (See "Protocol Settings.")
|
Remedy 2
|
Check the Server Address and Port Number in Register LDAP Server. (See "LDAP Server Settings.")
|
Remedy 3
|
Check whether the LDAP server is operating normally.
|
Remedy 4
|
If <Authentication Information> is set to [Use (Security Auth.)] for the LDAP server, check whether UDP (User Datagram Protocol) packages are blocked by the filter.
|
Cause 1
|
The user name or password is incorrect when setting Authentication Information for the LDAP server to [Use] or [Use (Security Auth.)].
|
Remedy
|
Check the user name and password in Register LDAP Server. (See "LDAP Server Settings.")
|
Cause 2
|
The domain name is incorrect when setting Authentication Information for the LDAP server to [Use (Security Auth.)].
|
Remedy
|
Check the domain name in Register LDAP Server. (See "LDAP Server Settings.")
|
Cause
|
The search could not be completed within the specified time.
|
Remedy
|
Increase the time setting for Search Timeout in Register LDAP Server. (See "LDAP Server Settings.")
|
Cause
|
The number of addresses that meet the search criteria exceeds the specified maximum number of addresses to search.
|
Remedy 1
|
Narrow down the search criteria, and then search again.
|
Remedy 2
|
Increase the maximum number of addresses to search. (See "LDAP Server Settings.")
|
Cause 1
|
"\" is used in the search criteria.
|
Remedy
|
Remove "\" from the search criteria, and then search again.
|
Cause 2
|
The combination of characters used in the search do not constitute acceptable search criteria.
There is an unequal number of "(" and ")".
"*" is not placed within "( )".
|
Remedy
|
Make sure that the characters for the search criteria form a legitimate combination, and then search again.
|
Cause 3
|
Characters other than ASCII Code (0x20-0x7E) are being used, when [LDAP Server Version and Character Code] is set to [ver.2 (JIS)].
|
Remedy
|
Omit characters that cannot be used, and then search again.
|
Cause
|
Although version 3 is selected as the server LDAP version number in Register LDAP Server, the LDAP server is running on version 2.
|
Remedy
|
Set the Server LDAP version and character code to version 2 in Register LDAP Server. (See "LDAP Server Settings.")
|