|
|
| Author |
Message |
jmsaul
|
|
M-Net down
| 
Feb 16 04:13 UTC 2000 |
M-Net is currently experiencing some sort of failure; it can't be reached
via telnet and doesn't respond to pings, and traceroute craps out in
Livonia. Since dialin users get through the authentication process but
never reach M-Net, I assume the problem is our machine.
|
| 84 responses total. |
jerome
|
|
response 1 of 84:
|
Feb 16 04:19 UTC 2000 |
Does this mean no one will be able to get in and check things out until
tomorrow morning?
|
eprom
|
|
response 2 of 84:
|
Feb 16 04:33 UTC 2000 |
bummer..nice to have a home away from home. :)
|
crosew
|
|
response 3 of 84:
|
Feb 16 04:37 UTC 2000 |
Where is m-net, not able to get in by any means :(
|
mdw
|
|
response 4 of 84:
|
Feb 16 05:56 UTC 2000 |
M-net is in Livonia, Michigan.
|
jmsaul
|
|
response 5 of 84:
|
Feb 16 07:00 UTC 2000 |
M-Net is located at the WWNet facility in Livonia. Their staff comes on at
8 tomorrow morning (well, this morning now) and I'll call them when I get
up if someone else hasn't already notified them. They can reboot the M-Box
for us, but we don't want to abuse the privilege so we aren't publishing the
phone number to contact them.
|
happyboy
|
|
response 6 of 84:
|
Feb 16 12:11 UTC 2000 |
thanks joe.
|
iggy
|
|
response 7 of 84:
|
Feb 16 12:58 UTC 2000 |
i just tried.. no luck.
but, i think i may be a tad early. it isnt quite 5am heree.
|
lowclass
|
|
response 8 of 84:
|
Feb 16 14:16 UTC 2000 |
At 8:59 am i dialed in on the guest line, and went through the
WWnet authentication process. After the "TTS system AUthentication"
Message, the system hung. Hope the information comes in handy.
(OH, for the good old days of M-Net, when Staff wasn't aloowed to have
a life. THey looked SOOO grand chained near the M-B0x. :) )
Tell 'em thanks for me even before they get the b0x back up. 'cause
I know they'll do it.
|
jmsaul
|
|
response 9 of 84:
|
Feb 16 15:16 UTC 2000 |
I just called WWNet, so hopefully it will be up soon. Thanks to all for
their patience and information!
|
jerryr
|
|
response 10 of 84:
|
Feb 16 15:40 UTC 2000 |
you bbs junkies. get a life!
|
iggy
|
|
response 11 of 84:
|
Feb 16 15:57 UTC 2000 |
still nothing. even the webpage is down.
|
jor
|
|
response 12 of 84:
|
Feb 16 17:03 UTC 2000 |
get a what
|
trex
|
|
response 13 of 84:
|
Feb 16 20:14 UTC 2000 |
we've got dns problems on m-net. and, we've had them for ages, but they don't
really cause a problem until m-net's dns server (itself) goes down for a day.
so, m-net is up, and I'm on it right now, but the world can't see it, unless
you telnet to it's ip address : 209.142.209.161
|
jmsaul
|
|
response 14 of 84:
|
Feb 16 22:48 UTC 2000 |
It's back up, and can be reached the normal way.
|
cyklone
|
|
response 15 of 84:
|
Feb 16 23:59 UTC 2000 |
Not for me at 6:54 pm today (dialing in).
|
russ
|
|
response 16 of 84:
|
Feb 17 03:34 UTC 2000 |
Sounds like a good reason for WWNet to handle M-Net's DNS.
|
jmsaul
|
|
response 17 of 84:
|
Feb 18 15:36 UTC 2000 |
Yep.
|
jerryr
|
|
response 18 of 84:
|
Feb 22 12:26 UTC 2000 |
mnut has been unreachable since very early this morning. connection is made
and immediately lost. telnet or dial-up telnet, doesn't matter which.
|
jmsaul
|
|
response 19 of 84:
|
Feb 22 13:33 UTC 2000 |
Just noticed that myself. Not sure what's up.
|
cyklone
|
|
response 20 of 84:
|
Feb 22 13:41 UTC 2000 |
<drums fingers impatiently>
|
cyklone
|
|
response 21 of 84:
|
Feb 22 13:42 UTC 2000 |
BTW, M-net also went down last night, notwithstanding #18.
|
jerryr
|
|
response 22 of 84:
|
Feb 22 13:43 UTC 2000 |
i noticed it was being bad aroun 1am. tough call - early morning or nite?
:)
|
iggy
|
|
response 23 of 84:
|
Feb 22 16:02 UTC 2000 |
still down...
|
jmsaul
|
|
response 24 of 84:
|
Feb 22 16:25 UTC 2000 |
... but we're back up now.
|