home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!gatech!hubcap!ncrcae!ncrhub2!ncrlnk!ncrstp!npdiss1!chuck
- From: chuck@npdiss1.StPaul.NCR.COM (Charles Rissmeyer)
- Newsgroups: comp.protocols.tcp-ip
- Subject: Re: STARLAN 10 10BASE-T hub unit doesn't like adapters
- Message-ID: <1579@npdiss1.StPaul.NCR.COM>
- Date: 8 Jan 93 17:07:48 GMT
- References: <Jan.4.19.20.49.1993.958@ocean.rutgers.edu> <1993Jan8.022641.27932@alf.cooper.edu>
- Organization: StPaul
- Lines: 24
-
- In article <1993Jan8.022641.27932@alf.cooper.edu> hak@alf.cooper.edu (Jeff Hakner) writes:
-
- >I've had a similar problem. When I used the Allied Telesis thick-10BASE-T
- >adapter and plucked the twisted pair into an AT&T STARLAN 10 hub, the
- >whole network starting dying with heavy collisions (and no traffic!).
- >WHen I replaced the hub with an Allied hub (more modern), no problems.
- >I thought STARLAN10 was supposed to be compatible with 10-BASE-T, but perhaps
-
- I'm not very familiar with the details of STARLAN10 hubs. The newer ones
- are 10BaseT compatible. It sounds like you might have a problem with the
- link-beat , sometimes called link integrity, or
- heartbeat. Basically, if you have link-beat on at the hub, you need it on
- at the workstation's transceiver. If your hub doesn't support link-beat, then
- you must turn it off at the terminal too.
-
- One more thing I just thought of, I believe some Allied Telesis transceivers
- do not have the ablility to turn off link-beat. This means you must have
- it on at the hub.
-
- Good luck,
-
- Charles (Chuck) Rissmeyer KE0VG
- (612) 638-7669 (VP 652-7669) - charles.rissmeyer@StPaul.NCR.COM
- NCR - An AT&T Company NCR CCS-PM&S NPD St. Paul
-