I'm not sure exactly whether it'll help (I have information from ISS that these params do not make any sense now), but try this: 1. in \ISS\issDaemon directory find file iss.access Check that in [\Roles\] section there are rows like this: --ISS Access 6.5-- [\]; [\Roles\]; [\Roles\KeyAdministrator\]; ..... [\Roles\KeyAdministrator\SERVERNAME_USERNAME\]; .....
where SERVERNAME - name of SP AS, USERNAME - name of the user account by which you're trying to manage this sensor. 2. in file \ISS\issDaemon\issDaemon.policy find row: master_console =S SERVERNAME; SERVERNAME - the name of AS. 3. Finally, the problem can be arisen due to the different crypto providers specified in sensor and in manager. This can be checked manually: /ISS/issDaemon/crypt.policy on the sensor and on the manager should contain at least one identical crypto provider. If crypto provider does not noted in crypt.policy, but you're sure that it's installed on machine, you can add info about crypto provider manually. Example of crypto provider information: [\encryption\provider1\]; ProviderType =L 1; ProviderName =S Microsoft Enhanced Cryptographic Provider v1.0; ExchangeName =S RSA_KEYX (1024 bit); ExchangeID =L 41984; ExchangeLen =L 1024; SecretName =S RC4 (128 bit); SecretID =L 26625; SecretLen =L 128; HashName =S SHA-1; HashID =L 32772; HashLen =L 160; [\encryption\provider2\]; ProviderType =L 1; ProviderName =S Microsoft Enhanced Cryptographic Provider v1.0; ExchangeName =S RSA_KEYX (1536 bit); ExchangeID =L 41984; ExchangeLen =L 1536; SecretName =S 3DES; SecretID =L 26115; SecretLen =L 168; HashName =S SHA-1; HashID =L 32772; HashLen =L 160; All files must be edited when issDaemon is stopped. --- Best regards, Sergey V. Soldatov. Information security department. tel/fax +7 495 745 89 50 tel +7 495 777 77 07 (1613) > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Javier Reyna Padilla > Sent: Tuesday, February 27, 2007 8:50 PM > To: [email protected] > Subject: [ISSForum] Cannot get master status on network sensor > > I have a windows box with 3 instances of network sensor v.7 > all of them are properly registered and working on > siteprotector sp2.61. Two of them are succesfully updated and > I can install a policy on this 2. But on the third i cannot > install a policy nor upgrade it, I get "unable to acquire > master status" error, when I tried to do some action on it. I > cannor find something usefull on ISS KB. Any suggestion? > > _______________________________________________ > ISSForum mailing list > [email protected] > > TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to > https://atla-mm1.iss.net/mailman/listinfo/issforum > > To contact the ISSForum Moderator, send email to [EMAIL PROTECTED] > > The ISSForum mailing list is hosted and managed by Internet > Security Systems, 6303 Barfield Road, Atlanta, Georgia, USA 30328. > _______________________________________________ ISSForum mailing list [email protected] TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo/issforum To contact the ISSForum Moderator, send email to [EMAIL PROTECTED] The ISSForum mailing list is hosted and managed by Internet Security Systems, 6303 Barfield Road, Atlanta, Georgia, USA 30328.
