🚀 go-pugleaf

In message <322E0545.2A94@iserv.net> - Bill <wott@iserv.net> writes:
>Ray Todd Sevens wrote:
>> Bottom line on 802.3 is that if you plan to use any other protocol    > besides ipx in your organization at anytime now or the future, don't  > use it.
> 
>Would you mind elaborating on this?
>We run IPX on 802.3 and IP on Ethernet_II to Netware 3.12 and 4.1 boxes
>with very good results...
>
>-- 
>Bill Ott			|	
>wott@iserv.net			|	
>dawgman1@ix.netcom.com		|

My preference is to use 802.2 for IPX.  Among other reasons, the most
practical is the most convincing:

Since 802.2 has been the default frame type since NetWare 3.12, most 3rd
party vendors are making it the default on their products (e.g. print
servers and cd-rom servers).  The servers tend to be more static (ie. on
larger networks you don't add servers as quickly as you add printers) so
anything that reduces steps is good (that is, you don't have to change
the frame type from .2 to .3 on new devices).

I usually recommend that both frame types get run on the network (.2 & .3)
and users be switched over gradually.  Yes this increases traffic, but on
large networks where 802.3 is being loaded 1st on the workstations, it
can be a difficult task to update users.  If you do visit each desktop to
make the change rather than automating the net.cfg update, consider up-
dating the drivers at the same time.

brian

***************************************
* Brian Helman        617.895.1324    *
* IBM/Boston                          *
*                                     *
***************************************
* Opinions expressed are mine.  My    *
* employer would not want them        *
* (unless they are really REALLY      *
* good!!)                             *
***************************************