[comp.sys.dec] TOKEN RING VS ETHERNET

loethen@psp.psp.com (10/24/90)

X-NEWS: psp comp.dcom.lans: 425

GREETINGS TO ALL ON THE NET.  

FIRST, PRELIMINARIES.  I AM POSTING THIS TO COMP.SYS.DEC,COMP.PROTOCOLS.TCP-IP, 
& COMP.DCOM.LANS. OUTSIDE IF THAT, CROSS-POST TO WHAT EVER YOU THINK MIGHT BE 
HELPFUL.
ALSO, PLEASE ANSWER VIA EMAIL.  MY NEWS FEED IS SPOTTY AND OCCASIONALLY 
UNRELIABLE.


I HAVE HELPED SPECIFY AND TEST A ETHERNET - TCP/IP NETWORK TO PROVIDE
BROADBAND CONNECTIVITY FOR A DEPARTMENT CONSISTING OF DEC (WORKSTATIONS, 3100
AND 3800), TANDEM AND PCS (AT AND MC BUS).  AS WE HAVE COMPLETED THE TESTING
OF THIS SYSTEM AND WERE MAKING PREPERATIONS TO PURCHASE SAID HARDWARE AND 
SOFTWARE, OUR CORPORATE SUPPORT GROUPS HAVE ASK US TO RE-EVALUATE OUR DECISIONS
AND ANALYZE WHAT IT WOULD TAKE TO MAKE THIS A TOKEN-RING NETWORK INSTEAD 
(RUNNING NOVELL ON THE RING FOR PCs).


SOME FACTS:

WE NEED FILE SHARING, REMOTE LOGIN, REMOTE BACKUP, PRINTER SHARING, TERMINAL
EMULATION (OBVIOUSLY) AND EVENTUALLY, REMOTE PROCEDURE CALLS.

THE COMPANY GOAL IS TO MIGRATE TO OSI

THERE ARE ALREADY TWO LARGE (75-100) TOKEN RINGS IN THE COMPANY, RUNNING NOVELL
AND PROVIDING CONNECTIVITY FOR PC TO THE IBM MAINFRAME.


QUESTIONS:

IS THIS A VIABLE SOLUTION (USING TOKEN RING)?  HOW MIGHT IT BE DONE?

IF T/R IS NOT A BETTER SOLUTION, WHAT ARE SOME REASONS THAT MIGHT SUPPORT THE
ETHERNET TCP/IP SOLUTION?



I HAVE DONE SOME CHECKING INTO THIS, OF COURSE, BUT I COULD USE SOME FEEDBACK
ON DIRECTIONS OR ALTERNATIVES I HAVEN'T THOUGHT OF YET.

THANKS AGAIN. 



-- 
*******************************************************************************
* Shelly Loethen		*  "Only By Attempting the Absurd,	      *
*                       	*        Can We Achieve the Impossible"	      *
*=============================================================================*
* ...uunet!amgraf!brian386!swl386!shellyl // loethen@psp.psp.com	      *
*******************************************************************************
* Disclaimer:  "My opinions are my own, thank you!"			      *
*******************************************************************************