RE: Trumpet WINSOCK

Gerry Freymann (freymann@eagle.ca)
Thu, 20 Jun 1996 16:22:23 -0500

> After aproximately 250 users, I've recently had a few occasions where
> trumpet 2.0b (which works 100% for the last 245 users) decides that
> it will not negotiate the connection for PPP. (I am not using pap)
> Upgrading to 2.1f didn't solve anything, the problems were the same..
> What appears on a PMWHO when this 'bad-trumpet' is playing its tune is
> CONNECTING... it does that for 30 seconds, then disconnects..

We get that here all the time. The clients call and complain and we
don't know what to tell them but to hang up and try again! As with
you, clients using winsock 2.1f don't fair much better. We've
upgraded the portmasters to cmos 3.3.1.c1 and that didn't make it go
away, and this week we upgraded the flashrom in the multitech modems
and still it's here.

In addition to the no ip problem, we also suffer from disconnects.
Yesterday a user with a USR Sportster 28.8 and a Prac.Periph. 28.8
couldnt stay on the line for more than five minutes.. he finally gave
up... but had the same problem this morning. He then calls at 1pm to
say he's been online for 30 minutes and is very happy! We haven't
done anything here...

I have the debug thing on in the portmasters hoping the logoff cause
line in the radius logs would help. This is a typical grep result:

Acct-Terminate-Cause = User-Request
Acct-Terminate-Cause = User-Request
Acct-Terminate-Cause = Lost-Carrier
Acct-Terminate-Cause = Lost-Carrier

We get far more "Lost-Carrier" messages than I think should be
normal <g>