ISDN Data Link Betwee two sites

[SpareTek]

I am trying to establish a data link over a point to point isdn QSIG line betwee two IP Offices. Voice is working ok over the line. When I ping site a to site b monitor at site A is indicating my password does not match even though all the passwords are the same. Any ideas? Monitor follows:

171164mS Interface Queue: v=HwcFrame WAN 0 1
IP Dst=132.152.162.1 Src=200.100.100.243 vl=45 tos=00 len=60 id=d2da ttl=127 flg=00 off=0000 pcol=1 sum=14f5
ICMP type=8 (EchoRequest) code=0 (NetUnreach) sum=545b 0200f700
0000 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 abcdefghijklmnop
0010 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69 qrstuvwabcdefghi
171335mS PPP LCP Tx: v=HwcFrame
PPP LCP Config-Req(1) id=1 len=33
MagicNum=0002d7d2
Protocol field compression
Address and control field compression
MRRU=1500
ShortSeq
EndPointDiscrim=mac 00e007004f18
MultiClass=6 Classes=4
171341mS PPP LCP Tx: v=HwcFrame
PPP LCP Config-Req(1) id=1 len=37
MagicNum=0002d7d8
AuthProt=c023
Protocol field compression
Address and control field compression
MRRU=1500
ShortSeq
EndPointDiscrim=mac 00e007004f18
MultiClass=6 Classes=4
171341mS PPP LCP Rx: v=HwcFrame
PPP LCP Config-Req(1) id=1 len=33
MagicNum=0002d7d2
Protocol field compression
Address and control field compression
MRRU=1500
ShortSeq
EndPointDiscrim=mac 00e007004f18
MultiClass=6 Classes=4
171342mS PPP LCP Tx: v=HwcFrame
PPP LCP Config-Ack(2) id=1 len=33
MagicNum=0002d7d2
Protocol field compression
Address and control field compression
MRRU=1500
ShortSeq
EndPointDiscrim=mac 00e007004f18
MultiClass=6 Classes=4
171347mS PPP LCP Rx: v=HwcFrame
PPP LCP Config-Req(1) id=1 len=37
MagicNum=0002d7d8
AuthProt=c023
Protocol field compression
Address and control field compression
MRRU=1500
ShortSeq
EndPointDiscrim=mac 00e007004f18
MultiClass=6 Classes=4
171348mS PPP LCP Tx: v=HwcFrame
PPP LCP Config-Ack(2) id=1 len=37
MagicNum=0002d7d8
AuthProt=c023
Protocol field compression
Address and control field compression
MRRU=1500
ShortSeq
EndPointDiscrim=mac 00e007004f18
MultiClass=6 Classes=4
171352mS PPP LCP Rx: v=HwcFrame
PPP LCP Config-Ack(2) id=1 len=33
MagicNum=0002d7d2
Protocol field compression
Address and control field compression
MRRU=1500
ShortSeq
EndPointDiscrim=mac 00e007004f18
MultiClass=6 Classes=4
171353mS PPP Sec Tx: v=HwcFrame
PPP PAP Authenticate-Request 2
peer="hwc" password="hwc"
171354mS PPP LCP Rx: v=HwcFrame
PPP LCP Config-Ack(2) id=1 len=37
MagicNum=0002d7d8
AuthProt=c023
Protocol field compression
Address and control field compression
MRRU=1500
ShortSeq
EndPointDiscrim=mac 00e007004f18
MultiClass=6 Classes=4
171356mS PPP Sec Rx: v=HwcFrame
PPP PAP Authenticate-Request 2
peer="hwc" password="hwc"
171358mS ERR: hwc PAP AuthenticateNak,
171358mS PPP LCP Tx: v=HwcFrame
PPP LCP Terminate-Req(5) id=2 len=4
171362mS PPP Sec Rx: v=HwcFrame
PPP PAP Authenticate-Nak 2
msg="PAP PASSWORD BAD"
171362mS ERR: HwcFrame PAP Authenticate fails, remote peer NAKs
171363mS PPP LCP Tx: v=HwcFrame
PPP LCP Terminate-Req(5) id=3 len=4

 

[MrIPO]

Refer to the FAQ regarding the configuration of this, I have not performed this connection over a QSIG link before only stright ETSI connection, over BRI and PRI

You can find the FAQ under FAQ's at the top of this page

Are you using PAP or CHAP currently in you config ??

 

[SpareTek]

On the PPP tab of the Service, Chap response interval is blank; that is the only field I see referencing PAP or CHAP. I also did not check use encrypted password.

My setup follows the faq close, but I added a shortcode to match the telephone number on the service tab to make it dial on the proper line group. This weekend I will try dial64K vs just dial and set the # of channels to one, or something. I had channels set to min & max of 2 so far, but did not have BACP checked on PPP tab.

A note on the faq, destination Georgia on site A does not match name or account on site B, which may be a typo??

Also, it is confusing as to what the default "dialin" ras has to do with it. I setup a new ras with the same name as my user. Also, I used the same user names and password everywhere to help eliminate any missmatch. I have done this on wan links with good success.

And all the above gets back to the fact that it appears to be negotiating a connection and just has a password issue, that is unless the calling site considers a timeout the same as a real NAK. However the monitor does show both tx and rx. On the called system, I cannot see any connection activity on monitor, but assume they may not show any data until a connection is negociated.