george@webb.psych.ufl.edu (Stephanie George) (09/25/90)
I've been running the NCSA telnet package with and without the
packet drivers sucessfully for more than a year now. Occasionally, I've been
getting the message "Local HOST or gateway not responding" on new
installations. The station that doesn't work is also not recognized as
"pingable" from any other host, either - nobody recognizes it. Curiously,
the station on either side may work flawlessly, so apparently there's no
obvious physical layer problem. I have endlessly tried changing the "address"
in the config.tel file to every possible combination between c000h and dc00h
to no avail. This has happened on old-bus PCs running WD8003s and 3Com 501s
as well as microchannel PS/2s running with WD8003s and 3Com 523s.
One suggestion that I received from someone on this campus was that
I might have too many stations on one length of Thinnet or I may have exceeded
the maximum length for the wire. In order to test that, I terminated the
cable at the errant station and tried again without success. (see following
diagram)
+----------+ +----------+ +----------+
| | | | | |
[7m-----[m| A |[7m--------[m| B |[7m--------[m| C |[7m---||[m
+----------+ +----------+ +----------+
Fig. 1: Stations A and C work just fine; Station B is new and gets the
"Local host ... not responding" message. Cable is terminated just
after station C, signal source is just before station A.
+----------+ +----------+ +----------+
| | | | | |
[7m-----[m| A |[7m--------[m| B |[7m----|| [m| C |[7m-----[m
+----------+ +----------+ +----------+
Fig. 2: Cable terminated between B and C. Station A works great; station B
still has error. (Assume signal source is before station A and that
A is first station on this run of cable.)
Has anyone ever seen this? What do I do now?
Stephanie George
--
Stephanie George 114 Psychology Dept.
george@webb.psych.ufl.edu University of Florida
(904) 392-3979 Gainesville, FL 32611