[comp.protocols.tcp-ip] annoying n/w problems

KCPENG@TWNCTU01.BITNET (11/03/90)

Hi netter,

   There exist some problems in our network, though not(?) severe but indeed
annoying. The net consists of tens of various machine: Vaxs, Suns, HPs,
RS6000s, X-terminals... Some observable phenomenons follow:
   . the Sun 4/370 console keeps printing the message a period of time -
     'le0 : No carrier - transceiver cable problem?'
     of course, it can still do network functions. Other Suns SSs just have
     no such annoyance.
   . there are 3 workstations, say A, B and C, networked together.
        (O) ftp A to B
        (O) ftp B to C
        (X) ftp A to C
     A, B = Sun, C = RS600. (B,C) and (A) are on two different repeter ports.
   . another 2 hosts, say D and E, connected.
        (O) telnet D to E
        (X) telnet E to D
        (X) telnet D to D
     these two nodes are not on the same repeter port. I've re-invoked the
     inetd of D, still in vain. (It seems D can telnet 'out' sometimes before)

What I'm concerned are,
1) what's the causes? repeater? cable? others?
2) any utility to monitor the network problems, like re-transmission rate?
   or you have to put some command, like netstat, in cron table and run it
   periodically, then do statistics yourself? if so, how do I suppose to know
   the 'correct'(tolerable) value in all these statistical values?
3) some friend mentioned to me a product called 'cable scanner'. is it helpful
   to the above problems?

Any clue is highly, highly welcome.

Regards,
Kai-Chih Peng,
kcpeng@twnctu01.bitnet