Ubtree

ESET support has ascertained that the problem is caused by Protocol Filtering of the scanner's IP address, and that the solution is to set that IP address as an exception for Protocol Filtering.

ESET is operating in interactive mode on all 3 PCs.

I am not experiencing any problems communicating between the PCs on the network. For a week after the scanner was installed on the network, I repeatedly tried to perform scans from each of the PCs, and rebooted each of the PCs a number of times. During this period, ESET never, on any PC, asked whether access should be allowed from the scanner IP address. Then, out of the blue, on one of the three PCs ESET asked whether to allow the scanner's IP address to communicate with that PC; I confirmed that communication should be allowed, and I was then able to scan to that PC. For whatever reason, on the other two PCs ESET has still not asked whether to allow access from the scanner's IP address (even though it is operating in interactive mode), and is blocking access. I therefore need to manually configure ESET to allow access from another IP address on the network.

I have a scanner on a network with 3 PCs (one running Windows XP, one runnning Windows 7 and one running Windows 10), all protected by ESET Smart Security. I have been unable to scan to any of the PCs over the network, and have spent several hours over the last week troubleshooting the issue. Today, for the first time, ESET asked whether to allow access to the PC from the scanner's IP address. I confirmed that access should be allowed, and after this I was able to scan to that PC for the first time. I clearly need to do this on the other PCs, but my understanding of ESET doesn't extend to doing this without first being prompted by ESET. Can someone point me to where this needs to be done within ESET?

Thank you for the quick reply, TomFace. i understand.

I have been able to update to 8.0.312.0 on one of my PCs, but on my other PC Smart Security update reports "Installed version 8.0.304.0 is up to date". Can anyone suggest why the auto-update is not working?

Sorry. Posted in the wrong forum! EEST update status.pdf

I have re-run the backup twice with ESET active; on both occasions, the backup stopped part way through, without any notification by ESET. Last night, I also tried running the backup with ESET disabled, and this time, it completed normally. I have checked the Personal Firewall settings. For each TrueImage module, inbound traffic is set to "Ask", and outbound traffic is set to "Allow).

Although this incident happened a few days ago, the Detected Threat log is empty, and in Setup, log files are set to keep records for 90 days,

Then switch to learning mode for a while until all necessary rules are created if you don't want to use automatic mode. I think that you have misunderstood the help that I need. According to the ESET Knowledgebase: "Learning mode is not secure, and should only be used until all rules for required communications have been created." All the rules required for communication had already been created: I had carried out the backup process without any problem on many previous occasions. ESET has reported a potential threat that I need to understand. To this end, I need to know: Was the original warning a real external threat (and therefore I was correct to block it), or could running a backup program on the PC have caused ESET to report that a remote computer was attempting to access an application on my PC? Where would I find a log reporting that warning, and the action taken in response to the warning?

Yes, I run ESET in interactive mode.

Halfway through a 14 hour backup (a process that I had carried out without any problem on many previous occasions), ESET Smart Security 8 warned that a remote computer was attempting to access an application on my PC; the IP address given for the remote computer was my router / internet gateway. TrueImage was still running (ie. the window was still open, and there was no error message), but it had suspended backing up files. I had no idea whether the ESET warning was a real threat, or why this event had happened at this point, and so I responded to the warning by asking ESET to block the activity on this occasion. (I did not check the box asking for the instruction to be remembered on future occasions.) The backup did not resume. Since then, I have twice tried to backup the computer, but on both occasions TrueImage simply stopped backing up files when it was only halfway through ( - the program continued to run, but progress ceased). I cannot find any log entries that relate to this incident (including any reference to the remote computer attempting to access an application on my PC). My initial questions are: Was the original warning a real threat (and therefore I was correct to block it), or could it have related to the TrueImage backup process (in which case I should have permitted it)? Where would I find a log reporting that warning, and the action taken in response to the warning? Any help would be greatly appreciated.