Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!uwvax!rutgers!iuvax!pur-ee!uiucdcs!uxc.cso.uiuc.edu!sandrock
From: sandrock@uxc.cso.uiuc.edu
Newsgroups: comp.os.vms
Subject: Re: Proxy access
Message-ID: <195600002@uxc.cso.uiuc.edu>
Date: Thu, 12-Nov-87 12:17:00 EST
Article-I.D.: uxc.195600002
Posted: Thu Nov 12 12:17:00 1987
Date-Received: Sun, 15-Nov-87 08:29:39 EST
References: <8711022234.AA10014@ncsc.ARPA>
Lines: 29
Nf-ID: #R:<8711022234.AA10014@ncsc.ARPA>:-30:uxc.cso.uiuc.edu:195600002:000:1343
Nf-From: uxc.cso.uiuc.edu!sandrock    Nov 12 11:17:00 1987


> /* ---------- "Proxy access" ---------- */
> I have a problem with a hopefully easy solution.  Here's the scenario:
> Joe has accounts on VAXA and VAXB. Each account has proxy logins enabled.
> If Joe is logged on to VAXA, he can copy files to VAXB, or copy files from
> VAXB to VAXA, without having to specifiy username, password, disk, and
> directory.  However, if he's logged in to VAXB, he must specify his username
> and password.  Otherwise, the file goes to the default DECNET account, or,
> if he specifies disk and directory, he gets an "insufficienr privilege or
> file protection violation."  Both accounts have proxy access, and the FAL
> object in the NCP has proxy access both incoming and outgoing.  I don't know
> that much about networking, so I must be missing something.  Any ideas?
>
> Thanks in advance,
>
> Tom Williams
> vtcf@ncsc.arpa

     I had a similar problem, which may or may not apply in your case:
   if VAXB belongs to a VAXcluster called, say CLUS, you must not only
   specify VAXB::USERNAME, but also CLUS::USERNAME. In fact I found I
   had to specify proxies for all the nodes in the cluster, as well as
   for the cluster alias.
     It wouldn't surprise me if there was a better way to do this, but
   this was what worked for me.

     Regards,

        Mark Sandrock, (sandrock@uxc.cso.uiuc.edu)