From: Pace Willisson pace@blitz.com
Subject: Can't cpu(1) to my cpu/auth server.
Date: Wed, 13 Sep 1995 13:05:38 -0400 [thread overview]
Message-ID: <19950913170538.1IVt-4My_no3fumBpX8PZSR6lBWWegFzUnmx6OD0d-g@z> (raw)
>cpu: can't authenticate: p9auth: can't connect to AS
Are you on a subnet of a "natural" network? I think I made this work
when I added an extra ipnet entry in /lib/ndb/local for my parent class
C network. Install made an entry like this:
ipnet=blitz ip=204.32.90.32 ipmask=255.255.255.224
ipgw=204.32.90.33
fs=etti.blitz.com
auth=kamar
then, I added
ipnet=blitzopus ip=204.32.90.0 ipmask=255.255.255.0
ipgw=204.32.90.33
fs=etti.blitz.com
auth=kamar
Pace
next reply other threads:[~1995-09-13 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-13 17:05 Pace [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-09-13 14:11 tbcc!bwc
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=19950913170538.1IVt-4My_no3fumBpX8PZSR6lBWWegFzUnmx6OD0d-g@z \
--to=9fans@9fans.net \
/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).