Hi David,
I've got an IP set in ip-global as 209.251.129.59 (in case
that matters). I do not have one set for ip-interface {{0 0 0}}
but I do have the same IP address set on ip-interface {{1 16 1}0}
(which is my ethernet connection for the TNT).
I'm not sure that I understand, the TNT won't let me set the
same IP address on {{0 0 0}}. Are you saying to use something
like 209.251.129.60 for {{0 0 0}}?
I'm willing to try anything once, just want to make sure I'm
trying the right thing. I should mention that I'm running
TAOS v9.0.3 and the working TNT does not have an IP set in the
{{0 0 0}} interface either and it doesn't seem to have a problem
with the same users that can't use my other TNT's.
I'm hoping to upgrade to TAOS v9.0.9 tomorrow.
--
David A. Niblett | eMail: niblettda at gru.net
Network Administrator | Phone: (352) 334-3400
Gainesville Regional Utilities | Web: http://www.gru.net/
> -----Original Message-----
> From: DPascarella at solunet.com [mailto:DPascarella at solunet.com]
> Sent: Monday, November 25, 2002 3:27 PM
> To: niblettda at gru.com; b.weeber at viastore.de; ascend-users at bungi.com
> Subject: RE: [Ascend] RE: (ASCEND) Disconnect code 185, Progress 30
> proble m
>
>
> Do you have a system-ip-address configured? Both in 'ip-glo'
> and "ip-int
> {{0 0 0}}"? These 2 IP must be unique (in your network) and
> configured the
> same in both places (on the TNT). It will be your new source
> IP for all IP
> packets leaving the chassis. I've seen cases like you
> describe because this
> was not configured correctly.....esp with WebTV Users! It
> screws up IPNCP
> for some modems.
>
> my $.02,
>
> - David
>
>
> -----Original Message-----
> From: niblettda at gru.com [mailto:niblettda at gru.com]
> Sent: Monday, November 25, 2002 11:25 AM
> To: b.weeber at viastore.de; ascend-users at bungi.com
> Subject: [Ascend] RE: (ASCEND) Disconnect code 185, Progress
> 30 problem
>
>
> Burkhard,
>
> Actually, I know it's hanging up at the LCP negotiation.
> I'm still confused why it works on my old number, but
> not my new number. The hardware is the same, the TAOS
> version is the same. People seem to negotiate the same
> connect speed as before, and can't connect, but if they
> force the modem to connect at a lower speed (like 33.6)
> they connect just fine to the new number.
>
> Here is a log from a machine calling my new number:
>
> 10/25/02 5:12 PM Dialing 5821111
> 10/25/02 5:12 PM CCL write: "ATDT5821111\13"
> 10/25/02 5:13 PM CCL match: "CARRIER"
> 10/25/02 5:13 PM CCL match: "CONNECT "
> 10/25/02 5:13 PM CCL match: "49333"
> 10/25/02 5:13 PM CCL match: "\10"
> 10/25/02 5:13 PM PPP connection started.
> 10/25/02 5:13 PM LCP: Sending Configuration Request.
> 10/25/02 5:13 PM LCP: >> Async Map = 0x00000000.
> 10/25/02 5:13 PM LCP: >> Magic Number = 0xB4EA711E.
> 10/25/02 5:13 PM LCP: >> Protocol Compression On
> 10/25/02 5:13 PM LCP: >> Address/Control Compression On
> 10/25/02 5:13 PM LCP: Sending Configuration Request.
> 10/25/02 5:13 PM LCP: >> Async Map = 0x00000000.
> 10/25/02 5:13 PM LCP: >> Magic Number = 0xB4EA711E.
> 10/25/02 5:13 PM LCP: >> Protocol Compression On
> 10/25/02 5:13 PM LCP: >> Address/Control Compression On
> ... Repeated 6 more times ...
> 10/25/02 5:13 PM No response from the remote side.
> 10/25/02 5:13 PM CCL write: "+++ATH\13"
> 10/25/02 5:13 PM CCL match: "OK\13\10"
> 10/25/02 5:13 PM CCL write: "AT&F\13"
> 10/25/02 5:13 PM CCL match: "OK\13\10"
> 10/25/02 5:13 PM The remote side is not responding correctly.
> 10/25/02 5:13 PM Connection terminated.
>
>
> On the same machine, dialing my old number, I get this:
>
> 10/25/02 5:20 PM Dialing 3777997
> 10/25/02 5:20 PM CCL write: "ATDT3777997\13"
> 10/25/02 5:21 PM CCL match: "CARRIER"
> 10/25/02 5:21 PM CCL match: "PROTOCOL: LAP"
> 10/25/02 5:21 PM CCL match: "CONNECT "
> 10/25/02 5:21 PM CCL match: "49333"
> 10/25/02 5:21 PM CCL match: "\10"
> 10/25/02 5:21 PM PPP connection started.
> 10/25/02 5:21 PM LCP: Sending Configuration Request.
> 10/25/02 5:21 PM LCP: >> Async Map = 0x00000000.
> 10/25/02 5:21 PM LCP: >> Magic Number = 0xD1BB17CD.
> 10/25/02 5:21 PM LCP: >> Protocol Compression On
> 10/25/02 5:21 PM LCP: >> Address/Control Compression On
> 10/25/02 5:21 PM LCP: Received Configuration Request.
> 10/25/02 5:21 PM LCP: >> MRU = 1524.
> ... All the normal PPP negotiation ...
> 10/25/02 5:21 PM PPP ready for TCP/IP with IP address
> 64.238.160.252.
> 10/25/02 5:21 PM Connection established at 49333 bps.
> 10/25/02 5:21 PM CCL write: "+++ATH\13"
> 10/25/02 5:22 PM CCL match: "OK\13\10"
> 10/25/02 5:22 PM CCL write: "AT&F\13"
> 10/25/02 5:22 PM CCL match: "OK\13\10"
> 10/25/02 5:22 PM Connection terminated.
>
> Thanks again.
>
> --
> David A. Niblett | eMail: niblettda at gru.net
> Network Administrator | Phone: (352) 334-3400
> Gainesville Regional Utilities | Web: http://www.gru.net/
>
>
>
> > -----Original Message-----
> > From: Burkhard Weeber [mailto:b.weeber at viastore.de]
> > Sent: Monday, November 25, 2002 9:53 AM
> > To: niblettda at gru.com; Ascend User List (E-Mail)
> > Subject: RE: (ASCEND) Disconnect code 185, Progress 30 problem
> >
> >
> > Looks like the PPP handshake fails.
> > I would use a telnet client which can capture to file, go
> > into diagnostics
> > mode and do a "wannext 1500".
> > Feed that file to "ethereal" and you will get a quite good
> > understanding
> > what happens.
> >
> > For a quick analysis of the snipplet you gave I would say
> > that the giving
> > away of the IP address fails or is late since the host is
> > still "0.0.0.0".
> >
> > Burkhard Weeber
> > viastore systems GmbH
> > P/O Box 300668
> > D-70446 Stuttgart
> > Tel: +49-711-9818-0
> > Email: B.Weeber at viastore.de
> >
> > Disclaimer:
> > The opinions expressed herein are my personal points of view
> > and do not
> > represent those of my employer.
> >
> > Windows95: <win-doz-nin-te-fiv> n.
> > 32 bit extensions and a graphical shell for a 16 bit patch
> to an 8 bit
> > operating system originally coded for a 4 bit microprocessor,
> > written by
> > a 2 bit company, that can't stand 1 bit of competition.
> >
> >
> >
> > > -----Original Message-----
> > > From: niblettda at gru.com [mailto:niblettda at gru.com]
> > > Sent: Monday, November 25, 2002 3:15 PM
> > > To: b.weeber at viastore.de
> > > Subject: RE: (ASCEND) Disconnect code 185, Progress 30 problem
> > >
> > >
> > > Burkhard,
> > >
> > > It takes 20 seconds from the time the call starts to when
> > > the TNT hangs up. I suppose that is could be too short, but
> > > that doesn't seem to be to me. Here is a chunk of syslog
> > > that I have on one of these calls.
> > >
> > > Nov 25 08:56:53 tnt2 1/17: [1/1/1/14] Incoming Call,
> > > 3523795987 [MBID 2214;
> > > 3523795987->3525821111]
> > > Nov 25 08:56:53 tnt2 1/17: [1/5/72/0] Assigned to port,
> > > 3523795987 [MBID
> > > 2214; 3523795987->3525821111]
> > > Nov 25 08:56:55 tnt2 1/17: [1/1/1/14] Call Connected,
> > > 3523795987 [MBID 2214;
> > > 3523795987->3525821111]
> > > Nov 25 08:57:16 tnt2 1/17: [1/1/1/14] Call Disconnected
> [MBID 2214;
> > > 3523795987->3525821111]
> > > Nov 25 08:57:16 tnt2 1/17: [1/5/72/0] Call Terminated [MBID 2214;
> > > 3523795987->3525821111]
> > > Nov 25 08:57:16 tnt2 1/5: [1/5/72/0] STOP: 'Answer'; cause
> > > 185.; progress
> > > 30.; host 0.0.0.0 [MBID 2214; 3523795987->3525821111] [Answer]
> > >
> > > Thanks!
> > >
> > > --
> > > David A. Niblett | eMail: niblettda at gru.net
> > > Network Administrator | Phone: (352) 334-3400
> > > Gainesville Regional Utilities | Web: http://www.gru.net/
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request at bungi.com
Archives: http://www.nexial.com/mailinglists/