From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] authentication help
Date: Mon, 9 Feb 2004 17:33:17 -0700 [thread overview]
Message-ID: <3ecfab0d6df4a2a82590a3ad63757410@plan9.ucalgary.ca> (raw)
In-Reply-To: <200402091754.48633.jhorey@cs.unm.edu>
> When I run "cpu -h <auth/cpu ip addr> -c ls /" on the cpu/auth server, I
> receive what I expect (a listing of all the files). However when I run that
> same command on my Plan 9 terminal, I receive "srvauth::auth server protocol
> botch".
that usually means your authdom= entry in ndb isn't what the auth
server thinks it is. run auth/debug from the terminal to see if
that's the case.
see other suggestions in the archives, particularly "telnet problem"
from 2003-Feb-11.
andrey
prev parent reply other threads:[~2004-02-10 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 0:54 James Horey
2004-02-10 0:33 ` andrey mirtchovski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ecfab0d6df4a2a82590a3ad63757410@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).