|
|
| Author |
Message |
| 25 new of 188 responses total. |
jazz
|
|
response 100 of 188:
| 
Oct 16 14:15 UTC 2000 |
It's a Halloween special. Enjoy it.
|
rcurl
|
|
response 101 of 188:
|
Oct 18 20:08 UTC 2000 |
I was logged in on a different process a moment ago, and it hung for
some time. I therefore logged in again, and the new login was as
responsive as usual while the other one remained frozen. How can this
happen? Eventually the first one thawed, and then I got a warning
that I had two logins. In that regard, what's wrong with having two
logins?
|
janc
|
|
response 102 of 188:
|
Oct 19 00:12 UTC 2000 |
"LOST HEAD" is a Marcus message. If you were Marcus it would tell you
that something interesting happened to the telnet queue, but it was
automatically detected and fixed correctly, so it's OK. If you are
anyone else, you can ignore it.
I don't know why one connection would be frozen while the other one is
fine. Could just as easily be something on your end or inbetween as on
Grex. Something waiting for a response until a timeout happens
probably.
We limit load by limiting the number of people who can telnet in at
once. If you are using two connections, and the system is full, then
you are keeping someone out.
|
jared
|
|
response 103 of 188:
|
Oct 19 02:59 UTC 2000 |
I loaded the latest software on the dsl router tonight. It was
several revisions behind. The router seems to be much happier
now.
|
russ
|
|
response 104 of 188:
|
Oct 19 04:22 UTC 2000 |
Re #102: Perhaps it should be re-named "Henry VIII error".
|
krj
|
|
response 105 of 188:
|
Oct 20 00:42 UTC 2000 |
Bursts of lag severe enough to make telnet connections unusable
have been hitting for the last 20 minutes or so.
|
jazz
|
|
response 106 of 188:
|
Oct 20 13:19 UTC 2000 |
I'd suggest it be called the "Ichabod Crane", Russ.
|
other
|
|
response 107 of 188:
|
Oct 23 02:31 UTC 2000 |
of the "queen of hearts" error...
|
aruba
|
|
response 108 of 188:
|
Oct 24 15:16 UTC 2000 |
Grex has hung up on me 4 times today, which hasn't happened to me in a long
time. I also noticed an extra strange tone when dialing in, so I think one
of the modems has gone flaky. I get the strange tone when dialing 3000,
5041, 3411, and 3451, but not when dialing 3554, so I think it's 3451 that
has the problem.
|
aruba
|
|
response 109 of 188:
|
Oct 24 16:17 UTC 2000 |
Looks like I jumped the gun - the problem seems to be with noise on my line,
since I got bumped off of Merit too. It rained in Ann Arbor last night,
which often correlates with line noise. Sorry for the false alarm.
|
scg
|
|
response 110 of 188:
|
Oct 24 16:56 UTC 2000 |
If rain causes line noise, it means the pair your phone line is on has a leak
in its insulation, that water is getting into. Call your telco and ask them
to fix it.
|
aruba
|
|
response 111 of 188:
|
Oct 24 17:04 UTC 2000 |
Well, maybe I'll try. Since the problem only shows up once in a while,
though, it'd be hard for them to know if they'd fixed it. Carol's line
(coming in through the same box right next to mine) seems fine - I haven't
been bumped off once.
|
davel
|
|
response 112 of 188:
|
Oct 25 00:39 UTC 2000 |
I'd not jump to the conclusion that it was anywhere near Mark's end that the
rain is getting in. When dialing in a few minutes ago, I got line noise I
could hear as major static - hear through the computer's speaker, I mean.
I aborted the dial, & tried again, & got a quiet connection. If it were at
the line to my house that water (or whatever causes frying-bacon-type static)
is getting in, would redialing make it magically disappear?
|
gelinas
|
|
response 113 of 188:
|
Oct 25 01:00 UTC 2000 |
Mark, yes, they can test for this problem even when the lines are dry.
At least, they did when I had the problem. Then the guy discovered he
had test the wrong pair! (Yes, I had two lines: one was good, the other
wasn't.)
|
aruba
|
|
response 114 of 188:
|
Oct 25 01:49 UTC 2000 |
OK. It seems OK at the moment, so it may have been just this morning that
there was a problem.
|
scg
|
|
response 115 of 188:
|
Oct 25 07:42 UTC 2000 |
The problem will go away as the line dries out.
The thing to do when calling Ameritech is to emphasize that it's an
intermitent problem. They won't write this down, but it will give you grounds
to yell at them on after the tech comes out a week later and leaves you a note
saying that the line seems to be working. Repeat the procedure until they
find the problem and fix it. It helps to actually talk to the tech who comes
out to look at it, since once they know that they're looking for an
intermitent problem, they're generally pretty good at finding it.
|
jared
|
|
response 116 of 188:
|
Oct 27 18:45 UTC 2000 |
one person had chronic problems until their phone lines were knocked
down by a tree. Once they restrung the lines, it went away.
|
katie
|
|
response 117 of 188:
|
Oct 28 13:53 UTC 2000 |
The tree went away? I'm impressed.
|
charcat
|
|
response 118 of 188:
|
Oct 31 06:24 UTC 2000 |
he he he he "the tree went away" he he
|
mooncat
|
|
response 119 of 188:
|
Oct 31 16:28 UTC 2000 |
Topiary adjustments...
|
russ
|
|
response 120 of 188:
|
Nov 4 03:28 UTC 2000 |
3 minute delay to get a login prompt tonight.
(On dial-in.)
|
russ
|
|
response 121 of 188:
|
Nov 4 03:34 UTC 2000 |
The internet connection appears to be down.
Login Name TTY Idle Login Time Location Work Phone
russ Russ Cage *uf Nov 3 22:27
j imtheonlyone
|
scott
|
|
response 122 of 188:
|
Nov 4 13:08 UTC 2000 |
Seems OK now.
|
i
|
|
response 123 of 188:
|
Nov 7 04:04 UTC 2000 |
The dial-ins seem to be goofed up this evening. I've tried calling in on
at least 3 numbers: sometimes i get the "Welcome to grex..." message
before it drops carrier, sometimes only the modem's CONNECT... message.
(I'm telnetted in now.)
|
scott
|
|
response 124 of 188:
|
Nov 7 12:16 UTC 2000 |
Grex was down a bit yesterday.
|
