Re: (ASCEND) Callback doesn't work if too quick (5.0A)

["John C. Day" <jcd@garlic.com>]

Ray, I've seen this for several releases on our Max 4000 (currently 
running 4.6Cp?), but I've been too busy/lazy to report and pursue it. 
 So, the good news is that you're not alone, the bad news is I don't 
know anything useful to tell you...

John Day, jcday@garlic.com

> To:            ascend-users@bungi.com
> Subject:       (ASCEND) Callback doesn't work if too quick (5.0A)
> Date:          Wed, 28 May 1997 14:06:21 +0200
> From:          Ray Davis <ray@carpe.net>

> We have a problem where some P50s set to callback can connect to our
> Max by itself with no problem, but when we dial it and it calls back
> we get a LAN security error.
 
<snip>
 
> If I initiate a call to the P50 using ^D 1 and then immediately
> kill it with ^D 2 before the callback comes it then there is no
> problem.
> 

> 
> Any ideas?  Is this a known problem?
> 
> Thanks,
> Ray
> ___
> Ray Davis                               carpeNet Information Technologies GmbH

> 
John C. Day,  Gilroy, CA  jcday@garlic.com
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.shore.net/~dreaming/ascend-faq>
or		<ftp://ftp.shore.net/members/dreaming/ascend-faq.txt>

---

References:

• (ASCEND) Callback doesn't work if too quick (5.0A)
• From: Ray Davis <ray@carpe.net>

---

• Prev by Date: (ASCEND) Ascend Max 4000
• Next by Date: Re: (ASCEND) P50/USR 2B aggravation
• Prev by thread: Re: (ASCEND) 56K Modem Throughput Degradation
• Next by thread: Re: (ASCEND) Callback doesn't work if too quick (5.0A)
• Index(es):
  • Main
  • Thread