Jump to content

carmik

Members
  • Posts

    127
  • Joined

  • Last visited

About carmik

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Greece

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Please excuse my ignorance here: is this public license id the same as the license key he needs to activate?
  2. Hello Marcos, I'm afraid he did not use a license mail address. Can he extract the key from the other installations?
  3. Hello, a friend had bought a multi user/1 year subscription for internet security. The product was activated on all systems. Since a new machine was purchased to replace one of the existing ones, eset was uninstalled on the old rig. Upon installation on the new one the friend realized that he had lost the license key to activate eset on the new system. What can be done in this case?
  4. Thanks for (yet another) speedy reply! I've been using this facility to "tell" eset that our own network is a trusted one. The question is whether this policy would work not in the case that a system had a second NIC, but in the case of a single NIC that has two different networks assigned to it. Can you please confirm whether or not this is feasible?
  5. We have a scenario in which we have a number of endpoint security 8.x clients managed by ESET Protect, that should connect to a 2nd network (different gateway/subnet etc), which resides outside our security perimeter in order to run a single Windows application. Network considerations apart, one would go about it with a single network card by a) first configuring the network card in Windows to have an additional ip address/subnet mask b) configuring static routes to connect to the second network appropriately c) and finally connecting the "foreign" router to our LAN. I know, not a great idea but it's for an interim period and the other network is from a "fellow" agency. Now the deal is that our own network is configured in ESET Protect to be a safe network. This is done by setting a policy that setups Settings ->Network Protection->Firewall->Known networks to include our own/safe network. My question is: is this setting applied NIC-wide (ie with a single network card, the connection could be either public, or home/private) or is it IP-wide (in which case we could have a policy that sets our own network as safe -home/private- and another policy that sets the 2nd network as public)? If the former applies (settings are applied NIC-wide) could someone offer perhaps an idea to solve this problem? PS: We've also toyed with the idea of creating a virtualbox WIndows VM and have its vNIC associated with a VLAN to keep traffic fully separated. However, this requires a lot of administrative effort for initial configuration and deployment. Plus there are hussles like configuring Virtualbox on each pc to pass through USB devices like barcode hand scanners to the VM...
  6. Apologies for my late reply. I have tried from home to connect with a browser to one of these systems over https. It failed (I presumed something needed was missing to establish a successful connection) when I tried this at home. I still think that eset should provide a utility to easily identify what is/isn't reachable from the ESET infrastructure. It will help both detection and isolation of the problem, as well as help whoever performs corrective actions to verify that things have worked. I have raised an issue with the WAN admins, but lack of an utility like this means that they will not be able to actually tell whether thinks have been fixed or not (at least on their side). 10.xx.xx.17 is the eset protect server, which hosts the apache module for caching traffic (updates etc): so nothing special there. One other question: why is the client trying to resolve things via Google DNS? Is this a fallback mechanism?
  7. Apologies for my late reply. I will raise an issue with my provider. However: 1) Regarding http fallback to 91.228.166.42, I tried to open https://91.228.166.42 from my home connection as well as from another place and that failed. How can I (or the ISP sysadmins) easily tell that https access to these systems work? Asking here because from the looks of it, it is impossible to connect "normally" regardless of your (network) location (home/business). 2) Why is Google DNS used at all? This is a centralized and controlled environment. As such, your client should not try to connect to any DNS, apart from the provisioned one.
  8. 1) Some tool I can check connectivity to these address over 53535/udp? 2) What should I look for on my local DNS?
  9. Marcos, I've found out that we've run into a similar situation that we had about a month ago: some proxy perhaps in our infrastructure is blocking queries to resolve/categorize links and sites. I've reproduced this issue on another site, not administered by me. Is there some sort of eset tool that checks availability of services provided by the eset infrastructure and presents them in an easily translatable form (for example works/does not work)? Which servers/protocols are used to query URL categories?
  10. ESET Protect 8 (latest) and endpoint security 8 (latest) running on Windows 20H2 boxes happily, till yesterday. At that moment we discovered that social networking was not blocked for example. We have a general URL allow rule (whitelisted domains/URLs) followed by a category block rule that included various categories. Digging further it seems that all domains get characterized as not resolved ones. Indeed, by selecting to block only this category, everything (except our whitelisted domains) gets blocked. Has something changed in the infrastructure, is this a known issue?
  11. Seems like a bug after all: I've whitelisted miscellaneous (as a category) before the blacklisted categories, but URLs categorized as "no content found" are still blocked. I'll open a support ticket.
  12. Hello, on my server I've got a web access policy for Endpoint security products that (a) first allows certain URLs and then (b) blocks certain categories. What would happen when a user tries to access a site that is not listed in (a) or in the categories of (b)? That is, is it allowed or somehow default-blocked? Specifically we are receiving blocks from the content filter, for pages categorized as "No content found" (included in Miscellaneous), even though the entire Miscellaneous category is not listed under the categories in (b).
×
×
  • Create New...