NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/comp/dcom/modems/19759

Internet Message Format | 1993-01-21 | 1.5 KB

Xref: sparky comp.dcom.modems:19759 biz.comp.telebit:1143
Path: sparky!uunet!paladin.american.edu!news.univie.ac.at!hp4at!usenet
From: [e-mail] (Paul Gillingwater)
Newsgroups: comp.dcom.modems,biz.comp.telebit
Subject: Anguish with T3000 settings
Date: 21 Jan 1993 07:50:27 +0100
Organization: EUnet EDV Dienstleistungs GmbH A-1010 Wien Austria
Lines: 24
Message-ID: <[e-mail]>
NNTP-Posting-Host: hp4at.eunet.co.at

i am getting a few critical comments for recommending the purchase of 5
T3000 modems because they're pigs to set up.  I had a similar experience
four years ago with Trailblazers.

The problem is very simple -- they refuse to connect to certain V22bis
modems, with or without MNP enabled.  It's a bit embarassing -- one of
my colleagues has spent nearly two days working on configs.  We're using
a fixed DTE speed, and I've successfully connected to high speed
services (v32 and v32bis) with both MNP and v42bis.  I had it working
with the 2400 modems that we call, but then my colleague decided to
AT&F0 and start again, to make sure it was repeatable -- and now we
can't get the T3000 to talk to *any* v22bis modem.  It just fails to
sync.  What could we be doing wrong?

Is there some PAQ that shows nice detailed lists of standard settings --
the ones in the manual don't seem to work for us.

Also, we're planning to use this with cc:Mail -- which i note has
support for Trailblazers.

Thanks in advance!
--
Paul Gillingwater
Home system: [e-mail] (Waffle)