Jump to content

Outcast

Members
  • Content Count

    20
  • Joined

  • Last visited

Profile Information

  • Location
    USA

Recent Profile Visitors

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

  1. There is no way the servers were returning "invalid/expired license" results to a range of clients with legitimate licenses unless there was serious DB corruption. I expect the servers were either returning errors or totally unreachable, and the clients weren't smart enough to interpret this. I do this every day and I know the lingo, excuses, etc.
  2. Sounds to me like ESET's failover was manual and not automatic, and software clients aren't smart enough to retry before throwing an error. I bet rebooting the affected machines or perhaps simply recycling their network adapters will magically "resolve" the issue at least some of the time. The clients will be forced to reconnect, and they should reconnect to functional servers in so doing.
  3. I'm not still having issues, but this makes me wonder why issues in one DC would affect customers to this extent. Redundancy? Does ESET understand that it's embarrassing and annoying to be giving a presentation and have a goofy alert pop up, and then to waste time interpreting the alert? I've only been using the product for a matter of days. Is this a frequent thing?
  4. Now the message is gone. So, it was an ESET issue, as I thought. Authentication servers having issues? (Rhetorical) I don't want to sound rude, but the whole reason I'm trying to get away from Microsoft Defender in the first place is that it wasted my time.
  5. I'm currently running a trial of ESET NOD32 Antivirus 14.0.22.0 on Windows 10 Pro x64 20H2. This error just popped up on the main window: "ESET LiveGrid is not accessible ... The credentials used to access ESET LiveGrid servers are not correct." I have changed nothing. I don't even know what "credentials" it would be referring to. I was just sitting here, trying to work, not interacting with the product, and this notification/error appeared out of nowhere. I'm guessing this is an issues on ESET's side. What's going on?
  6. Mistake? The issue is resolved. For some reason, I had to exclude my email client from the local proxy (Proxifier) to make it work, but work it does. Thanks.
  7. I can tell from reviewing packet logs that the traffic on port 587 is indeed encrypted when "Enable TLS" is enabled, and yet it works. So my email server does support TLS on port 587, meaning that my web host's documentation is flatly wrong. Quite annoying. Thanks for the replies!
  8. I found that using "host.name:587" actually works whether or not "Enable TLS" is on. Since my server doesn't support SSL/TLS on 587 at all, I can only guess that when it's on, the application tries using TLS and then automatically backs off to plaintext.
  9. Because my mail server only uses SSL/TLS on port 465, I hadn't tried port 587 in that manner, only 465. As it turns out, 587 (i.e. host.name:587) works, but 465 (i.e. host.name:465) does not. Strange.
  10. I see the issue now. The ESET NOD32 Antivirus process ekrn.exe is attempting to use SMTP on port 25 (whether or not I have the "Enable TLS" setting enabled). My SMTP server uses ports 465 (SSL/TLS) and 587 (non-SSL) only. And the interface doesn't allow me to specify a port (I tried tacking :465 on the end of the hostname, to no avail).
  11. I'm currently running a trial of ESET NOD32 Antivirus 14.0.22.0 on Windows 10 Pro x64 20H2. I'm not having any other issues with the product, so hopefully this will be my last thread! I can't get email notifications to work. When I hit "Test" under TOOLS > Notifications > "EMAIL NOTIFICATIONS", I get "An error occurred while sending the test notification." with no indication of what the error is. - No log entry is created explaining what the problem is. - I've quadruple-checked my SMTP server host name, my username, and password. - I've tried using the SMTP server's IP addr
  12. It just started working for me, finally. I think someone fixed something behind the scenes. Thanks for the replies.
  13. I have both of those LiveGrid settings enabled. I did see one event log entry saying that there was an issue connecting to the LiveGrid servers--there was a yellow message on the main interface at the same time--but that was a couple days ago, when I was having connectivity issues in general. Currently there is no such indication in the UI or in the event log.
  14. I'm running a trial of ESET NOD32 Antivirus 14.0.22.0 on Windows 10 Pro x64 20H2. When I invoke the Tools > "Running processes" facility, nothing at all appears in the list. Clicking the refresh button doesn't help. It's supposed to show a list of all running processes, right? The name of the tool implies it does, but the window also says "This window displays a list of selected files with additional information from ESET LiveGrid." What does "selected files" refer to? Is this a known issue, or am I missing something?
×
×
  • Create New...