SYSDEH@SUVM.BITNET (Donald E. Hanley) (01/11/90)
>I am attempting to install an async external bridge in a Token-Ring LAN >running SFT 2.15 (IBM 4M AT Bus NIC's). As I read the instructions in >the Bridge Manual, I HAVE (?) to use a modem. I already have in place, >a campus wide network using the AT&T Information Switch which provides >me with 9600 baud access to 4 different hosts. I would like to use this >setup to connect a remote workstation through a external bridge to my >TR LAN. (This will be for demo's mainly in a lecture hall, and I know >that it will be slug-slow) > >It appears that I will be forced to use a modem which is not practical >in this particular case. Incidentaly, we presently have a BBS on the >AT&T switch and any PC can access it by using any of several communication >packages (ie, direct connect RS232c via the COMx ports) > >Q1. Is there a way around the mode requirement (ie, using special con- > figuration, auto-connect, etc? You don't need a modem. Use special connection, auto-connect. De- pending on how your A&T data switch works, this may or may not cause you a problem, because the bridge software won't return the port to the data switch when the user LOGs out or hangs up. Our data switch is configured so that it forces a disconnect if the user hangs up or, alternatively, sends two breaks in succession; thereby freeing up the port for another user. >Q2. Will an ansyc board work or can I convince the bridge that the COM1 > port is an async board? You can use COM1 and/or COM2. >Q3. Will the sun come up in the west tomorrow and I will have been visited > by elves who ran ARCONFIG during the night and now everything works > just fine? (No, don't answer that, I must have really been dreaming) It really does work. Watch out for the following gotchas, however: a) When you run BRGEN, make sure you set the network addresses AFTER linking. b) If you use the venerable, old PC (what else do you do with these retirees), remember that it can't handle more than 9600 baud. c) Access through the asynch port is SLOW! However, you can speed things up considerably if your client station has a hard disk on which you can install the often-used network files, DOS, etc. Actually, if you use some care when setting up your search list in the LOGIN script, you can make a dual 1.44MB floppy client run acceptably.