Path: utzoo!news-server.csri.toronto.edu!rutgers!ucsd!sdd.hp.com!caen!sol.ctr.columbia.edu!emory!gatech!prism!gs26
From: gs26@prism.gatech.EDU (Glenn R. Stone)
Newsgroups: comp.dcom.modems
Subject: Re: MultiTech MultiModem V32 & T2500
Keywords: MultiModem V32, T2500
Message-ID: <24266@hydra.gatech.EDU>
Date: 13 Mar 91 19:34:17 GMT
References: <148@ipars.UUCP> <408@frcs.UUCP>
Organization: Dead Poets Society
Lines: 22

In <408@frcs.UUCP> paul@frcs.UUCP (Paul Nash) writes:

>Thus spake scotto@ipars.UUCP (Scott O'Connell):

>> I have just taken over a network with several MultiTech MultiModem V32
>> modems.  I have been using Telebit T2500's and now need to make the two
>> flavors of V32 talk consistantly.

>I have had a similar problem, and found that the only way to make the
>MultiTech talk to the TB reliably was by disabling MNP (error correction
>_and_ compression) on the TB.  Like this, it works fine.

You can set S106, S97, and S95 on the T2500 to toggle the negotiation
of LAP/M and MNP.  If the Multitech has V.42 LAP/M, you may want to 
set things up so that only LAP/M is used.  (I've found I have to do
the opposite (i.e. set for MNP only) when calling a Microcom modem
from my T2500.... the Microcom gets real confused when it hears the 
T2500 try to negotiate LAP/M...)  See the Release 7.00 Addendum to 
TFM for details.  

-- Glenn R. Stone
gs26@prism.gatech.edu