This problem is VERY repeatable, and is ALMOST ALWAYS resolved by
disconnecting and reconnecting. Occasionally, hoever, the entire Win95
stack stops working and has to be un/re installed.
Just my $.02.
On Sun, 27 Apr 1997, Nick Johnson wrote:
> On Sat, 26 Apr 1997, Sherwood Pekelo wrote:
>
> > can you ping them? What are they using? What ComOS do you have? What
> > product are you using PM2 or PM3 or other?
>
> That's what I've got to find out. I've got a few users with
> instructions to call me immediately the next time it happens, and then
> I'll find out. This has happened periodically with ComOS 3.3.1, 3.3.3,
> and now 3.5 (all our PMs are 3.5 now). There was an apparent increase in
> complaints with the 3.5 upgrade, but I can't be certain that actually
> means anything. I haven't heard anyone complain of this on a PM3 yet,
> and so far all the complaints have been about PM2e-30s.
>
> > Yes, people have had different problems... mines is a user's Supra getting
> > disconnected to a PM3 with ComOS 3.5.1b8... can't follow up on this yet,
> > until I contact the user and have him bring in the modem...
>
> I've found that Supras are excellent modems... at least the Supra
> Faxmodem is. I think two of the users that are having problems are
> using Maxtechs. I've tried about everything I can think of... most
> recently I had the user try an init string that would turn off retraining
> and auto fallback/forward with the idea in mind that the modems were
> attempting to retrain and failing forever.
>
> Nick
>
> ---
> Nick Johnson, writer of code, fixer of modems
> Gulf Coast Internet Systems Engineering Team
> Check the web: http://www.gulf.net/support/network_status/
>
>
-- Neal Rigney, PERnet Communications, (409)729-4638 neal@mail.pernet.net "I've seen better bandwidth between two gorillas with flash cards!"