Xref: utzoo comp.sys.novell:451 comp.dcom.lans:7117 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!mit-eddie!uw-beaver!milton!hayes.ims.alaska.edu!acad3.alaska.edu!jsdph From: jsdph@acad3.alaska.edu (HARRIS DENNIS P) Newsgroups: comp.sys.novell,comp.dcom.lans Subject: Re: Dialin service to Novell Server Message-ID: <1991Jan31.072910.4055@ims.alaska.edu> Date: 31 Jan 91 07:29:10 GMT References: <665164746@romeo.cs.duke.edu> <38655@cup.portal.com> Sender: usenet@ims.alaska.edu (J Random USENET) Reply-To: jsdph@alaska.edu Organization: University of Alaska Southeast Lines: 27 News-Software: VAX/VMS VNEWS 1.3-4 Nntp-Posting-Host: acad3.alaska.edu In article <38655@cup.portal.com>, AMillar@cup.portal.com (Alan DI Millar) writes... >Simple dial-in service is documented in the "Bridges" manual >for Netware 2.15. > >On your lan, you build an external bridge to receive calls. this method is a pain in the neck to install! the *simplest* method is to use carbon copy. this method can also provide good security, since carbon copy can be set for dialback if needed. carbon copy also provides better security since carbon copy will be required to access the dialin machine. you should make sure that users always log out before disconnecting, however. ccopy runs much faster than the bridge approach which can use an entire packet to send one character, and will want to load programs into your local cpu across the dialin bridge. unless you need to use a mouse, ccopy works fine for single dialin access. if you need multiple dilain access, take a look at the NACS multiple port board, reviewed sometime last summer in PC magazine's review of asynchronous communications servers... ================================================================================ dennis p. harris bitnet: jsdph@alaska.edu "The nation that controls magnetism controls the Universe." --- Diet Smith ================================================================================