Hello, > > I am trying to configure ISDN BRI for dialout using 2503 but could not > connect to remote access server of the ISP. I have taken a ISDN dialup > account from ISP and it has given me "userid", passwd and dialup number. > I > tried these through normal dialup (windows dun) and it connects > succesfully. > Now I have following configuration for my 2503 router but this could not > connect. Please advise if I am missing something as I am new to ISDN and > doing it for the first time > > > ! > interface BRI0 > ip address negotiated > ip directed-broadcast > encapsulation ppp > no ip split-horizon > dialer idle-timeout 2147483 > dialer string 12144444 > dialer hold-queue 10 > dialer-group 1 > isdn switch-type basic-net3 > ppp authentication pap > ppp pap sent-username <myusername> password <mypassword> > > ! > ip route 204.71.200.45 255.255.255.255 BRI0 > > ! > dialer-list 1 protocol ip permit > > > when I ping 204.71.200.45 , following appears on the terminal: > > > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 204.71.200.45, timeout is 2 seconds: > > 00:58:39: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 64 changed to > up > 00:58:40: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up.... > 00:58:46: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 12144444 > . > Success rate is 0 percent (0/5) > > 00:59:03: %ISDN-6-DISCONNECT: Interface BRI0:1 disconnected from > 12144444 , > cal > l lasted 22 seconds > 00:59:03: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down > 00:59:05: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 64 changed > to > dow > > sh in bri0 > > BRI0 is up, line protocol is up (spoofing) > Hardware is BRI > Internet address will be negotiated using IPCP > MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, > reliability 255/255, txload 1/255, rxload 1/255 > Encapsulation PPP, loopback not set > Last input 00:00:01, output 00:00:01, output hang never > Last clearing of "show interface" counters 01:09:44 > Input queue: 0/75/0 (size/max/drops); Total output drops: 0 > Queueing strategy: weighted fair > Output queue: 0/1000/64/0 (size/max total/threshold/drops) > Conversations 0/1/256 (active/max active/max total) > Reserved Conversations 0/0 (allocated/max allocated) > 5 minute input rate 0 bits/sec, 0 packets/sec > 5 minute output rate 0 bits/sec, 0 packets/sec > 536 packets input, 3389 bytes, 0 no buffer > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > 534 packets output, 3376 bytes, 0 underruns > 0 output errors, 0 collisions, 13 interface resets > 0 output buffer failures, 0 output buffers swapped out > 35 carrier transitions Looking at the outputs above and the configs, a couple of thoughts come to mind (some of which are related to the problem at hand:-) 1. I was curious about the use of the static route you had. Since it is a route to a specific host, I was curious as to why this was used? Given that you have set your IP address as "negotiated," what happens when there is a packet for any other network or host besides 204.71.200.45? My recommendation would be to do the following - set up a default route that points to your BRI0 interface, or to a dialer interface (which is bound to your ISDN BRI0). 2. You do understand you have set this link up to be pinned up full time once you get it working? This command: dialer idle-timeout 2147483 effectively does that. If you are on a metered line, be prepared to shell out some big doneros for your first month's bill. If you have no meter on the line, don't worry about it. I would recommend the default value under most circumstances. 3. SPIDs are not required since you are using a basic-net3 ISDN switch type. 4. It's probably not relevant to your problem, but verify whether there is a requirement for your ISDN switch to do ten digit dialing. 22 Seconds is about long enough to get the evil operator tone and go "off hook." 5. I would definitely look at your authentication exchange. A simple debug ppp auth will do the trick. Is one side authenticating, but not the other? Is your ISP doing CHAP only? Your Winthing using MS-DUN typically wants to use MS- CHAP unless you tell it otherwise. The same may be true for the router. You may even want to use the "ppp auth chap pap" command to use CHAP first, then revert to PAP. You will of course need extra entries to configure chap. If you are running post 12.0 code, your router should support MS-CHAP as well. Make sure if you are not at the console to execute the "term mon" command to get debug sent to your telnet session. I would also turn on "debug IP ICMP" to see what is happening to your pings. Are you sending any pings? Are you getting replies? Follow up your pings with a trace command to see where your packets are going/dying. 6. A more useful show command would be "sho int bri0:1" You will want to see that IPCP is negotiated on your B channel. If not, the "debug ppp negotiation" command is very useful, particularly to tell you if there were any LCP anomalies. 7. I don't see any other interfaces in your config, but do you plan to use NAT? If so, that will add configuration entries that are not yet shown (and will need to be configured). 8. You may want to turn on multilink. It is generally a good thing. HTH, Paul Werner ________________________________________________ Get your own "800" number - Free Free voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag ___________________________________ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
