LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Ben Parker <[log in to unmask]>
Fri, 23 Feb 1996 09:12:45 -0600
text/plain (28 lines)
Many of us users of HOME.EASE.LSOFT.COM and PEACH.EASE.LSOFT.COM are
having trouble at the moment because of a network problem.
 
Traceroute shows the following:
 
11. 192.41.177.210  fiddi.mae-east.netcom.net        (252ms)
12. 163.179.220.181 t3-2.was-dc-gw1.netcom.net       (258ms)
13. 163.179.220.186 t3-2.chw-il-gw1.netcom.net       (291ms)
14. 163.179.220.185 t3-1.was-dc-gw1.netcom.net       (279ms)
15. 163.179.220.186 t3-2.chw-il-gw1.netcom.net       (291ms)
16. 163.179.220.185 t3-1.was-dc-gw1.netcom.net       (279ms)
17. 163.179.220.186 t3-2.chw-il-gw1.netcom.net       (291ms)
18. 163.179.220.185 t3-1.was-dc-gw1.netcom.net       (279ms)
****
 
As a general question, what can/should we List Owners do when our list is
on a remote site we don't have direct control of and can't reach?
To whom should we report a problem like this?
 
(further information in the above specific case shows that the T1 line to
Lsoft site in Landover, MD is down.  Meaning the problem may not be with
Netcom.net routers at all, although the above endless loop doesn't look
right to me anyway.)
 
 ____________________________________________________________________________
  Ben Parker ............. (Oak Park IL) ........... [log in to unmask]
  owner DPRV-L

ATOM RSS1 RSS2