Jump to content

Chris T Fer

Members
  • Posts

    7
  • Joined

  • Last visited

About Chris T Fer

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Canada
  1. I ended up submitting a ticket. None of my clients have connected to ECA in 2 days. At the moment they have confirmed its a cloud issue and they're working on it. Hopefully resolved soon!
  2. I just tried to install a new client and although it installed ok and the agent is running... and I can even see it in the cloud... but the cloud administrator doesn't detect that the agent is installed. Can't see the IP address... etc... Here's the error... Agent peer certificate with subject 'CN=Agent-REMOVEDTHISTEXTTOHIDEINFO' issued by 'O="ESET, spol. s r.o.", OU=ECA 2017, CN=Eset Cloud Administrator External CA' with serial number '49c2' is invalid now (NodVerifyTrustResult: 42, NVT_NotTrusted, 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 Makes me think there is a definite communication error from our clients to the cloud. How would I fix this? The only thing that has changed in the office would be windows updates and the fact that many staff are working from home using VPN
  3. seeing replication errors. Yes using ESET Cloud administrator ERROR: SendRequestAndHandleResponse: Rpc message response INTERNAL_ERROR. Error message: Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: REMOVEDTHISTEXTTOHIDEINFO.a.ecaserver.eset.com:443, Connection established: true, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: REMOVEDTHISTEXTTO HIDEINFO, Sent logs: 0, Cached static objects: 0, Cached static object groups: 0, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0] All replication attempts: 119
  4. New user to ESET Endpoint protection and cloud management. I had set a firewall policy to allow vpn and rdp to work for a few users that needed it, It worked great to push the policy out to those users that needed it. I can check each client configuration and see the policies in place for the ones I assigned. Now that more are working from home I assigned the policy to more client PC's but they aren't picking it up for some reason. Its been a few days and still nothing... Any ideas or tips? A a workaround I've had to manually configure the firewall on each client to get get by... but for obvious reasons this isn't ideal. thanks in advance. Chris
  5. Ah ha! Found the troubleshooter. What an awesome tool! Got everything working. Now if I understand things correctly, I just need to work on setting up a policy with this rule in the Cloud Administrator so I can assign it to the users that need this functionality. Am I on the right track?
  6. Thanks for the replies... you'll have to excuse my ignorance but where would I find the Network Troubleshooting Wizard? And if I turn on learning mode, what learning mode settings do I need to set?
  7. Hi there! New ESET Endpoint Security User here... We just got things installed and although we can use Remote Desktop within the office between PC's and Servers, when I connect remotely via VPN and then try RDP it doesn't work. Oddly enough it DOES work when I remote to servers but not for PC's. Also, if I disable the firewall on a PC and THEN try it, it does work. I had found a couple of old articles in this forum on this issue but they are archived. Can anyone drop me some steps to adjust the firewall settings to allow RDP from "outside" our network via VPN? And what would be best as far as setting this up for a few users... via policy? Thanks in advance for any help! Chris
×
×
  • Create New...