My original question was:
>
> I'm using the Sunsoft Print Client (SSPC) and the Solstice Adminsuite version
> 2.1 . I'm running Solaris 2.5 and NIS+
>
> I'm unable to add or remove printers using Solstice, the GUI administration
> tool.
>
>
> I've spoken with SUN and have upgraded to Adminsuite 2.2, installed the FNS
> packages from the 2.5.1 CD, all with no luck.
>
> They sent a document telling how to use 'fnunbind' and 'fncreate_printer' to
> add and remove printers. When I try to use these, I get a "No permission" error
> for the printer I'm trying to add/delete. (I'm tried these both as 'root' and a
> member of the 'sysadmin' group).
>
> I've found very little information on FNS (which SSPC uses to distribute the
> printer maps) and am getting little help from SUN.
>
> I'd appreciate any advice/info. Due to the fact that I cannot do the
> fnunbind and fncreate_printer, I believe it is an FNS/NIS+ problem and not an
> SSPC problem.
>
>
> Thanks for any help/advice you can give.
>
> I will summarize.
>
>
Well.... I didn't get a single response, but solved the problem myself.
It was an authentification problem related to a corruption of the credentials that
happened several weeks ago (related to not doing a 'chkey' after changing root
passwords ...a whole 'nother story).
Sun sent me the following procedure to fix the problem with the credentials:
------------------------------------------------
Do all the the following as root in the bourne shell
*** kill nis_cachemgr and startup rpc.nisd at level zero on all nis+ servers. ***
kill <PID for rpc.nisd> on all nis+ servers.
kill <PID nis_cachemgr> on all nis+ servers.
rpc.nisd -S 0 on all nis+ servers.
*** Now redo the creds for the root master on the root master ***
nisaddcred -p unix.<root master>@`domainname` -P <root master>.`domainname`. des
enter the root passwd when prompted for passwd.
(If the above command hangs then rm /etc/.rootkey and kill keyserv)
*** next do the following on the root master ***
rm /etc/.rootkey
kill < PID for keyserv>
*** EXECUTE THE FOLLOWING COMMANDS ON THE ROOT MASTER, NOTE THE TRAILING DOTS THAT YOU
MUST HAVE ON THE NEXT 3 COMMANDS
***
nisupdkeys org_dir.`domainname`.
nisupdkeys groups_dir.`domainname`.
nisupdkeys `domainname`.
*** nisping all 3 objects on the root master ***
nisping org_dir
nisping groups_dir
nisping `domainname`
*** On the root master execute the following. ***
keylogin -r
enter the root passwd when prompted
*** EXECUTE THE FOLLOWING COMMANDS ON THE REPLICA SERVERS, NOTE THE TRAILING DOTS THAT
YOU MUST HAVE ON THE NEXT 3
COMMANDS ***
nisupdkeys org_dir.`domainname`.
nisupdkeys groups_dir.`domainname`.
nisupdkeys `domainname`.
*** Now startup rpc.nisd at level 2 and startup nis_cachemgr on all servers ***
kill rpc.nisd -S 0
rpc.nisd
/usr/sbin/nis_cachemgr -i
----------------------------------------------------
This fixed the credentials problems, however if one is using FNS (as does
SSPC), there is also an ctx_dir.`domainname`. on which you must use the
"nisupdkeys" command. So, the following command should also be run on the root master
and replicas at the appropriate point in the above procedure.
nisupdkeys ctx_dir.`domainname`.
After performing this command, I was able to modify the FNS information used by the
SSPC software.
David Klamet
Unix Administrator
AlliedSignal Commercial Avionics Systems
MD #S6
11300 Corporate Ave
Lenexa, Ks. 66219
Ph. (913) 768-2526
Fax (913) 791-1337
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:55 CDT