|
|
| Author |
Message |
| 25 new of 283 responses total. |
valerie
|
|
response 100 of 283:
| 
Oct 19 21:57 UTC 1997 |
This response has been erased.
|
remmers
|
|
response 101 of 283:
|
Oct 19 23:11 UTC 1997 |
A short while ago I wasn't able to telnet to Grex either, so I'm
using Backtalk. However, I tried again just now and the telnet
connection was successful. Did somebody diagnose and problem and
fix it?
|
valerie
|
|
response 102 of 283:
|
Oct 19 23:47 UTC 1997 |
This response has been erased.
|
omni
|
|
response 103 of 283:
|
Oct 20 00:29 UTC 1997 |
I'm having a problem dialing in at 2400. I was going to try some stuff with
my evil computer, and since the dang thing only has a 2400, it does the
handshake but the grex's modem goes to sort of blue funk and locks up.
So maybe someone would like to go to yon pumpkin and reset the modei so that
they answer in 2400 mode. Thanks.
|
scg
|
|
response 104 of 283:
|
Oct 20 00:34 UTC 1997 |
It looks like I screwed something up in DNS last night, which would be causing
Grex's DNS stuff to report the wrong number, and would indeed cause the
problems people are reporting. I'll fix it. Sorry about that.
|
scg
|
|
response 105 of 283:
|
Oct 20 00:39 UTC 1997 |
Ok, it's fixed. It will take a while to propegate to some places. grex.org
didn't have the typo, so it's working fine.
This is why I shouldn't be messing with DNS stuff when I should be sleeping.
|
davel
|
|
response 106 of 283:
|
Oct 20 13:29 UTC 1997 |
Re 103: when I tried to get on from home, also at 2400 bps, sometime Sunday,
a modem was answering but I could not get a connection. Haven't tried
since. (Now at work & using a faster modem to enter this.)
|
dang
|
|
response 107 of 283:
|
Oct 20 18:06 UTC 1997 |
As an explaination of the DNS problem that caused telnet errors:
The dns for cyberspace.org was wrong (it said 152.160.30.15, not 152.160.30.1)
but the dns for grex.cyberspace.org, grex.org, and www.cyberspace.org were
all correct. Thus, telnetting to any of the last three or accessing grexes
webpages or backtalk worked, but telnetting, pinging, ftping, whatever to
cyberspace.org failed. That should be fixed now, although it takes time for
the fix to make it's way around the internet.
|
richard
|
|
response 108 of 283:
|
Oct 20 18:07 UTC 1997 |
my default is always grex.cyberspace.org, not cyberspace.org, and
I couldnt telnet at all yesterday.
|
headdoc
|
|
response 109 of 283:
|
Oct 20 20:19 UTC 1997 |
Well, one good thing about not being able to dial into grex, I found my way to
backtalk through aol. And its in COLOR!! But I want to read my e-mail 8-(.
|
cmcgee
|
|
response 110 of 283:
|
Oct 21 02:24 UTC 1997 |
The modem answering 3000 has been flaky tonight. It would answer, give part
of the connection whistle, then hang there, not really connecting, but not
hanging up the phone either. Dialling back immediately, I would get no answer
(open ringing) or sometimes it would hang again. Frustrating.
|
janc
|
|
response 111 of 283:
|
Oct 21 14:24 UTC 1997 |
I was having the same problem. We suggested Audrey set the baud rate on
her com program to 19200, and that worked for her, but I haven't been
able to connect at all. Things are certainly not as they should be.
We need to either (1) get Grex fixed so we can go back to using the
serial card, (2) get the modems configured so they work right on the
terminal server, or (3) get the 4/670 setup.
|
kaplan
|
|
response 112 of 283:
|
Oct 21 14:30 UTC 1997 |
Re 111: You mean the 670 would be able to drive the ALM card so if it
were up and running, we would be able to put all the modems back on the
ALM card?
Would it be possible to put the ALM card into the 670 and use it as a
terminal server even if it is not ready to be grex yet?
|
kaplan
|
|
response 113 of 283:
|
Oct 21 14:31 UTC 1997 |
Er, I said would it be possible. Of coursre I meant would it be easy.
|
davel
|
|
response 114 of 283:
|
Oct 21 16:43 UTC 1997 |
I'm still unable to connect at 2400 bps.
|
omni
|
|
response 115 of 283:
|
Oct 21 18:23 UTC 1997 |
That's what I've been saying all along. No 2400, no evil computer
connections. Bummer.
|
dpc
|
|
response 116 of 283:
|
Oct 21 18:45 UTC 1997 |
Well, *I'm* connected at 2400 baud right now on a dialin.
|
mdw
|
|
response 117 of 283:
|
Oct 21 20:50 UTC 1997 |
At this point, it's looking more & more likely that the ALM-II card is
the culprit responsible for the large # of reboots we've seen recently
(esp. the "break/C" crashes). So, I'd say that getting the modems to
work correctly with the terminal server is the only real option we have
left.
|
scott
|
|
response 118 of 283:
|
Oct 21 22:02 UTC 1997 |
I'm going in this evening with an RS232 analyser, to try to nail the modem
config down.
|
scott
|
|
response 119 of 283:
|
Oct 21 23:43 UTC 1997 |
OK, the modems ought to be much better now, after I found some very suspect
settings and had a guinea pig (thanks, dang) dial in repeatedly until the
connection worked properly.
Of course, there's still the telnet queue problem... :(
|
jiffer
|
|
response 120 of 283:
|
Oct 22 01:36 UTC 1997 |
a REAL guinea pig? i hope he has a login ;P
|
tpryan
|
|
response 121 of 283:
|
Oct 22 02:14 UTC 1997 |
Took me awh8ile to connect to 5041. a number of enters and
a Control-C or three before getting the Grex time-tone-prompt.
Are all modei up to 9600 now?
|
omni
|
|
response 122 of 283:
|
Oct 22 05:10 UTC 1997 |
I don't know what happened but I was able to connect my evil computer to
Grex at 2400. Thanks whoever fixed the modems.
(note: My evil computer is the 386. ) Once a Mac person, always a Mac person)
|
scott
|
|
response 123 of 283:
|
Oct 22 11:14 UTC 1997 |
All modems (currently 7) are at 14400. I need to come up with correct
settings for the older style ones before I can deploy those.
|
valerie
|
|
response 124 of 283:
|
Oct 22 17:36 UTC 1997 |
This response has been erased.
|
