Yes, the connector could be building a charge and looping it back. I've
seen that happen.
>Here is another questions for you. (I am very glad finally someone
>answered my questions. I have sent questions a few times, with no
>response.
Note that the mailing lists are not official support channels so anything
posted here may never get an answer.
><omited ...>
>Received IPCP_CONFIGURE_REQUEST on port S22 of 18 bytes containing:
>xx xx xx xx xx xx xx
>
>Sending IPCP_CONFIGURE_ACK to port S22 of 22 bytes containing:
>xx xx xx xx
>
>LCP IPCP Open
>Connection Succeeded
>Received LCP_PROTOCOL_REJECT on port S22 of 750 bytes containing:
>xx xx xx xx xx xx xx xx xx xx xx xx
>
>Received LCP_PROTOCOL_REJECT on port S22 of 750 bytes containing:
>xx xx xx xx xx xx xx xx xx xx xx xx
The Aterm seems to be misconfigured, or perhaps buggy.
I'd take the full debug dump an run it through the debug script on the
website. It may help pinpoint what it is trying to negotiate.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588