Andrei-I 0 Posted 12 hours ago Share Posted 12 hours ago Hello, The trojans in my system keep being recreated despite Eset finding no issues. I have checked the Network Inspector and found that some connections are blocked. Could these be a sign of an infected router? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,267 Posted 11 hours ago Administrators Share Posted 11 hours ago Were the trojans detected by ESET? If so, could you please post the appropriate records from the Detections log? Quote Link to comment Share on other sites More sharing options...
itman 1,746 Posted 7 hours ago Share Posted 7 hours ago Is IP address, 192.168.1.1, your router/gateway or is it your PC network address? Quote Link to comment Share on other sites More sharing options...
Andrei-I 0 Posted 3 hours ago Author Share Posted 3 hours ago 3 hours ago, itman said: Is IP address, 192.168.1.1, your router/gateway or is it your PC network address? This is my gateway, I suppose. Quote Link to comment Share on other sites More sharing options...
itman 1,746 Posted 1 hour ago Share Posted 1 hour ago 11 hours ago, Andrei-I said: I have checked the Network Inspector and found that some connections are blocked. First, to run the Eset Network Inspector tool, your Eset existing set up network connection profile must be set to Private mode. The Eset network connection profile assignment by default is set to Automatic. This in turn defers to the current Windows firewall profile which is set to Public by default. Open Eset GUI and check your Eset network connection and verify that Connection profile is set to Private. If not, manually set the connection profile to Private. Next, go to the Tools section and select Network Inspector. Now select the Scan your network tab. Eset will proceed to scan your network and devices for network vulnerabilities. The scan will run for a while. When the scan completes, Network Inspector will either show; 1. No vulnerabilities found or; 2. What network devices have one or more vulnerabilities associated with them. Finally, reset Eset network connection back to Public if that was its initial setting. Ref.: https://help.eset.com/essp/17/en-US/idh_page_homenetwork_protection.html Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.