|
|
| Author |
Message |
| 25 new of 237 responses total. |
cross
|
|
response 100 of 237:
| 
Jul 23 21:08 UTC 2003 |
This response has been erased.
|
gelinas
|
|
response 101 of 237:
|
Jul 24 03:19 UTC 2003 |
I didn't ask about their dial-in options because Mary had already said that
they offer the service.
A separate terminal server made sense when the hardware was different.
Right now, this minute, I can't decide if it still makes sense; I _like_ the
idea of having the modems on a Portmaster. (I remember when a PDP-11 clone
had trouble with more than six or so PPP connections at 9600bps; we've come
a _long_ way since then, but I don't have a feel for the load a PPP connection
would put on the main machine. Nor do I know that such a connection would
make sense for grex's dial-in modems when directly connected to the grex
machine.)
|
cross
|
|
response 102 of 237:
|
Jul 24 04:16 UTC 2003 |
This response has been erased.
|
gelinas
|
|
response 103 of 237:
|
Jul 24 04:20 UTC 2003 |
*I*'m suggesting we should provide PPP.
|
aruba
|
|
response 104 of 237:
|
Jul 24 10:52 UTC 2003 |
This discussion really belongs somewhere else besides the system problems
item, I think.
We have occasionally, over the years, discussed allowing PPP connections to
Grex, because fewer and fewer computer users even know there *is* another
kind of modem connection you can make. People connectiong to Grex via PPP
wouldn't be allowed to http out onto the internet, but they could access
Grex's web pages that way. (We don't want to compete with real ISPs.)
|
mary
|
|
response 105 of 237:
|
Jul 24 12:33 UTC 2003 |
I'll follow-up on the modem question.
|
gull
|
|
response 106 of 237:
|
Jul 24 19:19 UTC 2003 |
I'd be careful about using any modem that could be described as "cheap"
for dial-in service. I haven't had good luck with that combination.
For example, while US Robotics Sportster modems work great for dialing
out, I had all kinds of reliability problems with a couple of them at
work until I replaced them with Couriers. The Sportsters simply would
never complete the initial negotiation if certain other brands of modem
tried to dial into them.
|
cross
|
|
response 107 of 237:
|
Jul 24 22:01 UTC 2003 |
This response has been erased.
|
dcat
|
|
response 108 of 237:
|
Jul 24 23:56 UTC 2003 |
/c is full again. from df:
/dev/sd4a 1944365 1749942 0 100% /c
|
keesan
|
|
response 109 of 237:
|
Jul 25 14:57 UTC 2003 |
I dialed 7615041 and my login timed out after 120 seconds without even giving
me a login prompt. Dialed 7613000 and got instant login prompt.
|
russ
|
|
response 110 of 237:
|
Jul 26 13:18 UTC 2003 |
WARNING TO ADMINS: The failure of one port as Sindi details in #109
is exactly what presaged last week's total failure of the terminal server.
|
tpryan
|
|
response 111 of 237:
|
Jul 26 15:06 UTC 2003 |
Right now, as I am dialed in, the good computer is burning a
CD. The computer to grex with is the 25Mhz, 4meg of memory machine.
BTW, when I telnet from M-net my pager goes screwy and pages more
lines that I want. Any clue?
|
dcat
|
|
response 112 of 237:
|
Jul 26 19:15 UTC 2003 |
resp:111 - probably your terminal client isn't communicating properly what
the size of your window is. Depending on what terminal you're using, you can
find out how big it is --- in PuTTY, drag one of the corners a little bit,
and look to the upper left corner --- and then use that number in 'stty rows
<X>'. Or use the 'change' program, which basically does the same thing
for you.
|
keesan
|
|
response 113 of 237:
|
Jul 27 03:55 UTC 2003 |
The following is a failed delivery message from an MSN account. Why are
the at signs turning into AEA? A friend cannot get mail from her friend
with MSN, he has had to retain his yahoo account to write her.
>
> ----- Original Message -----
> From: postmaster+AEA-mail.hotmail.com
> To: eepitt2+AEA-msn.com
> Sent: Saturday, July 26, 2003 11:12 AM
> Subject: Delivery Status Notification (Failure)
>
>
> This is an automatically generated Delivery Status Notification.
>
> Delivery to the following recipients failed.
>
> dpfitzen+AEA-cyberspace.org
>
>
>
>
> ATTACHMENT part 2 application/octet-stream name=ATT00037.dat
> ATTACHMENT part 3 message/rfc822 name=Test Message.email
> From: "EDWARD PITTENGER" <eepitt2@msn.com>
> To: "Dorothy Pfitzenmier" <dpfitzen@cyberspace.org>
> Subject: Test Message
> Date: Sat, 26 Jul 2003 11:13:57 -0500
>
> This is a test message to Dorothy from my MSN E-MAIL.
>
> Bud
|
keesan
|
|
response 114 of 237:
|
Jul 28 03:12 UTC 2003 |
Here is more info from the person who cannot use MSN email to write grex:
What is the rfc822; ?
The Diagnostic-Code looks like Marcus's humor.
Subject: Attachment from Bounce Back
I did get this verbiage attatched to the bounce back messge, but it
does not make sense to me. I hope it does to Sindi. Every thing that
follows is the attachment (except for the couple of lines that YAHOO
always attaches.
Reporting-MTA: dns;hotmail.com
Received-From-MTA: dns;mail.hotmail.com
Arrival-Date: Sat, 26 Jul 2003 09:12:26 -0700
Final-Recipient: rfc822;dpfitzen@cyberspace.org
Action: failed
Status: 5.0.0
Diagnostic-Code: smtp;552 And he that sat upon the throne said, Behold,
I make all things new.
pleased to meet you
250-EXPN
250-SIZE 100000
250 HELP
NING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-AUTH GSSAPI
250-DELIVERBY
250 HELP
250 HELP
HELP
0-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-X-LINK2STATE
250-XEXCH50
250 OK
signed.
which
220 have no reverse-DNS (PTR record) assigned.
tions from IP addresses which
220 have no reverse-DNS (PTR record) assigned.
is expressly PROHIBITED.
Rinet-Turbo machines without prior WRITTEN permission
220 is expressly PROHIBITED.
|
gelinas
|
|
response 115 of 237:
|
Jul 28 03:19 UTC 2003 |
RFC 822 is the document that standardised the text of Internet (at the time,
Arpanet) messages.
|
keesan
|
|
response 116 of 237:
|
Jul 28 03:42 UTC 2003 |
Srw says grex is bouncing mail from this MSN account as spam and that there
have been similar problems with other mail from MSN.
|
dcat
|
|
response 117 of 237:
|
Jul 28 23:18 UTC 2003 |
Received these messages when i logged in tonight:
mesg: Unable to find your tty (ttyp9) in utmp file
mesg: Unable to find your tty (ttyp9) in utmp file
|
dcat
|
|
response 118 of 237:
|
Jul 28 23:28 UTC 2003 |
Shortly after the previous message, about two minutes after joining party,
i got the following:
Party Process Killed.
zsh: 16042 terminated ( mesg -h n; /usr/local/bin/party; mesg -h y )
When I tried to rejoin party, i got a message from PuTTY about my connection
having been killed.
|
janc
|
|
response 119 of 237:
|
Jul 29 00:28 UTC 2003 |
You're making ssh connections, right? At some point today Grex was out
of ttys for what reason I know not. Under such circumstances ssh will
connect you without a tty. This really stinks, as lots of stuff doesn't
work right, like backspace keys. This may have something to do with #117.
If you were connected without a tty, then robocop would have eventually
killed your processes, as it dislikes all user processes not associated
with a tty....yup, I just checked the log...robocop killed you.
|
dcat
|
|
response 120 of 237:
|
Jul 29 04:01 UTC 2003 |
ah. okay.
|
charcat
|
|
response 121 of 237:
|
Jul 30 04:09 UTC 2003 |
I also dial into grex about half the time (I find dial up is faster than my
internet connection) but my mother's computer can only use dial up
|
jaklumen
|
|
response 122 of 237:
|
Jul 30 04:41 UTC 2003 |
This may not be a system problem, but for some odd reason, Backtalk has
the font size set so big that it's hard to read responses.
|
russ
|
|
response 123 of 237:
|
Jul 30 04:44 UTC 2003 |
2125 hours, dialing -3596:
"Welcome to Grex! It may take a few seconds to connect."
[1 minute 40 seconds later]
NO CARRIER
Same story on -3000 a few minutes later. I'm assuming Grex was down.
|
gelinas
|
|
response 124 of 237:
|
Jul 30 05:39 UTC 2003 |
Yup. 'Twas being switched back to the UPS.
|
