Perhaps this will help
A Shiva AccessPort tries SPAP for authentication first (default), but this is not
NAK'd
correctly by the Cisco device, which expects CHAP.
Solution:
Set the Shiva AccessPort to use only CHAP as the authentication protocol.
1. Go into admin mode, and enter the following commands:
net isdn2 se
listener
PAP: no
CHAP: yes
SPAP: no
My CHAP identifying name : lokal host name
Simultaneous two way authentication: no
Av
Neil Bennett wrote:
> Hi,
>
> Wondering if someone could help. I have been trying to set up a 3620 to dial
> in to a shiva intergrator by using dialer profiles.
> The router was configured using dialer map's but for some reason appeared to
> be very slow to open the isdn line up (to actually open it, not the PPP
> stage) using dialer profiles the line open's quickly but doesnt connect,
> debugging ppp auth returns nothing and debuging ppp neg shows the shiva
> rejecting chap. The shiva does work using chap when using dialer map's on
> the cisco.
> Im guessing that the problem is with my config of the dialer profiles, but i
> cant work out why.
>
> Here is dialer interface config,
>
> interface dialer0
> ip address 10.10.10.1 255.255.255.0
> encapsulation ppp
> dialer remote-name shiva
> dialer pool 1
> dialer-group 1
> no cdp enable
> ppp authentication chap
>
> What i dont understand is why it doesnt even reach the authentication
> stage.........the person supporting the shiva's isnt gonna change the config
> coz it already works that end!!
>
> TIA,
>
> Neil
>
> _________________________________
> FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]