Newsgroups: comp.sys.mac.comm Path: utzoo!utgpu!cunews!bnrgate!bwdls61.bnr.ca!bnr.ca!bschmidt From: bschmidt@bnr.ca (Ben Schmidt) Subject: Re: MacTCP Conflict with Std TelNet? Message-ID: <1990Dec12.155113.10057@bwdls61.bnr.ca> Sender: usenet@bwdls61.bnr.ca (Use Net) References:<5346@crystal9.UUCP> <276511E7.3FF5@intercon.com> Organization: Bell-Northern Research Date: Wed, 12 Dec 90 15:51:13 GMT In article <276511E7.3FF5@intercon.com> kdb@macaw.intercon.com (Kurt Baumann) writes: > In article <5346@crystal9.UUCP>, derosa@motcid.UUCP (John DeRosa) writes: > > My Question: am I doing something wrong or is there a conflict? > > What is the exact nature of the conflict? > > The problem is that you will be able to use the NCSA telnet first and > then use whatever uses MacTCP second, but then will not be able to go back > to the NCSA telnet. The reason is that MacTCP does not release the card > totally. NCSA telnet does. Hope this helps? John, yah, it's a headache. :^( We treat it like this: Our users can run non-MacTCP or MacTCP telnet as they wish. But as part of the NetNewsReader install, we tell them convert to MacTCP telnet or don't bother with the newsreader install. Draconian, but sure simplifies things. :^) 'Course they can ignore this advice. If they have problems, we just tell them to reboot between MacTCP and non-MacTCP applications until they see the light and get arount to ensuring that all their IP applications are MacTCP based. Usually they see the light fairly quickly. :^) Since most of our Macs are currently on LocalTalk behind DDP/IP gateways, conversion to MacTCP is not as painful as it might be. We distribute a pre-configured and "protected" copy of MacTCP which works behind any DDP/IP gateway, with no user configuration possible or necessary. They drop this in their System Folder, reboot and fire up a MacTCP-based telnet. Ben Schmidt Bell-Northern Research, Ltd. Ph: (613) 763-3906 Information P.O. Box 3511, Station C FAX:(613) 763-3283 Technology Ottawa Canada K1Y 4H7 bschmidt@bnr.ca