Cause 1 | The machine and cable are not properly connected. |
Remedy | Confirm that the machine is connected to the network using the correct cable, and then restart the machine. (See "Connecting the Machine to a Computer or Network.") |
Cause 2 | [Confirm Network Connection Set. Changes] is set to 'On', although the machine is not connected to a network. |
Remedy | Set [Confirm Network Connection Set. Changes] to 'Off'. |
Cause 1 | Because the IP address cannot be obtained automatically via DHCP, RARP, or BOOTP, [IP Address] in <IP Address Settings> (in the IPv4 Settings) is set to '0.0.0.0'. | ||
Remedy | See "TCP/IPv4 Settings" to specify the correct IPv4 address. | ||
Cause 2 | '0.0.0.0' is set as a static IPv4 address in [IP Address] of <IP Address Settings> (in the IPv4 Settings). | ||
Remedy | See "TCP/IPv4 Settings" to specify the correct IPv4 address. | ||
Cause 3 | The IPv6 addresses are not properly set up. | ||
Remedy | Check the following: Confirm that the settings for the addresses (<Use Stateless Address>, <Use Manual Address>, or <Use DHCPv6>) are set to 'On'. If you are using a stateless address or DHCPv6, confirm that addresses can be obtained. If addresses cannot be obtained, check the settings of the router or DHCPv6 server.
| ||
Cause 4 | The IP address of the DNS server is not correct. | ||
Remedy | See "TCP/IPv4 Settings" or "TCP/IPv6 Settings" to check the IP address of the DNS server. | ||
Cause 5 | Sending could not be performed due to a lack of resources in the TCP/IP protocol stack. | ||
Remedy | See "TCP/IPv4 Settings" or "TCP/IPv6 Settings" to specify the correct IPv4/IPv6 address. |
Cause 1 | The WebDAV server does not support TLS encrypted communication. |
Remedy | Specify the TLS settings required for your environment on the WebDAV server. |
Cause 2 | The proxy server does not support TLS encrypted communication. |
Remedy | If the WebDAV client is connected to the Internet via a proxy server, set the proxy server to use TLS. |
Cause 1 | An error occurred in the WebDAV server or proxy server. |
Remedy | Check the following: Check the settings for the WebDAV server. Check the settings of the proxy server. |
Cause 2 | External access to the target files or directories was denied. |
Remedy | Check the following: Check the settings for the WebDAV server. See "Specifying Destinations" to confirm the settings for a recipient address. |
Cause 3 | The WebDAV server is busy because of heavy access. |
Remedy | Try sending again later. |
Cause 4 | Sending files in chunks is not allowed. |
Remedy | Press [Off] for [Use Divided Chunk Send for WebDAV TX] in [Send] in [Function Settings] (Settings/Registration). (See "Dividing Data Into Chunks When Sending with WebDAV.") |
Cause 5 | The size of the sent data is too large. |
Remedy | Confirm the size of the sent data. |
Cause 6 | The specified URI (host name and folder path specified as the recipient address) is too long. |
Remedy | See "Specifying Destinations" to confirm the full path for the HTTP server entered in [Host Name] and the WebDAV folder path entered in [Folder Path] as the recipient address. |
Cause 1 | The machine tried to access the destination without using a proxy server, but it was necessary to access via a proxy server. |
Remedy | Check the following: Check the settings for the WebDAV server. Confirm the proxy server settings. (See step 12 in "Settings Common to TCP/IPv4 and TCP/IPv6.") |
Cause 2 | Access to the destination was denied. |
Remedy | Check the settings for the WebDAV server. |
Cause 3 | The machine tried to access the destination via a proxy server without using TLS encrypted communication. |
Remedy | Press [Off] for [Use Divided Chunk Send for WebDAV TX] in [Send] in [Function Settings] (Settings/Registration). (See "Dividing Data Into Chunks When Sending with WebDAV.") |
Cause 4 | The proxy server failed to communicate with the upstream server. |
Remedy | Check the following: Check the settings for the WebDAV server. Check the settings of the proxy server. |
Cause 5 | According to the request from the WebDAV client, the HTTP protocol version which is not supported by the WebDAV server is used. |
Remedy | Check the settings for the WebDAV server. |
Cause 6 | The disk space on the WebDAV server was insufficient to process the request from the WebDAV client. |
Remedy | Free up sufficient disk space on the WebDAV server. |
Cause | Proxy server authentication failed. |
Remedy | See step 12 in "Settings Common to TCP/IPv4 and TCP/IPv6" to confirm the settings of the proxy server. |
Cause 1 | The name specified for the SMB server is identical to the name of a computer or printer registered in the WINS database, when <WINS Resolution> for [WINS Settings] is set to 'On'. |
Remedy | Check whether the name specified in [Server Name] for [SMB Server Settings] is identical to the name of a computer or printer registered in the WINS database. For information on SMB server and WINS resolution settings, see "SMB and WINS Settings." |
Cause 2 | The name specified for the SMB server is identical to the name of a computer or printer that belongs to the same workgroup as this machine. |
Remedy | Check whether the name specified in [Server Name] for [SMB Server Settings] is identical to the name of a computer or printer in the workgroup specified in [Workgroup Name]. For information on SMB server and workgroup settings, see "SMB and WINS Settings." |
Cause | The same IPv4 address that is set to this machine already exists on the same network. |
Remedy | See "TCP/IPv4 Settings" to change the IP address of this machine not to be duplicated with the IP addresses which are set to the other devices. |
Cause | The key pair or server certificate to use has not been registered. |
Remedy | It is necessary to register a key pair and server certificate in order to perform encrypted TLS communication. See "Generating a Key Pair and Server Certificate" or "Registering a Key Pair File and Server Certificate File Installed from a Computer" to register a key pair. |
Cause | The key you are trying to erase is currently being used for encrypted TLS communication or used for the Restrict Receiving for Each Function mode in the device information delivery. |
Remedy | Cancel all TLS settings and encrypted TLS communication. Set all settings for [Restrict Receiving for Each Function] in Device Information Delivery Settings to 'On.' For details, see "Specifying Device Information Delivery Settings." |
Cause | The key you are trying to erase is currently being used for encrypted TLS communication or used for the Restrict Receiving for Each Function mode in the device information delivery. |
Remedy | Cancel all TLS settings and encrypted TLS communication. Set all settings for [Restrict Receiving for Each Function] in Device Information Delivery Settings to 'On.' For details, see "Specifying Device Information Delivery Settings." |
Cause | You are trying to register a key pair file which uses an unsupported encryption algorithm. |
Remedy | Register key pair file which uses a supported encryption algorithm. (See "Registering a Key Pair File and Server Certificate File Installed from a Computer.") |
Cause | The certificate is invalid. |
Remedy | Reinstall the valid certificate. |
Cause | The certificate is invalid. |
Remedy | Reinstall the valid certificate. |
Cause 1 | The certificate has expired. |
Remedy | Confirm the expiration date for the certificate. If it has expired, register a certificate which has not expired. |
Cause 2 | The date and time of the machine is not set correctly. (It is set to a future date and time.) |
Remedy | Confirm that the date and time of the machine is set correctly. |
Cause | The CA certificate which has issued the certificate could not be found. |
Remedy | If you want to verify the certificate, register the CA certificate which issued it. |
Cause | The certificate is listed on the CRL (Certificate Revocation Lists). |
Remedy | Install a new certificate. |
Cause | The CRL (Certificate Revocation List) is corrupt, or uses an unsupported signature algorithm. |
Remedy | Register a valid CRL. |
Cause 1 | The start date of validity for the CRL (Certificate Revocation List) is set to a future date. |
Remedy | Confirm the start date of validity for the CRL. If it is set to a future date, use the CRL after it becomes valid. |
Cause 2 | The date and time of this machine is not set correctly. (It is set to a future date and time.) |
Remedy | Confirm that the date and time of the machine is set correctly. |
Cause | The CRL (Certificate Revocation List) could not be verified on the machine. |
Remedy | Register the CRL. |
Cause | The certificate has expired. |
Remedy | Confirm the expiration date for the certificate. |
Cause 1 | Access to the user certificate was denied when sending a PDF or XPS file with a user signature. |
Remedy | See "Confirming a Key Pair and User Certificate" to confirm the user certificate settings. |
Cause 2 | Access to the device certificate was denied when sending a PDF or XPS file with a device signature. |
Remedy | See "Setting/Confirming a Key Pair and Device Certificate" to confirm the device certificate settings. |
Cause | The correct client authentication information (the key pair and certificate, user name and password, and the CA certificate) is not set. |
Remedy | Confirm the set authentication method and authentication information (the key pair and certificate, user name and password, and CA certificate). |
Cause | The password has expired. |
Remedy | Set a new password. |
Cause | The specified authentication method of the machine does not match the authentication method of the RADIUS server. |
Remedy | Confirm whether the authentication method specified for the machine and the authentication method specified for the RADIUS server match, and specify the correct authentication method if necessary. |
Cause | The server certificate sent from the RADIUS server has expired. |
Remedy | Confirm the expiration date for the server certificate of the RADIUS server. |
Cause | An error occurred when verifying the server certificate sent from the RADIUS server using the CA certificate. |
Remedy | Confirm the contents of the server certificate of the RADIUS server, as well as the CA certification registered on the machine. |
Cause | The machine failed to analyze the server certificate sent from the RADIUS server. |
Remedy | Confirm the server certificate contents of the RADIUS server. |
Cause | An error occurred when communicating with the authenticator. |
Remedy | Confirm the authenticator (LAN switch) settings, as well as the RADIUS server settings. |