Re: (ASCEND) Immediate Disconnects

["Greg Martin" <greg@earth1.net>]

Happens with Windows95,  Windows98 and 3COM OfficeConnect
LanModem.


> Is this a Windows 95 client?  If so, what version of the MS Dial Up Adapter 
> is being used.  There used to be a problem with early versions of MSDUN 
> where the IP address was not being released.  Microsoft came out with a fix 
> (a patch) that fixed this problem but, since then, MSDUN 1.3 was also 
> released which, supposedly, also fixes the problem.
> 
> My recommendation is for the user to upgrade MSDUN to 1.3 and try again.
> 
> Mitch
> -------------
> Original Text
> From: "Greg Martin" <greg@earth1.net>, on 6/2/99 6:11 PM:
> To: SMTP@DC2@OCC["Ascend Users" <ascend-users@bungi.com>]
> 
> If the user shuts down their system (power off, warm boot doesn't work)
> they can then get connected.  I have tracked the problem down to
> an ip address already in use.  It is looks as though the user is trying
> to login with a static address and if it is used it kicks him off.  But I
> have duplicated the problem and this is not the case.  The system
> is acting like the ip is static.  If it is in use it kicks the user off, if 
> it
> is free
> it let's them on as below.  Lets them use a different ip than what
> is being assigned from the pool.  Can't figure out why a user
> system shutdown corrects the problem.
> 
> PPPIF-34: bypassing async layer
> PPPIF-34: Link Is up.
> PPPIF-34: pppMpNegUntimeout last 0 layer 0
> PPPIF-34: pppMpNegUntimeout last 0 layer 0
> PPPIF-34: LCP Opened, local 'Answer', remote ''
> PPPIF-34: _openAuthentication
> PPPIF-34: pppMpNegUntimeout last 0 layer 1
> PPPIF-34: Auth Opened
> PPPIF-34: Remote hostName is 'scsb'
> PPPIF-34: CBCP Opened
> PPPIF-34: pppMpSendNeg Pkt
> PPPIF-34: pppMpNegTimeout layer 4
> ../pppif.c:1154 - 34 ppp is b033e5c0, aysnc is 1, syncAsync is 0
> PPPIF-34: using address from pool 0
> PPPIF-34: Allocated address [208.157.7.230]
> PPPIF-34: opening IPNCP: 208.157.7.11 -> 208.157.7.230
> PPPIF-34: pppMpSendNeg Pkt
> PPPIF-34: pppMpSendNeg Pkt
> PPPIF-34: pppMpNegTimeout layer 4
> PPPIF-34: pppMpSendNeg Pkt
> PPPIF-34: pppMpNegUntimeout last 0 layer 4
> PPPIF-34: pppMpNegUntimeout last 0 layer 4
> PPPIF-34: IPNCP Opened to 208.157.7.207
> PPPIF-34: Freed address [208.157.7.230]
> 
> 
> > Are any of the users experiencing the disconnects able to connect some of
> > the time or do they always get disconnected?
> >
> 
> >
> >
> > >Recently I have noticed (and received complaints) about users getting
> > >disconnected
> > >immediately after connecting.  I can watch my radius diag and see the
> > >authorization
> > >go ok but then they get disconnected before the accounting packet ever 
> gets
> > >sent.
> > >
> > >I thought this may have been with 7.0.4 (ftik.m40) so I returned to 
> 7.0.1
> > and
> > >still have the
> > >same problem.  The only difference  i know of is I have more ISDN 
> customers
> > now.
> > >
> > >I remember something months ago about a problem with ip address' not
> > getting
> > >released
> > >on ISDN calls.  Does anyone remember if this is the problem it caused?
> > >
> > >Wasn't this problem suppose to have been corrected?   I only have 3 more
> > ip's in
> > >the
> > >pool than modems.
> > >
> > >What is the best way to check to see if lack of ip's is the problem?
> > >
> > >Greg Martin
> > >Planet Earth Internet
> > >greg@earth1.net
> > >
> > >++ Ascend Users Mailing List ++
> > >To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> > >To get FAQ'd: <http://www.nealis.net/ascend/faq>
> > >
> >
> >
> 
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>
> 
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>