mac@unison.com (Michael A. Casteel,,x219,) (06/15/91)
Having observed recent discussions regarding UUNET performance, I was interested to find several people mentioned UUNET connect failures. I certainly have my share of connect failures, ever since I started using UUNET. I attribute them to modem problems and wonder if anyone has knowledge/ideas of problems such as this: I am using v.32 (NOT Telebit) modems, Prometheus to be exact. By dint of disabling MNP and not trying to connect at 2400, I seem to get 50% to 100% success rate. Some days it connects every time, I mean; normally it takes several tries. Listening to the modem, and watching Uutry output, there seem to be two classes of problem: (1) UUNET's T2500 answers, pips PEP, peeps v.32, my modem starts shrieking back, shrieks for the full timeout and drops the line. (2) UUNET's T2500 answers, does the usual stuff, my modem gets carrier but I see a steady stream of garbage coming in; Uutry's output displays, oh, maybe 100 characters then announces 'enough already' and eventually gives up. More recently I acquired a v.32bis/v.42/bis modem at home and in a few minutes of experimentation have so far failed to connect with UUNET's modems AT ALL. I get symptom (1), where my modem just shrieks until I shut it off; no carrier, the speaker just stays on. I'll experiment more, disabling this and that, because I'm curious if my new modem will talk to T2500's AT ALL. Sometimes I get the feeling that one or two of UUNET's Mountain View, CA modems is misconfigured so my v.32 can't ever connect if it hits that one. I'd like to hear from anybody else who uses v.32 to UUNET, especially to the Mtn View modem pool. Especially if they can tell me something I have misconfigured on my end! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Mike Casteel Unison Software, Inc. mac@unison.com 675 Almanor Ave., Sunnyvale, CA uunet!hal822!mac +1 408 245 3000 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~