1 Rookie

 • 

116 Posts

February 15th, 2018 01:00

I've also tested it (9.1.1.4) and it works like for bingo: without admin access I got "administrator: No privilege to view administrator list;", after nsraddadmin I can see the list.

I think it's worth a try to test it with FQDN / and/or for the specific IP/hostname if you have multiple adapters.

If nothing seems to work you can give a try to run: nsraddadmin -u "root@*", but make sure that you remove this immediately after testing..

1 Rookie

 • 

116 Posts

February 13th, 2018 23:00

I think the user 'root@nwclient' must be a networker administrator to be able to see the list of the admins.

I don't understand why did you added 'root@nwclient' to nsrla and port ranges resources.. networker admins are stored in the 'NSR' resource. You should use nsraddadmin utility to grant networker admin privileges.

I don't see why do you need to see the list of admins from a client, but granting nw admin access to a client to be able to get this info is overshoot

12 Posts

February 14th, 2018 03:00

Thanks for answer

root@nwclient is already administrator

root@nwserver # nsraddadmin -u root@nwclient

134748:nsraddadmin: 'root@nwclient' is already on the 'administrator' list.

I've added the user as administrator into nsrla and port ranges resources  just to attempt to solve the issue.

NW8 allows to view 'administrators' attribute. The trouble is detected in NW 9.1.0.2 and NW 9.1.1.5

2.4K Posts

February 14th, 2018 04:00

The behavior is a bit strange but in fact you may be able to change a parameter (as root@client) but you will not able to see the administrator's list untill you use nsraddadmin on the NW server and add the appropriate account.

Verified with NW 9.1.1.5.

12 Posts

February 14th, 2018 09:00

I've removed root@nwclient manually via nsradmin, and added the user via nsraddadmin, there are no changes

12 Posts

February 15th, 2018 04:00

Thanks for advises,

the trouble was related with incorrect host configuration.

I assume 'my hostname' attribute on client's NSRLA resource must be equal with the user host in administrators of server side.

No Events found!

Top