Very Computer

Our network has a bunch of VAXstations.  On one particular system, Moe,
I cannot set up a network proxy for the SYSTEM account.  I have, however,
successfully established proxies for other accounts.

moe_jwright$ run authorize
UAF> sh /proxy *::*

 Default proxies are flagged with (D)

*::JWRIGHT
     JWRIGHT (D)

*::SYSTEM
     SYSTEM (D)

The proxy for JWRIGHT works fine:

moe_jwright$ dir 0::

Directory 0::SYS$SYSDEVICE:[JWRIGHT]

[a bunch of files]

...but the proxy for SYSTEM does not work:

moe_system$ dir 0::

Directory 0::SYS$SPECIFIC:[FAL$SERVER]

[a few NETSERVER.LOG files]

The problems are specific to Moe.  Moe also happens to be running
version T5.4-0K of VMS.  However, we have another T5.4-0K system
that works as expected (i.e., the SYSTEM account successfully
maps to the SYSTEM account).

I am stumped.  What could be causing remote SYSTEM account access
on this specific system to seemingly ignore the proxy entry and use
the FAL$SERVER account instead?

--
-------------------------------------------------------------------

This message is completely free of trans fatty acids.

=moe_jwright$ run authorize
=UAF> sh /proxy *::*
=
= Default proxies are flagged with (D)
=
=*::JWRIGHT
=     JWRIGHT (D)
=
=*::SYSTEM
=     SYSTEM (D)

Note:  In the above, you didn't tell us what your default directory was when
you ran AUTHORIZE.  This may be important.

=I am stumped.  What could be causing remote SYSTEM account access
=on this specific system to seemingly ignore the proxy entry and use
=the FAL$SERVER account instead?

SYS$SYSROOT is a searchlist.  Be sure that either:
        1)  Your network proxy database is in SYS$SPECIFIC:; or
        2)  If your network proxy database is in SYS$COMMON:, there's no
            network proxy database in SYS$SPECIFIC:.
--------------------------------------------------------------------------------

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.

If I've just changed my proxy database and there's still a SERVER_nnnn process
* around, the next FAL request will reuse that process, which still
carries with it the previous version of the proxy database.  I have to do
a STOP/ID= on each SERVER_nnnn process to have FAL reaccess the proxy database.

This usually fixes my proxy problem.

Larry Bleau
University of Maryland

301-405-6223