(ASCEND) Re: Ascend Max to Pipe NAT question

[Daniel <daniel@lynx.net>]

yyy.yyy.yyy.yyy is the NAT address assigned by the Max (in the RADIUS
profile).

Regards,

Daniel


At 09:12 AM 6/23/99 PDT, you wrote:
>LCP looks good
>Name/Password looks good
>IPNCP config is failing - you removed the address contained
>in : >PPPIF-34: IPNCP Opened to yyy.yyy.yyy.yyy
>
>is it to the bogus address or NAT address assigned by the Max?
>
>>PPPIF-34: LCP Opened, local 'max002', remote ''
>>PPPIF-34: _openAuthentication
>>PPPIF-34: pppMpNegUntimeout last 0 layer 1
>>PPPIF-34: Auth Opened
>>PPPIF-34: Remote hostName is ''
>>PPPIF-34: prep MP bundle for
>>PPPIF-34: using profile hostname max002
>>PPPIF-34: authOpenedContinue
>>PPPIF-34: prep MP bundle for
>>PPPIF-34: using profile hostname max002
>>PPPIF-34: new MP bundle
>>PPPIF-34: First channel, MpID 233
>>PPPIF: Assigning vjInfo (B05D9300) and bncpInfo(B0596A40)
>>PPPIF-34: CBCP Opened
>>PPPIF-34: pppMpSendNeg Pkt
>>PPPIF-34: pppMpNegTimeout layer 4
>>PPPIF-34: opening CCP
>>PPPIF-34: pppMpSendNeg Pkt
>>PPPIF-34: pppMpNegTimeout layer 6
>>PPPIF-34: opening IPNCP: xxx.xxx.xxx.xxx -> yyy.yyy.yyy.yyy
>>PPPIF-34: pppMpSendNeg Pkt
>>PPPIF-34: pppMpNegTimeout layer 4
>>PPPIF-34: pppMpNegUntimeout last 0 layer 6
>>PPPIF-34: pppMpNegUntimeout last 0 layer 4
>>PPPIF-34: pppMpSendNeg Pkt
>>PPPIF-34: pppMpSendNeg Pkt
>>PPPIF-34: pppMpNegUntimeout last 0 layer 4
>>PPPIF-34: IPNCP Opened to yyy.yyy.yyy.yyy
>>PPPIF-34: _pppClose called
>>PPPIF-233: pppMpNegUntimeout last 1 layer 0
>>PPPIF-34: cleanup pass
>>
>>Any ideas,
>>
>>Thanks.
>>
>>Daniel
>>
>>
>>
>>At 02:19 PM 6/22/99 PDT, you wrote:
>> >I'd first try building a local connection profile on the max just
>> >for testing purposes, then after I get outbound calls from the max
>> >to the pipe working successfully I'd offload it RADIUS. Sort of a
>> >divide and conquer method. Also on the max I'd go into diagnostics
>> >mode (F1 key, d for diagnostics) and type pppif, then you'd know
>> >at what stage PPP negotiation is failing.
>> >
>> >
>> >
>> >>From: Daniel <daniel@lynx.net>
>> >>To: Jason Murphy <jmurphy89@hotmail.com>
>> >>CC: <ascend-users@bungi.com>
>> >>Subject: Re: Ascend Max to Pipe NAT question
>> >>Date: Tue, 22 Jun 1999 09:42:21 -0700
>> >>
>> >>Yes, I have set the remote IP address on the P50 as the Max4k's IP 
>>address
>> >>and also the remote name as well. I will try to capture the hex code to 
>>see
>> >>what is going on.
>> >>
>> >>Thanks.
>> >>
>> >>Any more suggestion as where to look into ?
>> >>
>> >>Daniel
>> >>
>> >>
>> >>At 09:07 AM 6/22/99 PDT, you wrote:
>> >> >Hi, I saw your posting on the Ascend mailing list. I think that for 
>>PPP
>> >> >negotiation to work you need to set the Pipeline's remote IP address
>> >>under
>> >> >the config menu to that of the max's. I ran into this before. Make 
>>sure
>> >>that
>> >> >the remote name on the Pipe is set to the system name of the max also.
>> >>What
>> >> >you may want to do though is to go into diagnostics mode (hit the F1 
>>key,
>> >> >then d for diagnostics) and do a
>> >> >>wandisplay 64
>> >> >- then bring up the call from the max end and you will see hexadecimal
>> >> >output. Capture the trace with your telnet program or terminal 
>>emulation.
>> >> >Then email it to suppport@ascend.com and ask them to decode the trace 
>>to
>> >> >determine exactly where the PPP negotiation is failing.
>> >> >
>> >> >
>> >> >
>> >> >_______________________________________________________________
>> >> >Get Free Email and Do More On The Web. Visit http://www.msn.com
>> >> >
>> >> >
>> >>
>> >
>> >
>> >_______________________________________________________________
>> >Get Free Email and Do More On The Web. Visit http://www.msn.com
>> >
>> >
>
>
>_______________________________________________________________
>Get Free Email and Do More On The Web. Visit http://www.msn.com
>
>
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>