> 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.
Just a reply to my own message. FreeBSD routers and WinNT servers I
have online right now do not have that async map. Both maps on these
connections are 00000000.
Thus far, none of my dedicated customers have complained.
Jaime Bozza
Nucleus Communications, Inc.