Jump to content

Multiple domains, some computers not checking in at correct interval


Recommended Posts

I have machines in a separate work group that are not apart of the domain, and none of the machines not in our domain only check in when they are turned on despite the policy being applied for every 10 minutes. Has anyone experienced this issue before? We definitely have the policy applied to all computers that are running the client.  Any help would be appreciated.

Link to post
Share on other sites
  • Administrators

I'd recommend opening a ticket with your local ESET distributor. Trace logs from 1-2 troublesome clients as well as from the server will be needed for a start. It's possible that the logs will need to be generated with trace / debug verbosity but we'll see, maybe standard logs will be enough.

Link to post
Share on other sites
  • ESET Staff

Just to be sure, but by "only check in when they are turned on" you mean that do connect only once, after they are started, and another connection attempt is made after reboot? If so, I would double-check configuration of interval, especially in case "cron" based configuration was used.
Also as mentioned, troubleshooting of such device connectivity will be required, as issue might be also related to network configuration, which might prevent subsequent connections, especially in case there are other security/VPN products used or strict firewall configuration is applied.

Link to post
Share on other sites
7 minutes ago, MartinK said:

Just to be sure, but by "only check in when they are turned on" you mean that do connect only once, after they are started, and another connection attempt is made after reboot? If so, I would double-check configuration of interval, especially in case "cron" based configuration was used.
Also as mentioned, troubleshooting of such device connectivity will be required, as issue might be also related to network configuration, which might prevent subsequent connections, especially in case there are other security/VPN products used or strict firewall configuration is applied.

They only check in once despite the policy application of every 10 minutes, and the configuration choice is applied policy on the /all in the configuration console setting. I would think that if it were a fire wall issue it wouldn't allow the traffic by default, not just a single instance of the traffic. At first glance you would think it would be a domain issue, but i truly shouldn't matter as they are routed straight to the eset server. And it isn't every computer in the workgroup doing it, just most. Once I have the logs and don't see an immediate solution I'll revert with more. If I find a solution I will also report. I just wanted to make sure it wasn't a known issue or if someone had a similar problem what their experience was.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...