> On Mon, 25 Aug 1997, Jordan Mendelson wrote:
>
> >Using the command:
> >
> >asyncmap 0x00000000
> >
> >Fixes basically everything. The file now downloads at 10.54 K/s, I have very
> >few slowdowns whatsoever.
>
> I posted a message to this effect 2 days ago. I wonder if improper
> asynch control maps might not be causing more retrains and disconnects
> than having a less than stellar modem on the client end.
If that's the case, is this something fixable? I noticed this:
Active Configuration Default Configuration
-------------------- ---------------------
Port Type: Netwrk Netwrk (Dial In) (Security)
Baud Rates: 31200 64000,64000,64000
Flow Control: RTS/CTS RTS/CTS
Modem Control: on on
Remote Host: ppp1.nuc.net
Netmask: 255.255.255.255 0.0.0.0
Interface: ptp5 (PPP,Quiet,VJ-Comp)
Mtu: 1500 1500
Async Map: L:00000000 R:000a0000 00000000
Dial Group: 0
when I dial in with Win95 ... The R:000a0000 I assume is from the Win95
machine? I've noticed the same on all the other connections I just
tested.
Now, Personally I've never had a connection problem, even with the new
cards. Some of my customers are (I'm trying to get a list of models and
firmware revisions from all of them) and if this is causing a problem, it
would be great to see if there's a fix.
Looking at it deeper, the async map is turning off CTRL-S and CTRL-Q,
which are XON/XOFF ... Could software flow control be confusing something
somewhere? That would certainly cause the modem to simulate a "lockup",
which is what causes the eventual "Call Circuit Disconnect" to show up.
Jaime Bozza
Nucleus Communications, Inc.