|
|
| Author |
Message |
| 25 new of 234 responses total. |
senna
|
|
response 145 of 234:
| 
Aug 10 05:05 UTC 1998 |
Figures. I picked the one week to be out of dialin range that I really need
to be able to use the dialins.
|
scg
|
|
response 146 of 234:
|
Aug 10 05:50 UTC 1998 |
Ameritech is sending somebody out to look at the line tomorrow morning.
|
bmoran
|
|
response 147 of 234:
|
Aug 10 12:49 UTC 1998 |
tomorrow Monday, or tomorrow Tuesday?
|
headdoc
|
|
response 148 of 234:
|
Aug 10 15:24 UTC 1998 |
Is there anything I can do to expedite the progress or lack of it? Grex is
my primary, actually only e-mail aonduit and I am getting very frustrated.
Let me know what I can do to get things rolling again.
|
scg
|
|
response 149 of 234:
|
Aug 11 00:47 UTC 1998 |
We are back on the Net, as of around 6 pm today. Ameritech lost track of our
trouble ticket twice, apparrently, such that it spent most of today waiting
around well past the most recent due date for a technician to pick it up.
I finally got ahold of somebody there who was willing to spend a lot of time
on tracking this down, and had a technician paged and told that our ticket
was his highest priority, and to get out there and fix it *now*.
We should be opening the system back up to users as soon as the mail finishes
coming in. Right now the system load has come back down to a reasonable
level, but incoming mail still has the Net connection running at 100% of
capacity.
|
e4808mc
|
|
response 150 of 234:
|
Aug 11 01:50 UTC 1998 |
Yay for all the staff work that got Ameritech to FINALLY pay attention, and
to troubleshoot everything so we were sure it was them, not us!
|
headdoc
|
|
response 151 of 234:
|
Aug 11 02:52 UTC 1998 |
Many thanks for the work you did to get Grex back and operating. I think I
have to get a backup isp. I keep thinking about it, but this latest downtime
showed me I have to do more than think about it.
|
aruba
|
|
response 152 of 234:
|
Aug 11 02:55 UTC 1998 |
Thanks, Steve G., for all your work on this.
|
tpryan
|
|
response 153 of 234:
|
Aug 11 03:32 UTC 1998 |
Not only should you get a refund/reduction in charge for the days
of lost service, particulary due to lost trouble ticket, you all should
send them a bill for consulting on the solution.
|
dpc
|
|
response 154 of 234:
|
Aug 11 14:24 UTC 1998 |
Great work!!
|
albaugh
|
|
response 155 of 234:
|
Aug 11 14:31 UTC 1998 |
What was the "root cause" of the ISDN problem? I.e. was this a "once in a
blue moon" thing, totally unanticipated? Or could this situation arise again,
in much the same (unexpected) way?
|
rcurl
|
|
response 156 of 234:
|
Aug 11 17:39 UTC 1998 |
Could the comment flashed on the screen when a connection attempt is made
and terminated be made to show longer? I have to turn on capture and then
reconnect to read what it says.
|
scg
|
|
response 157 of 234:
|
Aug 11 20:34 UTC 1998 |
re 155:
When Ameritech called me back to say it was fixed, it was a couple of
hours after the line had come back up, and I was in the middle of about five
other things that absolutely needed to be done at work. Having already spent
seeral hours on the phone with them, my goal at that point was to get them
off the phone as quickly as possible, and I didn't think to ask what they had
done to fix it. I probably should have.
|
krj
|
|
response 158 of 234:
|
Aug 12 03:51 UTC 1998 |
You could probably call Ameritech back with the trouble ticket number
and ask for the gory details.
|
scg
|
|
response 159 of 234:
|
Aug 12 06:08 UTC 1998 |
I've already spent more time on this than I want to. If you want to call and
ask, I can send you the ticket number.
|
aruba
|
|
response 160 of 234:
|
Aug 12 07:41 UTC 1998 |
I keep getting that "mkids too small" error from Picospan again. Could
someone tell me what that means, again?
|
mdw
|
|
response 161 of 234:
|
Aug 12 08:05 UTC 1998 |
It means you should quit picospan and run it again. There's a bug and
it runs out of space in an internal array after being used for a
(longish) while...
The "root" cause of the ISDN problem was probably water and bad cable.
Since something very like this problem happened once before, yes, it
probably will happen again.
|
albaugh
|
|
response 162 of 234:
|
Aug 12 16:06 UTC 1998 |
Pardon my ignorance: Which stretch of grex's ISDN cabling is "bad" and/or
subject to "water problems" ?
|
gull
|
|
response 163 of 234:
|
Aug 12 16:25 UTC 1998 |
With Ameritech handling it? Probably most of it. :P
|
mdw
|
|
response 164 of 234:
|
Aug 13 03:06 UTC 1998 |
The part of grex's ISDN cabling that appears to be unreliable is the
part from ameritech's central offices to the blackrose society.
|
aruba
|
|
response 165 of 234:
|
Aug 13 05:04 UTC 1998 |
"The Blackrose Society?"
|
mdw
|
|
response 166 of 234:
|
Aug 13 05:59 UTC 1998 |
You know, our ISP.
|
aruba
|
|
response 167 of 234:
|
Aug 13 14:11 UTC 1998 |
Oh.
|
albaugh
|
|
response 168 of 234:
|
Aug 13 14:38 UTC 1998 |
So we can take some "misery loves company" comfort from knowing that all of
grex's ISP's customers were affected? ;-)
|
e4808mc
|
|
response 169 of 234:
|
Aug 13 14:46 UTC 1998 |
Yeah, that was my question. Did *everyone* who uses our ISP lose net service
for 5 days?
|
