Path: utzoo!utgpu!watmath!uunet!labrea!bloom-beacon!tut.cis.ohio-state.edu!osu-cis!att!ihlpl!ihchk!ihtlt!kosman!kevin
From: kevin@kosman.UUCP (Kevin O'Gorman)
Newsgroups: unix-pc.general
Subject: Re: 3B1 <=> Trailblazer
Keywords: Unix PC, ATT 3B1, Telebit Trailblazer
Message-ID: <499@kosman.UUCP>
Date: 13 Nov 88 02:15:06 GMT
References: <169@rtjpc.UUCP>
Reply-To: kevin@kosman.UUCP (Root)
Distribution: unix-pc
Organization: K.O.'s Manor - Vital Computer Systems, Oxnard, CA 93035
Lines: 17

In article <169@rtjpc.UUCP> jacob@rtjpc.UUCP (tom jacob) writes:
>My university has recently acquired a Telebit Trailblazer for its Vax
>11/780 (BSD 4.3).  It has no trouble talking to all of its connections
>EXCEPT my 3B1 (internal modem, 1200 baud).  When calling my machine, the
>Vax connects OK and logs in OK, but when it tries to "sendfile" it
>gets "pkcget: alarm #####" signals.
>
>I have heard that Unix PCs have trouble talking to Trailblazers.  Has
>anyone figured out how to solve this problem?

Yes.  I did several things, so I'm not sure exactly which ones are
essential.  The last thing I did before this started working was to
NOT lock the interface speed on the 'blazer.  You should also turn off
MNP recognition in the 'blazer, according to some mail I got, and I
believed it and did it.

There may be more, but those two seemed for sure.  Good luck.