[20667] in Hotline Meeting
More on e52-364-p
daemon@ATHENA.MIT.EDU (John Chase)
Tue Jan 18 11:40:42 1994
To: hotline@MIT.EDU, op@MIT.EDU
Cc: jsd@MIT.EDU
Date: Tue, 18 Jan 94 11:40:22 EST
From: John Chase <jchase@MIT.EDU>
OP,
Could this in any way be screwwing up e52-364-p.
It's most consistant error is an ability to ping but
not recieve SNMP requests or be able to print.
John Chase
------- Forwarded Message
Received: from ATHENA-AS-WELL.MIT.EDU by po6.MIT.EDU (5.61/4.7) id AA19252; Tue, 18 Jan 94 11:33:18 EST
Received: from THOR.MIT.EDU by MIT.EDU with SMTP
id AA03151; Tue, 18 Jan 94 11:33:16 EST
From: jsd@MIT.EDU
Received: by thor.MIT.EDU (AIX 3.2/UCB 5.64/4.7) id AA35628; Tue, 18 Jan 1994 11:33:09 -0500
Message-Id: <9401181633.AA35628@thor.MIT.EDU>
To: John Chase <jchase@MIT.EDU>
Subject: Re: Problems with e52-364-p
In-Reply-To: Your message of Tue, 18 Jan 94 11:03:48 -0500.
<9401181603.AA19012@w20-575-33.MIT.EDU>
Date: Tue, 18 Jan 94 11:33:07 EST
I guess I wrote that too quickly. What I meant was that I have a non-kerberized
machine(trader) that uses arbor-eater as a remote print-server(i.e. it has a remote
print queue established for arbor-eater). I didn't know if a non-kerberized machine may
have caused problems with the authentication scheme(we have a user access list
in /afs/.athena/system/config/servers/e52-364-p/restrict.list) I am probably way
off but I thought I would let you know just in case. I can take a look at it
today(monitor it's activity) but for now it seems ok again. Thanks for the
help mun and I'll talk to you later.
John
------- End of Forwarded Message
