Jump to content

cdfosburg

Members
  • Posts

    16
  • Joined

  • Last visited

About cdfosburg

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA
  1. Hey Everyone, I searched around the forum and I did not see an answer for this. If I am running the Virtual Appliance, is there a way for me to convert that to a Windows Server 20012 R2? Meaning can I back up all my clients and configs and restore to the Windows platform. It seems like the Virtual Appliance is next to impossible to manage and upgrade. Thank you, Chris
  2. Hi All, I want to confirm a thought I have. If I delete an object form ERA, will it be re-created when the computer checks back in? Thanks, Chris
  3. I would like to chime in that I am seeing the same. Let me give you some information about my setup. I am running the ERA 6.3 Linux Virtual Appliance. Restarting the ERA server does not seem to resolve the issue. I have not restored the appliance to an earlier time. When I look at client details, I can see all information about the NICS, OS version etc. Clients are physical machines, not virtual. I am not sure how to check the logs on the virtual appliance.
  4. Is that not what I setup in the above screen shot?
  5. Hello, I have the below set in my policy, however I am still being alerted to "Operating system is not up to date" when looking at the clients.
  6. Hello All, I am curious to know if anyone has some best practices regarding policies with the ESET product? I have one in place now with my security product for my clients, but I am curious if I should deploy others as well.
  7. Hello, I am running the most current version of ESET RA 6 and I have some servers that have ESET File Security installed on them. Some of them are showing verision 6.3.12004.0 and others 6.3.12006.0. I cannot seem to locate why some of them are off a bit. I have two that show this was that are both on Server 2012 R2 Standard.
  8. Hello All, Is there a recommended process to update CentOS when using the virtual appliance? Thank you, Chris
  9. I am using the Virtual Appliance 6.x so I am not sure of the self signed password that was given to the CA during creation.
  10. When I attempt to create a new Server Cert using the existing CA, I get the below. Failed to create certificate: Creating and signing peer certificate failed. Check input parameters for invalid or reserved characters, check certification authority pfx/pkcs12 signing certificate and corresponding password.: Trace info: ParsePkcs12: Could not verify password (invalid password or corrupted pkcs12 structure
  11. I created both a new CA and a new CERT. These are the errors we are getting now. Error: CReplicationManager: Replication (network) connection to 'host: "204.186.2.60" port: 2222' failed with: Receive: NodSslWriteEncryptedData: Incorrect/unknown certificate or key format. Error Agent peer certificate with subject 'CN=Agent certificate for host 204.186.2.60' issued by 'CN=CA for Outside Computers, C=US' with serial number '01ccaa780f61734724b7d8db1070c26d0801' is invalid now (NodVerifyTrustResult: 6, NVT_NotTrustedRoot, X509ChainStatus: 0x10000, X509CSF_PartialChain) Peer certificate may be valid but can not be verified on this machine Check time validity and presence of issuing certification authority Error: VerifyDnsSubjectAltName: Hostname does not match any supported record in certificate SubjectAltName extension (dmi1-eset.corp.lehighgas.local,10.10.10.179,127.0.0.1) Remote host: 204.186.2.60
  12. Hello, We have certain situations where we want to protect remote computers that will not be part of the LAN or VPN. I have setup a public ip on my firewall and NATs as well. Pings and telnets to ports 2222 and 2221 tell me this is working. I am having issues with the certificate. I created a cert with the outside dns name of my eset, however the agent installer is throwing the error that host name does not match. Do I need to create a new cert and bind that to an agent installer in these cases? I also cannot create a peer cert, eset is giving me a long winded message about that as well. Thank you, Chris
  13. It appears this has wiped out my firewall config and now I cannot access my web interface. Any suggestions?
  14. This is really welcome feature! Thanks! Agreed, I am looking forward to that feature as well. Thank you for the heads up!
  15. Hello, Everything is working fine with ESET, except for the issue that I cannot ping the ip address of the server. I believe this has something to do with the firewall on the linux appliance provided by ESET. Anyone know how I can allow this or remove it. I cannot ping from multiple locations both on and off the subnet ESET is on. Thanks, Chris
×
×
  • Create New...