RE: dialer remote name/ppp chap hostname [7:59224]

[test test]

You could try another approach on this as opposed to performing
authentication commands on the individual interfaces.

set up AAA authentication globaly on the routers 
this prevents intensive interface configuration 
allows you to focus purely on the authentication problem
you can establish radius, tacacs+, or local authentication
which is what you are trying to do.

there are several debug commands you may try at the head end.

something like: debug ppp authentication chap

sorry it's been a while...


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=59270&t=59224
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

RE: dialer remote name/ppp chap hostname [7:59224]

[pete bateman]

Keith,

Its to do with the order in which the call is handled. The dialer-remote
name is what allows the incomming call to be bound to the dialer. Otherwise
IOS has no way of knowing which dialer the call is for. The call must
authenticate first, then get the remote name from chap, then lookup the
dialer. No dialer remote name, no call binding. LCP will complete, but you
will get no IPCP nego because the call has not bound to an IP enabled Dialer.

PPP chap host is only used as an outgoing alternative hostname if the device
at the other end is not a cisco router, or there is some other reason why
you do not want to identify your router with its real hostname.

Get rid of the ppp chap hostname commands put the dialer remote names back
in, make sure the local prompt matches the remote user and remote dialer
remote statement each way and it will work.




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=59301&t=59224
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]