HDTenEightyP/NetNews huggingface dataset:
From: seifert@netcom.com (Rich Seifert)
Subject: Re: Bridge/switch/router for multicast addresses?
Date: Mon, 14 Sep 92 16:40:31 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Keywords: multicast

In article <1992Sep11.021850.5029@monu6.cc.monash.edu.au>, shall@fawlty1.eng.monash.edu.au (Dr SC Hall) writes:
> I am developing a conferencing application on Ethernet, and want to
> make use of the multicast (as distinct from broadcast) addressing
> feature.  A problem arises when I want to work across more than one
> Ethernet segment, because the bridge/switch/router needs to be able to
> interpret these addresses.  I have been unable to get an answer out of
> local vendors as to how their products treat multicast addresses.
> Therefore, my question is: Does anyone know of an Ethernet
> bridge/switch/router which CAN handle multicast addresses?  
>

By default, all bridges will forward all multicast traffic. This would
allow your application to operate successfully (assuming that the
bridge latency is acceptable). Many bridges can be programmed to
BLOCK specified multicast addresses; this is sometimes useful for
segmenting traffic.

Routers will effectively block ALL multicast data link addresses. There
are multicast mechanisms available at the network layer (in IP, at least)
but few routers today can make use of these.
 


-- 
Rich Seifert                    Networks and Communications Consulting
seifert@netcom.com              (408) 996-0922
                                (408) 996-2860 FAX
"... specialists in Local Area Networks and Data Communications systems"
Newsgroups: comp.dcom.lans.ethernet
From: nolan@tssi.com (Michael Nolan)
Subject: Re: LANtastic network cards
Reply-To: nolan@tssi.com
Organization: Tailored Software Services, Inc.
Distribution: usa
Date: Thu, 10 Sep 1992 21:11:02 GMT

brettw@matt.ksu.ksu.edu (Brett D. Watson) writes:

>  Anyone know off the top of their head:

>  Can I use ANY ethernet card with Lantastic or are the cards vendor
>specific?  I'm assuming from the older cards we have that they must
>come from Artisoft.  I thought they must be different network cards
>since it's a peer-peer network op system.

The answer is yes, sort of.  There are actually two compatible versions of
LANtastic.  One is 'LANtastic' and uses Artisoft's NIC's.  The other is
'LANtastic/AI' [Adapter Independent] and supports non-Artisoft NIC's, such as 
WD8003's.  It used to support more thinnet cards than it did 10Base-T cards, 
but that may have changed by now or you may be able to find LANtastic-compatible
3rd party drivers.  Check with Artisoft or a LANtastic dealer to find out
exactly what 3rd party cards are currently supported.

You can have a LANtastic network with both Artisoft and non-Artisoft NIC's on 
it, but you need to install the appropriate version at each workstation.  The
kicker is that LANtastic is licensed on a per-network basis (up to 300 nodes,
I think) and LANtastic/AI is on a per-station basis.  In short, you can pay
them for the NIC or you can pay them for the network software. 
---
Michael Nolan, nolan@tssi.com      "Freedom of the press is still alive in    
Tailored Software Services, Inc.    America, at the U. S. Mint"  (Gallagher)   
Lincoln, Nebraska (402) 423-1490  
Newsgroups: comp.dcom.lans.ethernet
From: gary@sci34hub.sci.com (Gary Heston)
Subject: Re: ThickWire repeaters...
Reply-To: gary@sci34hub.sci.com (Gary Heston)
Organization: SCI Systems, Inc., Huntsville, Al.
Date: Tue, 8 Sep 1992 18:51:18 GMT

In article <PIM.92Sep4140823@diana.fct.unl.pt> pim@fct.unl.pt (Joao Paulo Pimentao) writes:
>
>We are considering using thick wire ethernet to connect two buildins
>on our campus. Later on we are going to replace it by fiber optics;
>but the easiest way and the fastest for us presently is to create a
>thick wire connection.

Be aware that all coax can suffer from lightning strikes and ground
loop problems. If at all possible, interbuilding links should be fiber.

>Our thick wire cable may be near the maximum lenght that I believe is
>1 km.

You can run thick for 1000m as a point-to-point link; that means you'll
have to have a bridge between each end of this link and your building
networks.

>Could you please help me sugesting the best way to extend it.

Fiber. Start with it, and save the expense of changeover (at $1.80US/m,
plus transceivers, you're talking about a fair amount of money to 
pitch when you change. If you don't need full bandwidth and want to 
avoid spending lots of money right now, set up a pair of async bridges.

>I think I can use repeaters to enlarge it with another km or so. Is
>this true? Could you point me to some repeaters?

No, the total link separation between two transceivers cannot be over 
1500m, with a maximum of two repeaters in the path. If you use bridges
instead of repeaters, that's a different matter.

The above is based upon the Ethernet Version 1.0 document, section 7.1.5.

-- 
Gary Heston    SCI Systems, Inc.  gary@sci34hub.sci.com   site admin
The Chairman of the Board and the CFO speak for SCI. I'm neither.
    The most dangerous person in the world is Jessica Fletcher.
        Everywhere she goes, people die.
Newsgroups: comp.dcom.lans.ethernet
From: dazz@monu6.cc.monash.edu.au (Mr D.K. Woodman)
Subject: 10Base-T over STP type 1
Organization: Monash University, Melb., Australia.
Date: Sun, 6 Sep 1992 03:32:40 GMT

Can anyone tell me from personal experience what, if any, problems they
have running 10Base-T over standard IBM type 1 (STP) cable.

Does it still conform to the UTP standard of 100 metre lobe lengths?
Does the lobe require any line balancing equipment?

If I use a modern intelligent hub with signal re-generation are there
any possible problem areas to be aware of?

I am about to implement a lan using already installed STP but due to the 
high costs of network cards I am considering going ethernet instead of 
token ring and whilst the hub vendors assure me that I won't have problems
using existing STP cable I would like some "real world" opinions.

any replies appreciated
thanks
dazz
From: turner@ctron.com (David Turner)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: cascading multiport repeaters
Date: 11 Sep 92 15:47:39 GMT
Reply-To: turner@olympus.ctron.com (David Turner)
Organization: Cabletron Systems INc.

In article <1992Sep9.130247.23082@mercury.ncat.edu> lazarea@mercury.ncat.edu writes:
>i have a thickwire network with six transceivers connected to it. on
>each transceiver i have a multiport transceiver. three are dec, three
>are cabletron.
>
>what would be the advantages or disadvantages of cascading the multiport
>transceiver off of one single port tansceiver. or maybe cascading three
>multiport transceivers off of two single port transceivers.
>
>any thoughts would be appreciated. i am reading up on it but i do like
>to hear from real people with real networks :-)
>
>andy
>
>
>-- 
>Andy lazare                  internet  lazarea@garfield.ncat.edu
>n.c. a&t state univ                    lazarea@mercury.ncat.edu
>greensboro, n.c.             bitnet    lazarea@atsuvax1.bitnet
> 

The advantage of cascading off of one single transceiver into one multiport
transceiver box is that you get more devices connected to the backbone at
a single point.  

The disadvantage is that you loose 10 meters of AUI drop cable length per
multi-transceiver box.  This will limit the AUI drop cable run.  You must
add up the cable lengths and not exceed 50 meters for standard AUI drop
cable.

You can only cascade two multi-transceiver boxes off of one single transceiver
on the thicknet backbone.  More than that will cause JITTER.


-- 
-------------------------------------------------------------------------------
David P. Turner         Internet: turner@ctron.com
Cabletron Systems Inc.  Compuserve: 76702,1733
Voice: (603) 335-9400   E-mail Cabletron Support Internet - support@ctron.com
Newsgroups: comp.dcom.lans.ethernet
From: matcsp@nuscc.nus.sg (Chan Shih-Ping)
Subject: HELP: `Multiplexing' 10Base-T - is it possible?
Organization: National University of Singapore
Date: Thu, 10 Sep 1992 00:11:10 GMT

I have an office with just *one* 10Base-T outlet to a wiring hub which I do
not have access to.  However I have two computers in the room each
with a twisted pair nic (3COM etherlink II/16T if it matters).

Is there such a thing as an inexpensive  hub which will allow
me two connect the two computers and then connect itself to the
single outlet.  Is this `daisy chaining`, `multiplexing` or
`cascading` or what?  I am a novice to 10Base-T so I do not know
what wiring is or is not possible.

Thanks --
Shih-Ping Chan
Dept of Mathematics
National University of Singapore
matcsp@nuscc.nus.sg
From: mike@elec.canterbury.ac.nz (Cosmik Debris)
Newsgroups: comp.dcom.lans.ethernet
Subject: 802.3 and EthernetII yet again
Date: 10 Sep 92 03:37:43 GMT
Organization: Electrical Engineering, University of Canterbury, New Zealand

On our campus we run EthernetII and 802.3 (netware) on the same LAN. I read in
Novell documents it wasn't a good idea to run the two together. I have noticed people in this group and comp.sys.novell saying the same thing. Being a good soul I changed my novell servers to EthernetII. Some of the other servers on campus are still 802.3. I have never noticed a problem running the two together. What is the problem? Can someone give a good reason for all the other Novell servers to change?
-- 
*******************************************************************************
*  Mike Shurety                           mike@elec.canterbury.ac.nz          *
*  Computer Systems Manager               psi%(5301)30000012::mike            *
*  Electrical & Electronic Engineering    FAX        : (64) (3) 642-761       *
*  University of Canterbury               Phone work : (64) (3) 642-295       *
*  New Zealand                            Phone home : (64) (3) 891-629       *
*                                                                             *
*                      "I owe money, therefore I am"                          *
*******************************************************************************
From: nolan@tssi.com (Michael Nolan)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Can Token Ring wire be used for 10BaseT?
Date: 9 Sep 92 17:31:35 GMT
Reply-To: nolan@tssi.com
Organization: Tailored Software Services, Inc.

perl@dwrsun4.UUCP (Robert Perlberg) writes:

>Our building is wired for token ring.  Each office has a box with two
>connectors on it.  One is an RJ45 modular connector used by the Centrex
>phone system (you plug your phone into it).  The other is (sorry I
>don't know the official designation) a big approx. 1 inch square four
>conductor connector used for our token ring PC LAN.  In the
>communications room there are cables which are terminated in these
>square connectors each of which corresponds to an office and the ones
>which come from offices with PC's get plugged into a MAU.

>My question is, can this wiring be used for Twisted Pair Ethernet?  Can
>I make (or buy) an adapter that will connect an RJ45 to a token ring
>connector and use the existing building wiring for 10BaseT?  (With, of
>course, appropriate 10BaseT transceivers in the offices and 10BaseT
>hubs in the communications room.)

I think it must be possible, because my son is in Donner hall at Carnegie-Mellon
and the building apparently was originally wired for token ring but later
converted to 10Base-T.  They sell a token-ring-to-10Base-T cable for
around $30 which plugs into the IBM Token Ring jack in the dorm room,
has some kind of balun or transformer on it, and an RJ45 cable which goes
into the RJ45 jack on the 10Base-T NIC.  (I saw LatticeNet equipment in the 
wiring closet in the basement, if that means anything.)

(At last report my son isn't up and running yet, so I don't know any 
additional details, but maybe someone at CMU can contribute further, to 
enlighten both Mr. Perlberg and me.)
---
Michael Nolan, nolan@tssi.com      "Freedom of the press is still alive in    
Tailored Software Services, Inc.    America, at the U. S. Mint"  (Gallagher)   
Lincoln, Nebraska (402) 423-1490  
Newsgroups: comp.dcom.lans.ethernet
From: skipm@dorsai.com (Skip Mac-Stoker)
Subject: Cabling Specifications
Organization: The Dorsai Embassy +1.718.729.5018
X-Newsreader: Tin 1.1 PL4
Date: Wed, 9 Sep 1992 05:49:48 GMT


Newsgroups: comp.dcom.lans.ethernet,comp.dcom.fax
From: iskandar@nynexst.com (Sam Iskandar)
Subject: Recommendation on Fax server
Reply-To: iskandar@nynexst.com
Organization: NYNEX Science & Technology, Inc
Date: Mon, 14 Sep 92 18:51:00 GMT

Hi there,

I have been asked to setup a Network Fax server on our network. We're running
TCP/IP over Ethernet, with Sun workstations, some PCs and MACs. Do you have any
recommendations ? Do you have any experience with a product that you were
satisfied with ? Please keep in mind that in addition to supporting the Sun
users, I would like the PC and MAC users to be able to use the product too.

Any info would be helpful.

Pls e-mail me directly, and I'll post summary on the net.

Thanks

Sam
---
============================================================
Sam Iskandar - MTS             E-mail: iskandar@nynexst.com
Nynex Science & Technology     Phone:  (914)644-2548
============================================================

Newsgroups: comp.dcom.lans.ethernet
From: hshamans@magnus.acs.ohio-state.edu (Harry T Shamansky)
Subject: Help with TCP/IP transfer from a PC to Unix Workstation
Keywords: tcp/ip, network, pc to unix
Organization: The Ohio State University
Distribution: comp.dcom.lans.ethernet
Date: Fri, 11 Sep 1992 20:04:40 GMT



   Hello...

   Sorry if this is not the correct group to post to,
   but we're pretty sure this is a general question
   that many people have probably covered before...

   We are looking for any example software that would
   help us send and receive tcp/ip packets to/from
   a unix workstation.  We hope to find examples that
   would help us format up packets similar to telnet
   or ftp or finger etc. (we know what the details
   of the packet are, from Comer's book). We need to
   send/receive data via ethernet to a unix workstation 
   from our program(s) on the pc.

   BTW: We have *all* the sources to the NCSA packet
   driver information; but it looks like a huge effort
   to extract out the key parts we really need to do
   our task.

   Any help or pointers would be most appreciated....
   Post or e-mail will be fine, we will summarize if
   there is interest.

   thanks

   Harry Shamansky, hts@hertz.eng.ohio-state.edu
   WeiHung Lin, whl@gauss.eng.ohio-state.edu
From: pat@hprnd.rose.hp.com (Pat Thaler)
Date: Fri, 11 Sep 1992 00:34:44 GMT
Subject: Re: Ethernet CRC/Alignment errors
Organization: HP Roseville Networks Division
Newsgroups: comp.dcom.lans.ethernet

    > Unfortunately, repeaters do not check the CRC of received packets,
    > and simply pass them through. (By the time the CRC comes by, the packet
    > is through anyway!). 

    I was afraid of that. I don't have control of the entire campus ethernet
    :-(. Another helpful reader suggested that they may be caused by IBM
    RS/6000 machines, of which there are a few on campus, "dribbling" extra
    bits at the end of some packets. Anybody else out there running RS/6000s
    and NOT seeing CRC/Alignment errors? I'm guessing the errors are more
    "Alignment" than CRC - they seem quite short, and the data insiode is
    totally random.

Repeaters do not reject or mark a packet as having CRC errors.  Repeaters
with management often do count the number of packets received with CRC
errors.  

Since you say the bad packets are very short (I assume near
minimum frame size) it is possible that the network has been allowed to
grow to large so that collision fragments are sometimes longer than
the minimum frame size.  Depending on where you are observing the network,
you analyzer might not detect the occurance of the late collision, but 
fragments greater than minFrameSize would be detected and counted as
CRC/Alignment errors.

Pat Thaler
Newsgroups: comp.dcom.lans.misc
Subject: Re: Lan Manager/Novell modem link?
From: Aengus Lawlor <RBYAML@rohvm1.rohmhaas.com>
Date: Tue, 15 Sep 1992 13:06:59 EDT
Organization: Rohm and Haas Company

In article <BuJIr4.8qA@news.cso.uiuc.edu>, gill@eagle (Warren Gill) says:
>
>bob@comlab.gatech.edu (Bob Baggerman) writes:
>: With LAN Manager 2.1 Microsoft provides an IPX/SPX interface for your
>: Novell redirector and stack to use along with the LAN Manager stack and
>: redirector.  It probably takes up a bit of memory when you get them all
>: loaded but NDIS 2.0 supports dynamic loading and unloading of protocol
>: stacks drivers can be moved in and out of memory as needed.  I haven't
>: actually tried it.  I generally try to avoid Novell.  But it looks pretty
>: simple from the installation documents.
>
>  I have NETBEUI, TCP/IP, an NDIS<->Packet "shim", and NDIS<->IPX drivers
>running on one PC. They all Work!  Netware Connectivity package from Microsoft
>is easy to install, and easy to use (just type 'NWLOAD' and the driver
>loads, and you LOGIN to Novell - type 'NWUNLOAD' to unload the drivers when
>you are done).  Also, if the installation detects a copy of MS Windows, it
>loads network drivers which allow you to logon and connect resources from
>within Windows!  For example, "Connect Net Drive" in file manager prompts
>you for "NetWare" or "LAN Manager".   Neat!
Tell me more! Is this for DOS? Is it just called Netware Connectivity?
Will it work with PathWorks which is (kinda) LanMan based? Where do I get
it, and how much does it cost?

>--wg
Aengus
--
RBYAML@ROHMHAAS.COM                    Aengus Lawlor
RBYAML@ROHVM1.BITNET                   (who used to be ALAWLOR@DIT.IE)
"How about some of that famous Dublin wit, Barman?"
"Certainly, sir. Would that be Dry or Sparkling?"
Newsgroups: comp.dcom.lans.misc
From: rob@nike.ct.louisville.edu (Rob Miracle)
Subject: Lan Installation Times
Date: Thu, 10 Sep 1992 21:02:26 GMT
Organization: Information Technology, University of Louisville

This is going to really only be practical to Universities, but others are 
just as welcome to respond.

A committee that I am on is wanting to benchmark our installation times 
against other sites.  Now, like other sites, once we have the equipment and 
if the facility is ready, it is only a matter of hours depending on the 
size.  The time we are looking for can be described by the following 
scenerio:

You work for your University's DP department supporting Local Area 
Networks.  A department calls and wants to install a LAN needs info.  You 
meet with them and recommend a LAN and provide them a proposal.  They find 
the cost acceptable and say "Lets Do this..."

From that moment, how long does it take before the installers show up at 
their site with parts.

Our particular problem here involves the paper work, delays through 
purchasing, shipping delays, and so on.  Also if you could describe the 
process it would be of great help.

The way we do it currently, and are looking to change is as follows:

Meet with Customer
Present Proposal if a LAN is recommeded
Customer Decides to do it
Network is designed
Customer signs off on design
Customer orders workstations and file servers, buys installation, cards, 
hubs and site license software from us.
Order goes through purchasing to vendors.
Equipment arrives at various times (due to multiple vendors)
Installation is scheduled
Installation is performed.

From the time the customer decides to purchase the LAN until our people show 
up can range any where from 6 weeks to 6 months.  How do you handle this?

Thanks in Advance
Rob Miracle
Network Analyst
--
Rob Miracle                |  Internet:   rwmira01@vlsi.louisville.edu
Network Consultant         |  BITNET:     rwmira01@ulkyvx
University of Louisville   |  CompuServe: 75140,625
Louisville, KY             |  To boldy go where no one has gone before.
Newsgroups: comp.dcom.lans.misc
From: gill@eagle (Warren Gill)
Subject: Re: Lan Manager/Novell modem link?
X-Newsreader: Tin 1.1 PL4
Organization: Sangamon State University
Date: Sun, 13 Sep 1992 23:33:03 GMT

bob@comlab.gatech.edu (Bob Baggerman) writes:
: With LAN Manager 2.1 Microsoft provides an IPX/SPX interface for your
: Novell redirector and stack to use along with the LAN Manager stack and
: redirector.  It probably takes up a bit of memory when you get them all 
: loaded but NDIS 2.0 supports dynamic loading and unloading of protocol
: stacks drivers can be moved in and out of memory as needed.  I haven't
: actually tried it.  I generally try to avoid Novell.  But it looks pretty
: simple from the installation documents.

  I have NETBEUI, TCP/IP, an NDIS<->Packet "shim", and NDIS<->IPX drivers
running on one PC. They all Work!  Netware Connectivity package from Microsoft
is easy to install, and easy to use (just type 'NWLOAD' and the driver
loads, and you LOGIN to Novell - type 'NWUNLOAD' to unload the drivers when
you are done).  Also, if the installation detects a copy of MS Windows, it
loads network drivers which allow you to logon and connect resources from
within Windows!  For example, "Connect Net Drive" in file manager prompts
you for "NetWare" or "LAN Manager".   Neat!
--wg
      ______                                                               
      )     (   Warren Gill, Microcomputer Software Specialist
     /       |  Sangamon State University, Springfield, IL                 
    (        |  Internet:        gill@eagle.sangamon.edu
     \_  *   |                                                             
       \     |  HSB-117          Monday-Friday 08:00-16:30 CDT
       /    /   217/786-7354
        \/\/    
          It is better to know nothing than to know what ain't so.        
           {H.W. Shaw}                                                    
Newsgroups: comp.dcom.lans.misc
From: weber@rhrk.uni-kl.de (Christoph Weber-Fahr [KIT])
Subject: Re: How to interconnect a LAN ?
Organization: University of Kaiserslautern, Germany
Date: Mon, 14 Sep 1992 16:08:02 GMT

Hello,

two small corrections: 

klitd@hpsgm2.sgp.hp.com (Raj PUBALA) writes:

>To do the above, you can use NFS NLM on the Netware server (I presume it
>is a 3.11 Netware version) and run NFS on the SCO Unix. This will allow
>file sharing and access by both Netware clients (PCs) and SCO Unix users.
>Netware users on the LAN can access the files on the SCO Unix transparently
>(they don't see NFS, they see them as part of Netware volume). 

This is not correct. Netware NFS exports volumes, but doesn't import them
(which would violate NFS specs, since a Netware server would re-export
them to DOS clients).

> likewise,
>SCO Unix see Netware volumes as NFS volumes). Integration of the print
>services can be done through a third party product (I think it is reflex?
>I can't remember the name). Basically, it uses the "lpr" to support remote
>spooling. And SCO Unix does support "lpr". 

This isn't correct, too. Netware NFS contains fully bidirectional lpr support.
Novell also sells the lpr-support stuff alone together with some utilities 
as FlexIP - maybe you meant that.

>Now all these only concern 
>integration of services and nothing about bridging or routing.

Regards

Christoph Weber-Fahr

-- 
  Christoph Weber-Fahr                  |  E-Mail:  weber@rhrk.uni-kl.de 
  Universitaet Kaiserslautern,  KIT     |  S-Mail:  Postfach 3049
  Tel. 0631/205-3391                    |           D-6750 Kaiserslautern
--------------------------  My personal opinion only    ---------------------
Xref: sparky comp.dcom.lans.misc:731 comp.os.os2.networking:1294