kenw@duke.cs.duke.edu (Ken Weaver) (01/29/91)
I have been asked to set up dialin service to our novell network. Could someone please E-mail me with suggestions. Thanks in advance Ken Weaver Operations Manager Library Systems Duke University Kenw@mail.lib.duke.edu
AMillar@cup.portal.com (Alan DI Millar) (01/30/91)
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. There is built-in support for using Hayes-type modems on COM1 or COM2. You configure an external bridge with one or more lan cards. You also configure a lan adapter using the Novell-supplied driver that says "IBM Async COM1 and COM2". After the BRGEN, you use a separate program called ARCONFIG to configure the port's baud rate, etc. On the machine that will dial in, you use SHGEN to create an IPX with the "IBM Async COM1 and COM2" driver. You then use ARCONFIG to configure the IPX with the phone number of your external bridge, etc. When you run IPX on the workstation, it will dial the phone and connect you to the bridge. You then run NET3 (or 2 or 4) and you are connected to a server! Access is somewhat slow at 2400 baud. The best thing to do is to put commonly used commands, such as LOGIN and MAP, on the workstation to speed things up. However, I just tried it last week and it works. There are other approaches, like PCAnywhere, but they aren't using the power of your machine at home. With this approach you can even link TWO BRIDGES for remote lan interconnection! - Alan Millar AMillar@cup.portal.com
john@mantis.co.uk (John Brimacombe) (01/30/91)
kenw@duke.cs.duke.edu (Ken Weaver) writes: > > I have been asked to set up dialin service to our novell network. > Could someone please E-mail me with suggestions. > There are essentially 2 types of solution. The first involves having an extra machine with modem on the network. This runs a program like Carbon Copy or PC-Anywhere. The remote user must also have a copy of the package and a modem. He then dials the host machine, and establishes a link. Essentially. keystrokes and screen updates are exchanged. The problem with this is that you end up using 2 machines for 1 session. The alternative solution is products along the line of one produced by Novell. This consists a unit containing a number of modems and a 386 machine which can emulate multiple 8086 sessions. For a large number of connections, this is a tidier solution. I beleive that you can also use a pd package like PC-PLUS at the remote end.
jsdph@acad3.alaska.edu (HARRIS DENNIS P) (01/31/91)
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 ================================================================================