|
|
| Author |
Message |
| 25 new of 162 responses total. |
nestene
|
|
response 25 of 162:
| 
Jul 29 09:36 UTC 1999 |
I've been having trouble trying to dial in on 761-3000 these last few weeks.
Usually, things hang after I'm told it might take a few seconds to connect,
but today I didn't get anything after my modem's CONNECT notice. As usual,
dialing in on 761-3411 worked perfectly.
|
e4808mc
|
|
response 26 of 162:
|
Jul 29 14:29 UTC 1999 |
Same problem this morning. 3000 hangs there without giving me the few seconds
to connect notice.
|
scott
|
|
response 27 of 162:
|
Jul 29 16:05 UTC 1999 |
I think we may have a futzy terminal server port.
|
aruba
|
|
response 28 of 162:
|
Jul 29 16:42 UTC 1999 |
I couldn't get in on 3000 or 5041 today.
|
krj
|
|
response 29 of 162:
|
Jul 29 17:46 UTC 1999 |
I can't get 761-3000 to work today.
Last night, in party, dea said that he had to hunt around a bit to find
a working phone line on Grex.
|
keesan
|
|
response 30 of 162:
|
Jul 29 19:48 UTC 1999 |
Same problem yesterday and today. We thought it was in the computer, tried
three different modems, two com ports, a new version of Procomm, and then
another computer. Glad to know it is not at our end.
|
scott
|
|
response 31 of 162:
|
Jul 29 22:01 UTC 1999 |
I dinked around with the terminal zerver this afternonn, but couldn't find
anything really wrong. I power-cycled a few modems and left it for now. I
dial in enough to notice any problems...
|
tpryan
|
|
response 32 of 162:
|
Jul 29 22:09 UTC 1999 |
Problem persists. And I thought you where practiceing shutting down
early.
|
scott
|
|
response 33 of 162:
|
Jul 29 22:25 UTC 1999 |
Ah well. back to the salt mines...
|
krj
|
|
response 34 of 162:
|
Jul 29 23:19 UTC 1999 |
I was not able to get in on 761-3000 just now, but 761-5041 got me in.
|
mooncat
|
|
response 35 of 162:
|
Jul 30 01:57 UTC 1999 |
Took me several tries at 761-3000, but eventually it worked.
|
aruba
|
|
response 36 of 162:
|
Jul 30 06:25 UTC 1999 |
I couldn't get in on 300 or 5041 tonight, but 3411 worked. So I'm betting
it's the 5041 port that has a problem.
|
jiffer
|
|
response 37 of 162:
|
Jul 30 12:48 UTC 1999 |
the idle buster doesn't seem to be working..
|
davel
|
|
response 38 of 162:
|
Jul 30 17:21 UTC 1999 |
Last night Grace tried to log in, from home (dialin). Connected to the modem,
no further response. I've now tried; I've been connected to the modem for
over 15 minutes with no response. Possibly from this fact it would be
possible to deduce which modem is to blame. (From work I can telnet in, so
as to enter this.)
|
scott
|
|
response 39 of 162:
|
Jul 30 17:25 UTC 1999 |
Telling which modem is the culprit is a lot harder than it used to be.
|
pthomas
|
|
response 40 of 162:
|
Jul 31 00:44 UTC 1999 |
7613000 hangs as soon as I get the CONNECT message from my modem...may
want to check it out.
|
tpryan
|
|
response 41 of 162:
|
Jul 31 04:29 UTC 1999 |
In my previous dial in, just now, to 3000, it rang thru to next line.
Then it hung after connect. I got thru on the 3411 line.
|
mooncat
|
|
response 42 of 162:
|
Jul 31 14:40 UTC 1999 |
dialing 761-3000 worked on the first try for me this morning...
|
scott
|
|
response 43 of 162:
|
Jul 31 14:57 UTC 1999 |
I've swapped terminal servers, and als a modem that appeared to be flaky.
|
i
|
|
response 44 of 162:
|
Jul 31 22:25 UTC 1999 |
I'm getting "Invalid IP Address" now when i try to dial in.
|
scott
|
|
response 45 of 162:
|
Jul 31 23:23 UTC 1999 |
Oops. That should be fixed now.
|
aruba
|
|
response 46 of 162:
|
Aug 1 14:44 UTC 1999 |
I'm dialed in, but when I try to run Kermit, Grex tells me that only dial-in
users can use Kermit, and I should be using ftp instead. Looking at the
script, it appears that Scott must have changed the terminal server's IP
address from 204.212.46.131 to 204.212.46.132, but /usr/local/bin/kermit
doesn't know that. Could someone fix it? I imagine the x- y- and z-modem
scripts have the same problem.
|
omni
|
|
response 47 of 162:
|
Aug 1 16:00 UTC 1999 |
They do. I was trying to download a few web pages (less then 10k) and I
got that stupid text. IT was annoying to say the least
|
scott
|
|
response 48 of 162:
|
Aug 1 16:27 UTC 1999 |
Ah. Well, I actually changed to our spare terminal server, which naturally
has a different IP address.
I'll see if I can fix the script.
|
scott
|
|
response 49 of 162:
|
Aug 1 16:29 UTC 1999 |
OK, I fixed it.
|
