>>> On 12 Nov 1997 11:42:41 -0600, js@cctechnol.com (Johnie Stafford) said:
js> I don't even remember what started all this, but now I have my account
js> all messed up. This morning it seems that solstice can't figure out
js> what to call my domain. Up until today everything was working
js> fine. But now if I have the domain set to 'cctechnol.com' then when
js> solstice fires up it says that isn't a valid domain. So I change it
js> back to 'cctechnol.com.' and try to solstice to change the password on
js> my account and I get an error dialog with this message:
js> The operation failed with this status:
js> modify_user method failed: /usr/bin/nisaddcred: domain of principal
js> 'js.cctechnol.com..' does not match destination domain
js> 'cctechnol.com.'.
js> Should only add DES credential of principal in its home domain
js> /usr/bin/nisaddcred: unable to create credential.
js> I get 'Permission denied' when I try to change my password as either
js> me or root. 'chkey -p' gives me a cannot generate netname.
js> I'm seeing this in the syslog files:
js> Nov 12 11:32:30 kraken nisd[149]: _svcauth_des: no public key for nobody or uni
js> x.1018@cctechnol.com
js> I've tried restarting the rpc daemons and even rebooting. Nothing
js> seems to work.
Thanks to all that responded.
Gerhard Grasboeck suggested that the problem might be with Solstice
related to Bug ID #1238611, which has no patch and only a
workaround. Here is what he had to say:
> My current status of information about this problem is this:
> This is a known NIS+ bug (according to SUN) experienced by many users, but not
> yet fixed. There is also a workaround to this problem. You can find it in the
> attached Bug Report #1238611 from SUN.
>
> I myself have nearly no NIS+ experience, but could use this report to work
> around the bug and do the required NIS+ administration tasks (although during my
> first read of the document i could not see the relation of the bug described
> there to my problem).
> The bug seems to be within the solstice NIS+ GUI. When i created or modified a
> user without 'credential table setup' checked and than added credentials
> manually as described in the report, everything worked fine.
My solution:
I finally found somebody at Sun that found a solution. Although I am
running Solaris 2.6, Solstice AdminSuite 2.3 has been around since
Solaris 2.5, but there is a patch needed to make it work correctly
with 2.6. I downloaded the Solstice AdminSuite Jumbo Patch (104468-06)
from sunsolve1.sun.com and it solved the problem. There is also an
i386 patch available, 104469-06, to solve the same problem for the
i386 architecture.
If you're running AdminSuite under Solaris 2.6 you need this patch.
Johnie
-- ============================================================================== Johnie Stafford, System Administrator * Phone: (318) 261-0660 C & C Technologies, Inc. * Fax: (318) 261-0192 730 East Kaliste Saloom Road * E-mail: js@cctechnol.com Lafayette, LA 70508 * URL: http://www.cctechnol.com ==============================================================================