…Your Nextdoor IT Professional

Posts by Joey Kappe

GPG-Error when updating Ubuntu machines

By on May 29, 2013 in Ubuntu | 0 comments

When updating Ubuntu machines I often get this error: W: GPG error: http://archive.debian.org etch/updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 16126d3a3e5c1192 Solution: Receive publickey for the source from the keyserver with the following command: sudo apt-key adv –recv-keys –keyserver keyserver.ubuntu.com...

Read More

RSA Authentication Manager Issue – Node secret mismatch

By on Oct 15, 2012 in RSA | 8 comments

Follow these instructions if you get following error messages in your Authentication Monitor: “Node secret mismatch: cleared on server but not on agent” “Node secret mismatch: agent and server using different node secrets” 1. Open the Security Operations Console and check out the realtime authentication monitor. You gonna find it in the RSA Security Console in the menupoint Reporting. Reporting –> Real-time activity monitors –> Authentication activity monitor 2. Clear the secret node on your RSA Server and your Cisco ASA. The secret node is stored in the ASA´s flash drive. It should have a name like 192-168-250-100.sdi You can clear the ASA´s node secret in Access –> Authentication Agents –> Manage Existing. Click on the ASA to open up the dropdown menu, choose Manage Node Secret. Ccheck the box “Clear the node secret” und save your settings. Within the first authentication the RSA server und the ASA will negotiate a new Node Secret. Make sure that the time is in sync on the RSA Server and the Client before establishing a connection. 3. Now it should be fine. Sometimes you have to repeat step 2. I had to delete the secret 4 times before the authentication worked correctly.   This article helped you? Nice! Please take 1 minute of your time and leave a comment, I would appreciate that. Thank you...

Read More

RSA Authentification Manger 7.1 SP4 – Configure Primary- and Replicaserver

By on Aug 14, 2012 in RSA | 0 comments

Here are some commands to configure the primary- and the replica server: I am using the rsautil tool for this operation. You can find it in the directory: C:\Program Files\RSA Security\RSA Authentication Manager\utils   With this command you setup the server to a primary server:   rsautil setup-replication -m yoursuperadminpasswordhere -a set-primary -V   Output:  Setup Replication ims-2.0.4-build20101208044128 Copyright (C) 2010 RSA Security Inc. All rights reserved.   %% Running at: testserver:[kcsdgqh5] %%   ======================================= %       Setting up Primary Site       % ======================================= [Primary] Port      : 2334 DB name   : kcsdgqh5 DB host   : testserver. de Instance  : testserver. de Site name : testserver. de   Is this correct (Y/N): y   %% Starting configuration — Configuring primary — Setting up queues at [kcsdgqh5] — Adding [AM] supplemental logging at [kcsdgqh5] — Adding [IMS] supplemental logging at [kcsdgqh5] — Executing [AM] primary scripts at [kcsdgqh5] — Executing [AM] common scripts at [kcsdgqh5] — Registering primary information — Executing [IMS] primary scripts at [kcsdgqh5] Done…   You add the Replica server with the following command:     rsautil setup-replication -m yoursuperadminpasswordhere -a add-replica-online -f C:/RSA/Testserver2-replica.pkg -V   You can check your Replication status via rsautil setup-replication -a report -m...

Read More