Paradise.net: PPP_NO_PROTOCOLS_CONFIGURED

Discussion in 'NZ Computing' started by Mainlander, Oct 6, 2003.

  1. Mainlander

    Mainlander Guest

    This is windows error 720 "Could not negotiate a compatible set of
    protocols". The helpdesk blames Windows, but I blame Paradise for these
    frequent errors over the last three days.

    Excerpts from ppplog.txt:

    10-07-2003 11:00:12.78 - Microsoft Dial Up Adapter log opened.
    10-07-2003 11:00:12.78 - Server type is PPP (Point to Point Protocol).
    10-07-2003 11:00:12.78 - FSA : Adding Control Protocol 80fd (CCP) to
    control protocol chain.
    10-07-2003 11:00:12.78 - FSA : Protocol disabled by user - skipping
    control protocol 803f (NBFCP).
    10-07-2003 11:00:12.78 - FSA : Adding Control Protocol 8021 (IPCP) to
    control protocol chain.
    10-07-2003 11:00:12.78 - FSA : Protocol not bound - skipping control
    protocol 802b (IPXCP).
    10-07-2003 11:00:12.78 - FSA : Adding Control Protocol c029 (CallbackCP)
    to control protocol chain.
    10-07-2003 11:00:12.78 - FSA : Adding Control Protocol c027 (no
    description) to control protocol chain.
    10-07-2003 11:00:12.78 - FSA : Adding Control Protocol c023 (PAP) to
    control protocol chain.
    10-07-2003 11:00:12.78 - FSA : Adding Control Protocol c223 (CHAP) to
    control protocol chain.
    10-07-2003 11:00:12.78 - FSA : Adding Control Protocol c021 (LCP) to
    control protocol chain.
    10-07-2003 11:00:12.78 - LCP : Callback negotiation enabled.
    10-07-2003 11:00:12.78 - LCP : Layer started.
    10-07-2003 11:00:12.78 - PPP : Transmitting Control Packet of length: 25
    10-07-2003 11:00:13.17 - PPP : Received Control Packet of length: 38
    10-07-2003 11:00:13.17 - LCP : Received and accepted MRU of 1524.
    10-07-2003 11:00:13.17 - LCP : Received and accepted ACCM of a0000.
    10-07-2003 11:00:13.17 - LCP : Received and accepted authentication
    protocol c223 (CHAP).
    10-07-2003 11:00:13.17 - LCP : Received and accepted protocol field
    compression option.
    10-07-2003 11:00:13.17 - LCP : Received and accepted address+control
    field compression option.
    10-07-2003 11:00:13.17 - PPP : Transmitting Control Packet of length: 19
    10-07-2003 11:00:13.17 - PPP : Received Control Packet of length: 9
    10-07-2003 11:00:13.17 - LCP : Received configure reject for callback
    control protocol option.
    10-07-2003 11:00:13.17 - PPP : Transmitting Control Packet of length: 22
    10-07-2003 11:00:13.29 - PPP : Received Control Packet of length: 25
    10-07-2003 11:00:13.29 - LCP : Received and accepted MRU of 1524.
    10-07-2003 11:00:13.29 - LCP : Received and accepted ACCM of a0000.
    10-07-2003 11:00:13.29 - LCP : Received and accepted authentication
    protocol c223 (CHAP).
    10-07-2003 11:00:13.29 - LCP : Received and accepted protocol field
    compression option.
    10-07-2003 11:00:13.29 - LCP : Received and accepted address+control
    field compression option.
    10-07-2003 11:00:13.29 - PPP : Transmitting Control Packet of length: 25
    10-07-2003 11:00:13.30 - PPP : Received Control Packet of length: 22
    10-07-2003 11:00:13.30 - LCP : Layer up.
    10-07-2003 11:00:13.30 - CHAP : Layer started.
    10-07-2003 11:00:13.41 - PPP : Received Control Packet of length: 34
    10-07-2003 11:00:13.41 - PPP : Transmitting Control Packet of length: 31
    10-07-2003 11:00:13.58 - PPP : Received Control Packet of length: 7
    10-07-2003 11:00:13.58 - CHAP : Login was successful.
    10-07-2003 11:00:13.58 - CHAP : Layer up.
    10-07-2003 11:00:13.58 - IPCP : Layer started.
    10-07-2003 11:00:13.58 - IPCP : IP address is 0.
    10-07-2003 11:00:13.58 - CCP : Layer started.
    10-07-2003 11:00:13.58 - PPP : Transmitting Control Packet of length: 42
    10-07-2003 11:00:13.58 - PPP : Transmitting Control Packet of length: 17
    10-07-2003 11:00:13.59 - PPP : Received Control Packet of length: 18
    10-07-2003 11:00:13.59 - IPCP : Received and accepted compression
    protocol request f 1.
    10-07-2003 11:00:13.59 - IPCP : Received and accepted IP address of
    ca002e51.
    10-07-2003 11:00:13.59 - PPP : Transmitting Control Packet of length: 18
    10-07-2003 11:00:13.59 - PPP : Received Control Packet of length: 12
    10-07-2003 11:00:13.59 - CCP : Received and accepted compression value 1.
    10-07-2003 11:00:13.59 - PPP : Transmitting Control Packet of length: 12
    10-07-2003 11:00:13.71 - PPP : Received Control Packet of length: 18
    10-07-2003 11:00:13.71 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:13.71 - PPP : Received Control Packet of length: 12
    10-07-2003 11:00:13.71 - CCP : Layer up.
    10-07-2003 11:00:16.72 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:19.73 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:22.74 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:25.74 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:28.75 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:31.76 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:34.76 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:37.77 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:40.78 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:43.79 - IPCP : Layer finished.
    10-07-2003 11:00:43.79 - FSA : Last control protocol failed.
    10-07-2003 11:00:43.79 - FSA : No network protocols were successfuly
    negotiated.
    10-07-2003 11:00:53.22 - Remote access driver is shutting down.
    10-07-2003 11:00:53.22 - CRC Errors 0
    10-07-2003 11:00:53.22 - Timeout Errors 0
    10-07-2003 11:00:53.22 - Alignment Errors 0
    10-07-2003 11:00:53.22 - Overrun Errors 0
    10-07-2003 11:00:53.22 - Framing Errors 0
    10-07-2003 11:00:53.22 - Buffer Overrun Errors 0
    10-07-2003 11:00:53.22 - Incomplete Packets 0
    10-07-2003 11:00:53.22 - Bytes Received 320
    10-07-2003 11:00:53.22 - Bytes Transmittted 670
    10-07-2003 11:00:53.22 - Frames Received 10
    10-07-2003 11:00:53.22 - Frames Transmitted 19
    10-07-2003 11:00:53.22 - LCP : Layer down.
    10-07-2003 11:00:53.22 - CHAP : Layer down.
    10-07-2003 11:00:53.22 - IPCP : Layer started.
    10-07-2003 11:00:53.22 - IPCP : IP address is 0.
    10-07-2003 11:00:53.22 - CCP : Layer down.
    10-07-2003 11:00:53.22 - PPP : Transmitting Control Packet of length: 6
    10-07-2003 11:00:53.73 - Microsoft Dial Up Adapter log closed.

    The difference between unsuccessful login and successful login seems to
    be after the CCP layer is up. On a successful login the log looks like
    this:

    10-07-2003 10:04:15.20 - Microsoft Dial Up Adapter log opened.
    10-07-2003 10:04:15.20 - Server type is PPP (Point to Point Protocol).
    10-07-2003 10:04:15.20 - FSA : Adding Control Protocol 80fd (CCP) to
    control protocol chain.
    10-07-2003 10:04:15.20 - FSA : Protocol disabled by user - skipping
    control protocol 803f (NBFCP).
    10-07-2003 10:04:15.20 - FSA : Adding Control Protocol 8021 (IPCP) to
    control protocol chain.
    10-07-2003 10:04:15.20 - FSA : Protocol not bound - skipping control
    protocol 802b (IPXCP).
    10-07-2003 10:04:15.20 - FSA : Adding Control Protocol c029 (CallbackCP)
    to control protocol chain.
    10-07-2003 10:04:15.20 - FSA : Adding Control Protocol c027 (no
    description) to control protocol chain.
    10-07-2003 10:04:15.20 - FSA : Adding Control Protocol c023 (PAP) to
    control protocol chain.
    10-07-2003 10:04:15.20 - FSA : Adding Control Protocol c223 (CHAP) to
    control protocol chain.
    10-07-2003 10:04:15.20 - FSA : Adding Control Protocol c021 (LCP) to
    control protocol chain.
    10-07-2003 10:04:15.20 - LCP : Callback negotiation enabled.
    10-07-2003 10:04:15.20 - LCP : Layer started.
    10-07-2003 10:04:15.20 - PPP : Transmitting Control Packet of length: 25

    [...]

    10-07-2003 10:04:16.19 - CCP : Layer up.
    10-07-2003 10:04:16.29 - PPP : Received Control Packet of length: 24
    10-07-2003 10:04:16.29 - IPCP : Changing IP address from 0 to d2f6188a.
    10-07-2003 10:04:16.29 - IPCP : Accepting primary DNS cb609804.
    10-07-2003 10:04:16.29 - IPCP : Accepting backup DNS cb60980c.
    10-07-2003 10:04:16.29 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 10:04:16.40 - PPP : Received Control Packet of length: 30
    10-07-2003 10:04:16.40 - IPCP : Layer up.
    10-07-2003 10:04:16.40 - FSA : Last control protocol is up.

    Note in the failed logon attempt the following

    10-07-2003 11:00:13.71 - CCP : Layer up.
    10-07-2003 11:00:16.72 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:19.73 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:22.74 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:25.74 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:28.75 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:31.76 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:34.76 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:37.77 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:40.78 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 11:00:43.79 - IPCP : Layer finished.
    10-07-2003 11:00:43.79 - FSA : Last control protocol failed.
    10-07-2003 11:00:43.79 - FSA : No network protocols were successfuly
    negotiated.

    The same 30 byte packet was transmitted 8 times before the system
    apparently gave up (the log data shows the packets were identical). On
    the screen this can be seen as a noticeable delay while the message is
    displayed "Verifying username and password". As can be seen this is more
    than 30 seconds with each packet transmitted at approximately 3 second
    intervals.

    Is there enough information to determine where the likely problem is? We
    have had intermittent connection problems on Paradise for weeks. This
    seems to suggest the problem may be associated with particular IP
    addresses (particular equipment racks at the ISP). The two machines I am
    using both run Windows 95 and have a 14400bps and 33600bps modem.

    In the log shown, Netbeui and IPX/SPX (plus TCP/IP) are bound to the
    dialup adapter but are unchecked in the dialup connection settings.
     
    Mainlander, Oct 6, 2003
    #1
    1. Advertising

  2. Mainlander

    Vogan Guest

    "Mainlander" <*@*.*> wrote in message
    news:...
    >
    > This is windows error 720 "Could not negotiate a compatible set of
    > protocols". The helpdesk blames Windows, but I blame Paradise for these
    > frequent errors over the last three days.
    >

    <SNIP>>
    > The same 30 byte packet was transmitted 8 times before the system
    > apparently gave up (the log data shows the packets were identical). On
    > the screen this can be seen as a noticeable delay while the message is
    > displayed "Verifying username and password". As can be seen this is more
    > than 30 seconds with each packet transmitted at approximately 3 second
    > intervals.
    >
    > Is there enough information to determine where the likely problem is? We
    > have had intermittent connection problems on Paradise for weeks. This
    > seems to suggest the problem may be associated with particular IP
    > addresses (particular equipment racks at the ISP). The two machines I am
    > using both run Windows 95 and have a 14400bps and 33600bps modem.


    Hi

    I have had similar problems over the last few days also, my firewall comes
    up with funny connection attempts to IP adresses like 0.0.0.0 and things
    like that. Also hangs at the same Verifying screen that you have seen. Can
    usually fix it by disconnecting and then re-connecting. I am on paradise
    dial up in Christchurch. Perhaps try the alternative phone number? I had
    to use it last night to get on.

    Hope this is of some help

    Cheers
    Vaughan

    BTW I am using Win XP
     
    Vogan, Oct 7, 2003
    #2
    1. Advertising

  3. Mainlander

    Mainlander Guest

    In article <cXtgb.6634$>,
    says...
    >
    > "Mainlander" <*@*.*> wrote in message
    > news:...
    > >
    > > This is windows error 720 "Could not negotiate a compatible set of
    > > protocols". The helpdesk blames Windows, but I blame Paradise for these
    > > frequent errors over the last three days.
    > >

    > <SNIP>>
    > > The same 30 byte packet was transmitted 8 times before the system
    > > apparently gave up (the log data shows the packets were identical). On
    > > the screen this can be seen as a noticeable delay while the message is
    > > displayed "Verifying username and password". As can be seen this is more
    > > than 30 seconds with each packet transmitted at approximately 3 second
    > > intervals.
    > >
    > > Is there enough information to determine where the likely problem is? We
    > > have had intermittent connection problems on Paradise for weeks. This
    > > seems to suggest the problem may be associated with particular IP
    > > addresses (particular equipment racks at the ISP). The two machines I am
    > > using both run Windows 95 and have a 14400bps and 33600bps modem.

    >
    > Hi
    >
    > I have had similar problems over the last few days also, my firewall comes
    > up with funny connection attempts to IP adresses like 0.0.0.0 and things
    > like that. Also hangs at the same Verifying screen that you have seen. Can
    > usually fix it by disconnecting and then re-connecting. I am on paradise
    > dial up in Christchurch. Perhaps try the alternative phone number? I had
    > to use it last night to get on.


    0873 number is fine but it's not the number Paradise want you to use, if
    everyone used it there would probably be continuous overload since they
    only list it as a "test number".

    What is your OS and software? Set up your DUN connection properties to
    record a log file and then check C:\Windows\ppplog.txt after each
    unsuccessful connection attempt. (Note that under Windows 95 and maybe
    even 98/ME this file will not update once it has reached > 256KB in size)

    The issue is I want Paradise to acknowlegde there is a problem with their
    systems, which so far they deny. I think with connection problems nonstop
    for the last two weeks, they don't really have a clue.
     
    Mainlander, Oct 7, 2003
    #3
  4. Mainlander

    Fishb8 Guest

    I'm on Paradise, too, and I've had that error 720, protocols... recently. I
    run XP Pro and have just re-installed.
    Thought it was me but maybe not!
    Roy Price
     
    Fishb8, Oct 7, 2003
    #4
  5. Mainlander

    T.N.O. Guest

    "Mainlander" wrote
    > The issue is I want Paradise to acknowlegde there is a problem with their
    > systems, which so far they deny. I think with connection problems nonstop
    > for the last two weeks, they don't really have a clue.


    There are a lot of Paradise users who hang around in this group, and only
    two users complaining... it sounds fairly isolated... are you two in the
    same suburb?
     
    T.N.O., Oct 7, 2003
    #5
  6. Mainlander

    Mainlander Guest

    In article <yCDgb.6939$>,
    says...
    > I'm on Paradise, too, and I've had that error 720, protocols... recently. I
    > run XP Pro and have just re-installed.
    > Thought it was me but maybe not!
    > Roy Price


    I don't think so.

    I suggest everyone, set up your connection to record a log file. This is
    pretty easy to do.
     
    Mainlander, Oct 7, 2003
    #6
  7. Mainlander

    Gordon Smith Guest

    Why are you using CHAP instead of PAP??
     
    Gordon Smith, Oct 7, 2003
    #7
  8. Mainlander

    Mainlander Guest

    In article <>, says...
    > "Mainlander" wrote
    > > The issue is I want Paradise to acknowlegde there is a problem with their
    > > systems, which so far they deny. I think with connection problems nonstop
    > > for the last two weeks, they don't really have a clue.

    >
    > There are a lot of Paradise users who hang around in this group, and only
    > two users complaining... it sounds fairly isolated... are you two in the
    > same suburb?


    There's been several people, and this is only a small thread. There are
    probably dozens more people out there who don't use the news service, or
    are in different cities and accessing different POPs.
     
    Mainlander, Oct 7, 2003
    #8
  9. Mainlander

    Mainlander Guest

    In article <>,
    says...
    > Why are you using CHAP instead of PAP??


    If you know the technical guff then spew, I wouldn't have a clue what
    half these protocols are, the order they go in etc etc, but having the
    information available probably goes some way to working out whether the
    problem is on my side of the connection or theirs.

    I am especially interested to discover why it gets to that point of
    retrying the same packet 8 times without a response from the other end.

    If you read you will see PAP is in use, as well as CHAP, CCP, IPCP,
    CallbackCP, LCP etc etc.

    These are the critical differences. As can be seen there is a difference
    in what happens in the last few packets sent.

    10-07-2003 19:38:41.63 - CCP : Layer started.
    10-07-2003 19:38:41.63 - PPP : Transmitting Control Packet of length: 42
    10-07-2003 19:38:41.63 - PPP : Transmitting Control Packet of length: 17
    10-07-2003 19:38:41.63 - PPP : Received Control Packet of length: 18
    10-07-2003 19:38:41.63 - IPCP : Received and accepted compression
    protocol request f 1.
    10-07-2003 19:38:41.63 - IPCP : Received and accepted IP address of
    ca002e51.
    10-07-2003 19:38:41.63 - PPP : Transmitting Control Packet of length: 18
    10-07-2003 19:38:41.65 - PPP : Received Control Packet of length: 12
    10-07-2003 19:38:41.65 - CCP : Received and accepted compression value 1.
    10-07-2003 19:38:41.65 - PPP : Transmitting Control Packet of length: 12
    10-07-2003 19:38:41.76 - PPP : Received Control Packet of length: 18
    10-07-2003 19:38:41.76 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 19:38:41.77 - PPP : Received Control Packet of length: 12
    10-07-2003 19:38:41.77 - CCP : Layer up.
    10-07-2003 19:38:44.78 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 19:38:47.79 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 19:38:50.78 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 19:38:53.79 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 19:38:56.79 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 19:38:59.79 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 19:39:02.81 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 19:39:05.82 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 19:39:08.82 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 19:39:11.83 - IPCP : Layer finished.
    10-07-2003 19:39:11.83 - FSA : Last control protocol failed.
    10-07-2003 19:39:11.83 - FSA : No network protocols were successfuly
    negotiated.
    10-07-2003 19:39:15.00 - Remote access driver is shutting down.
    10-07-2003 19:39:15.00 - CRC Errors 0
    10-07-2003 19:39:15.00 - Timeout Errors 0
    10-07-2003 19:39:15.00 - Alignment Errors 0
    10-07-2003 19:39:15.00 - Overrun Errors 0
    10-07-2003 19:39:15.00 - Framing Errors 0
    10-07-2003 19:39:15.00 - Buffer Overrun Errors 0
    10-07-2003 19:39:15.00 - Incomplete Packets 0
    10-07-2003 19:39:15.00 - Bytes Received 321
    10-07-2003 19:39:15.00 - Bytes Transmittted 676
    10-07-2003 19:39:15.00 - Frames Received 10
    10-07-2003 19:39:15.00 - Frames Transmitted 19
    10-07-2003 19:39:15.00 - LCP : Layer down.
    10-07-2003 19:39:15.00 - CHAP : Layer down.
    10-07-2003 19:39:15.00 - IPCP : Layer started.
    10-07-2003 19:39:15.00 - IPCP : IP address is 0.
    10-07-2003 19:39:15.00 - CCP : Layer down.
    10-07-2003 19:39:15.00 - PPP : Transmitting Control Packet of length: 6
    10-07-2003 19:39:15.00 - Data 0000: c0 21 05 03 00 04 00 00 | .!......
    10-07-2003 19:39:15.52 - Microsoft Dial Up Adapter log closed.

    10-07-2003 20:01:21.08 - CCP : Layer started.
    10-07-2003 20:01:21.08 - PPP : Transmitting Control Packet of length: 42
    10-07-2003 20:01:21.08 - PPP : Transmitting Control Packet of length: 17
    10-07-2003 20:01:21.08 - PPP : Received Control Packet of length: 18
    10-07-2003 20:01:21.08 - IPCP : Received and accepted compression
    protocol request f 1.
    10-07-2003 20:01:21.08 - IPCP : Received and accepted IP address of
    c0a80f2a.
    10-07-2003 20:01:21.08 - PPP : Transmitting Control Packet of length: 18
    10-07-2003 20:01:21.22 - PPP : Received Control Packet of length: 18
    10-07-2003 20:01:21.22 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 20:01:21.23 - PPP : Received Control Packet of length: 23
    10-07-2003 20:01:21.23 - FSA : Received protocol reject for control
    protocol 80fd.
    10-07-2003 20:01:21.23 - CCP : Layer finished.
    10-07-2003 20:01:21.37 - PPP : Received Control Packet of length: 24
    10-07-2003 20:01:21.37 - IPCP : Changing IP address from 0 to cb4f4c2f.
    10-07-2003 20:01:21.37 - IPCP : Accepting primary DNS cb609804.
    10-07-2003 20:01:21.37 - IPCP : Accepting backup DNS cb60980c.
    10-07-2003 20:01:21.37 - PPP : Transmitting Control Packet of length: 30
    10-07-2003 20:01:21.51 - PPP : Received Control Packet of length: 30
    10-07-2003 20:01:21.51 - IPCP : Layer up.
    10-07-2003 20:01:21.51 - FSA : Last control protocol is up.
    10-07-2003 20:28:39.89 - Remote access driver is shutting down.
    10-07-2003 20:28:39.89 - CRC Errors 0
    10-07-2003 20:28:39.89 - Timeout Errors 0
    10-07-2003 20:28:39.89 - Alignment Errors 0
    10-07-2003 20:28:39.89 - Overrun Errors 0
    10-07-2003 20:28:39.89 - Framing Errors 0
    10-07-2003 20:28:39.89 - Buffer Overrun Errors 0
    10-07-2003 20:28:39.89 - Incomplete Packets 0
    10-07-2003 20:28:39.89 - Bytes Received 1704187
    10-07-2003 20:28:39.89 - Bytes Transmittted 1062682
    10-07-2003 20:28:39.89 - Frames Received 4932
    10-07-2003 20:28:39.89 - Frames Transmitted 4453
    10-07-2003 20:28:39.89 - LCP : Layer down.
    10-07-2003 20:28:39.89 - PAP : Layer down.
    10-07-2003 20:28:39.89 - IPCP : Layer down.
    10-07-2003 20:28:40.06 - CCP : Layer started.
    10-07-2003 20:28:40.06 - PPP : Transmitting Control Packet of length: 6
    10-07-2003 20:28:40.06 - Data 0000: c0 21 05 03 00 04 00 00 | .!......
    10-07-2003 20:28:40.17 - PPP : Received Control Packet of length: 6
    10-07-2003 20:28:40.17 - Data 0000: c0 21 06 03 00 04 00 00 | .!......
    10-07-2003 20:28:40.17 - LCP : Received terminate acknowledgement.
    10-07-2003 20:28:40.17 - LCP : Layer finished.
    10-07-2003 20:28:40.17 - Microsoft Dial Up Adapter log closed.
     
    Mainlander, Oct 8, 2003
    #9
  10. Mainlander

    T.N.O. Guest

    "Mainlander" wrote
    > I am especially interested to discover why it gets to that point of
    > retrying the same packet 8 times without a response from the other end.


    what type of modem do you have?
     
    T.N.O., Oct 8, 2003
    #10
  11. Mainlander

    T.N.O. Guest

    "Gordon Smith" wrote
    > Forgot to add that LCP, IPCP, CCP are all part of PPP network control.
    > See http://www.networksorcery.com/enp/protocol/IPCP.htm for more
    > info


    Fix your clock... dont those fancy Linux boxes you use have time sync?

    Daylight saving was last weekend :)
     
    T.N.O., Oct 8, 2003
    #11
  12. Mainlander

    Gordon Smith Guest

    In article <>, Mainlander wrote:
    > In article <>,
    > says...
    >> Why are you using CHAP instead of PAP??

    >
    > If you know the technical guff then spew, I wouldn't have a clue what
    > half these protocols are, the order they go in etc etc, but having the
    > information available probably goes some way to working out whether the
    > problem is on my side of the connection or theirs.
    >

    <snip>

    Not many providers will support CHAP (challenge handshake auth protocol).
    Everyone supports PAP though. I'd suggest disabling CHAP in your dialup
    config.
     
    Gordon Smith, Oct 8, 2003
    #12
  13. Mainlander

    Gordon Smith Guest

    Gordon Smith, Oct 8, 2003
    #13
  14. Mainlander

    Mainlander Guest

    In article <blvioo$gtckk$-berlin.de>,
    says...
    > "Mainlander" wrote
    > > I am especially interested to discover why it gets to that point of
    > > retrying the same packet 8 times without a response from the other end.

    >
    > what type of modem do you have?


    14400bps Dynalink, 33600bps Sysgration
     
    Mainlander, Oct 8, 2003
    #14
  15. Mainlander

    Mainlander Guest

    In article <>,
    says...
    > In article <>, Mainlander wrote:
    > > In article <>,
    > > says...
    > >> Why are you using CHAP instead of PAP??

    > >
    > > If you know the technical guff then spew, I wouldn't have a clue what
    > > half these protocols are, the order they go in etc etc, but having the
    > > information available probably goes some way to working out whether the
    > > problem is on my side of the connection or theirs.
    > >

    > <snip>
    >
    > Not many providers will support CHAP (challenge handshake auth protocol).
    > Everyone supports PAP though. I'd suggest disabling CHAP in your dialup
    > config.


    Where is the setting to disable it?

    I only have the standard options enabled - software compression and
    TCP/IP and record a log file are checked in the connection settings.
     
    Mainlander, Oct 8, 2003
    #15
  16. Mainlander

    Mainlander Guest

    Mainlander, Oct 8, 2003
    #16
  17. Mainlander

    Mainlander Guest

    In article <>,
    says...
    > In article <>, Mainlander wrote:
    > > In article <>,
    > > says...
    > >> Why are you using CHAP instead of PAP??

    > >
    > > If you know the technical guff then spew, I wouldn't have a clue what
    > > half these protocols are, the order they go in etc etc, but having the
    > > information available probably goes some way to working out whether the
    > > problem is on my side of the connection or theirs.
    > >

    > <snip>
    >
    > Not many providers will support CHAP (challenge handshake auth protocol).
    > Everyone supports PAP though. I'd suggest disabling CHAP in your dialup
    > config.


    CHAP is being used in only some logins, a mixture of successful and
    unsuccessful.

    It appears that CHAP is not always used, so I assume there is provision
    to negotiate its use.
     
    Mainlander, Oct 8, 2003
    #17
  18. Mainlander

    Vogan Guest

    "Mainlander" <*@*.*> wrote in message
    news:...
    > In article <cXtgb.6634$>,
    > says...
    > >
    > > "Mainlander" <*@*.*> wrote in message
    > > news:...
    > > >
    > > > This is windows error 720 "Could not negotiate a compatible set of
    > > > protocols". The helpdesk blames Windows, but I blame Paradise for

    these
    > > > frequent errors over the last three days.
    > > >

    > > <SNIP>>
    > > > The same 30 byte packet was transmitted 8 times before the system
    > > > apparently gave up (the log data shows the packets were identical). On
    > > > the screen this can be seen as a noticeable delay while the message is
    > > > displayed "Verifying username and password". As can be seen this is

    more
    > > > than 30 seconds with each packet transmitted at approximately 3 second
    > > > intervals.
    > > >
    > > > Is there enough information to determine where the likely problem is?

    We
    > > > have had intermittent connection problems on Paradise for weeks. This
    > > > seems to suggest the problem may be associated with particular IP
    > > > addresses (particular equipment racks at the ISP). The two machines I

    am
    > > > using both run Windows 95 and have a 14400bps and 33600bps modem.

    > >
    > > Hi
    > >
    > > I have had similar problems over the last few days also, my firewall

    comes
    > > up with funny connection attempts to IP adresses like 0.0.0.0 and things
    > > like that. Also hangs at the same Verifying screen that you have seen.

    Can
    > > usually fix it by disconnecting and then re-connecting. I am on

    paradise
    > > dial up in Christchurch. Perhaps try the alternative phone number? I

    had
    > > to use it last night to get on.

    >
    > 0873 number is fine but it's not the number Paradise want you to use, if
    > everyone used it there would probably be continuous overload since they
    > only list it as a "test number".
    >
    > What is your OS and software? Set up your DUN connection properties to
    > record a log file and then check C:\Windows\ppplog.txt after each
    > unsuccessful connection attempt. (Note that under Windows 95 and maybe
    > even 98/ME this file will not update once it has reached > 256KB in size)
    >
    > The issue is I want Paradise to acknowlegde there is a problem with their
    > systems, which so far they deny. I think with connection problems nonstop
    > for the last two weeks, they don't really have a clue.
    >
    >


    Hi

    Good idea, I'll set it up now. Point taken about the 0873 number but if I
    can't get on using the normal number then I will use to 0873 one. My OS is
    WinXP Pro, IE6, Outlook 2000.

    Cheers
    Vaughan
     
    Vogan, Oct 8, 2003
    #18
  19. Mainlander

    T-Boy Guest

    In article <>,
    says...
    > Forgot to add that LCP, IPCP, CCP are all part of PPP network control.
    > See http://www.networksorcery.com/enp/protocol/IPCP.htm for more


    Uncheck LCP for dialup paradise connections - not supported according to
    the tech I spoke to (fixing a dialup problem this Monday).

    --
    Duncan
     
    T-Boy, Oct 8, 2003
    #19
  20. Mainlander

    Mainlander Guest

    In article <>,
    says...
    > In article <>,
    > says...
    > > Forgot to add that LCP, IPCP, CCP are all part of PPP network control.
    > > See http://www.networksorcery.com/enp/protocol/IPCP.htm for more

    >
    > Uncheck LCP for dialup paradise connections - not supported according to
    > the tech I spoke to (fixing a dialup problem this Monday).


    None of these protocols are user configurable. They are all negotiated by
    the two computers.
     
    Mainlander, Oct 8, 2003
    #20
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. DaveG

    Paradise Net & pppd

    DaveG, Nov 24, 2003, in forum: NZ Computing
    Replies:
    10
    Views:
    486
    DaveG
    Nov 27, 2003
  2. K & S

    Site not working with Paradise.net

    K & S, Jan 8, 2004, in forum: NZ Computing
    Replies:
    3
    Views:
    408
    K & S
    Jan 8, 2004
  3. K & S

    WEB Site not working with Paradise.net

    K & S, Jan 8, 2004, in forum: NZ Computing
    Replies:
    8
    Views:
    329
  4. Kazonme

    paradise.net traffice bandwidth

    Kazonme, Feb 8, 2004, in forum: NZ Computing
    Replies:
    1
    Views:
    308
    T.N.O. - Dave.net.nz
    Feb 8, 2004
  5. Jones Minor

    Clear Net vs Paradise Net

    Jones Minor, Nov 21, 2005, in forum: NZ Computing
    Replies:
    2
    Views:
    447
    Michael Newbery
    Nov 21, 2005
Loading...

Share This Page