Skip to end of metadata
Go to start of metadata


Description:

This document describes possible error messages displayed in LANmonitor of a LANCOM device and their possible cause.


The cause for the failure of PPP negotiation can in most cases be determined by analyzing the error messages. The error messages displayed by a LANCOM router can have the following causes:

  • LCP rejected (0x8000)
    The remote device rejected the PPP link control protocol. There is a serious malfunction in the PPP stack of the remote device.
  • Authentication failed (0x8001)
    The remote device does not support the authentication protocol used. The settings in the LANCOM router and the remote device must match. It may only be possible to establish a connection when authentication is switched off.
  • Authentication request rejected (0x8002)
    The remote device rejected all authentication. A connection can only be established after switching off authentication in the PPP list.
  • PAP rejected (0x8010)
    Although an accepted part of LCP negotiation, the remote device rejected password authentication protocol for authentication. There is a serious malfunction in the PPP stack of the remote device. It may still be possible to establish a connection securely by activating the challenge handshake authentication protocol (CHAP) in the PPP list.
  • PAP Rx timeout (0x8011)
    The remote device failed to begin broadcasting PAP requests to the LANCOM router within the set period of time. This problem can usually be solved by increasing the number of retries.
  • PAP Tx timeout (0x8012)
    The remote device failed to respond to a PAP request from the LANCOM router within the set period of time. This problem can usually be solved by increasing the number of retries.
  • PAP Req incorrect
    The password used by the remote device does not match the password in the PPP list.
  • PAP NAK received (0x8014)
    The error message "PAP NAK received" means password authentification protocol not acknowledged. This means that the Internet service provider's authentication server has received your request (indicating that there is no physical problem), but authentication with the user data held in the router (user name / password) was rejected during PPP negotiation. The cause may be an error when entering user data, account locking by the ISP (Internet service provider), multiple dial-in attempts using the same user data, etc.
  • CHAP rejected
    Although an accepted part of LCP negotiation, the remote device rejected the challenge handshake authentication protocol for authentication. There is a serious malfunction in the PPP stack of the remote device. It may still be possible to establish the connection securely by activating the password authentication protocol (PAP) in the PPP list.
  • CHAP Rx timeout
    The remote device failed to respond to a CHAP challenge from the LANCOM router with a CHAP response within the set period of time. This problem can usually be solved by increasing the number of retries.
  • CHAP Tx timeout
    The remote device failed to respond to a CHAP response from the LANCOM office router within the set period of time. This problem can usually be solved by increasing the number of retries.
  • CHAP Resp incorrect
    The response received from the remote device does not match the expected value. The name and password combination used by both devices does not match. The device name or the key entry in the PPP list must be modified in the LANCOM router.
  • CHAP Fail received
    The remote device rejected the CHAP response from the LANCOM router. The same error occurred as with "CHAP Resp incorrect".
  • CHAP peer ID unknown
    The CHAP request from the remote device contained a peer ID that cannot be resolved in the LANCOM router's PPP table. It could be that the same error occurred as with "CHAP Resp incorrect".
  • IPXCP rejected (0x8030)
    The remote device rejected the IPX control protocol for negotiating the IPX parameters. Either the remote device does not support IPX routing over PPP, or IPX has not been activated for this connection in the remote device. The configuration of the remote device must be checked.
  • IPXCP network incorrect (0x8031)
    The IPX network addresses used for ISDN by both devices do not match. Either the IPX router in the LANCOM router is incorrectly configured, or the IPX router in the remote device.
  • IPXCP network rejected (0x8032)
    The remote device rejected negotiation of the IPX network address for ISDN. The configuration of the remote device must be checked.
  • IPXCP route unknown (0x8030)
    The remote device uses a different routing protocol for IPX than RIP/SAP. The configuration of the remote device must be checked.
  • IPCP rejected (0x8040)
    The remote device rejected the IPX control protocol for negotiating the IP parameters. Either the remote device does not support IP routing over PPP, or IP has not been activated for this connection in the remote device. The configuration of the remote device must be checked.
  • No NCP available (0x80F0)
    It was not possible to activate either IPXCP or IPCP for the connection. The IPX router and the IP router contain no reference to the remote device in their configurations.

Compare the name of the remote device as received by the LANCOM router for the connection (on the CLI or in WEBconfig under LCOS Menu Tree →  Status → Info connection → Peer) with the entries in the routing table of the IP router (under IP router → Routing → IPv4 routing table) and modify them accordingly. Check the settings in the router's layer list under Communication → General). Make sure that the correct entry for your remote device is stored here.