pedrommm
Members-
Posts
16 -
Joined
-
Last visited
Reputation
0 Neutral-
OK well, as it turned out i stuffed up I saved the last file and it named it fixlist(2) as the last one was already their. so when i ran the fix it used the prior fixlist. Log attached Anyway after it ran, i was able to restore the firewall settings and checked a couple of other things and all seems ok. No hopefully no harm no fowl. Having said that it seems that the fixlist process creates a restore point somewhere.?? So is the process reversible (just in case ) Fixlog.txt
-
Hello, I definitely did not do a restore manually, but i would note that on the 13th .. the first fix log you sent and I ran , timed out ?? would this have restored because of the time out ? You subsequently sent me a new fix log that went through ok . CCleaner has been uninstalled now . Yes i still need the Screen connect software. ScreenConnect Client (651e45d845fb48e3) (HKLM-x32\...\{890469FF-A48A-4B4D-92DB-E969BAFE3EFE}) (Version: 19.2.29494.7513 - ScreenConnect Software)ScreenConnect Client (9c627210f2739768) (HKLM-x32\...\{3EA04E81-7EA1-4ADF-977F-381551F040F2}) (Version: 21.6.3172.7787 - ScreenConnect Software) I have also had a network guy investigate the the issues this had with connecting to the domain which now seem to be sorted out. Apparently he removed the machine from the domain and then reset it to the domain again ( all gobly gook to me). Also disabled IPv6 Internet protocol service which was causing intermittent issues with joining the domain correctly. We also had to open a couple of ports in the firewall to get my print server to work correctly. Everything is running smooth as at the moment ? Having said all this should i run this latest fixtlist.txt you sent ? I am concerned it will reset the firewall again and i would need to recalibrate the settings again ??
-
Scan run as requested, log Attached. Also given the large number of intrusions i was getting from the open RDP port. I have been able to close that port to the outside world at my router level so RDP connections from within my domain are still possible which is all i needed anyway. RDP Brute force attacks have stopped. At this stage Malwarebytes seems to behaving correctly. msert.log
-
mbst-grab-results.zipFollowed all instructions and have attached the files as requested. At this stage Malwarebytes is running fine.. Though it always does following a reinstall.. I am getting continuous notifications of RDP Bruce force attacks though Is this something to be concerned about ? If not i probably need to turn off notifications as the popup notification happens continuously ?
-
Hello, Thanks for the reply... Yes this machine does connect to a domain controller.. It was my home computer which now just serves as print server.. I am not particularly computer savvy so bear with my dumb questions.. I do on occasion get an error logging due to domain issues but not often.. When I do a reboot normally sorts that out now, The FRST64 program you refer to.. i don't seem to have that installed, (i ran the MB Support tool to get the logs to attach) Should i download that program ? and continue with the fix as recommended. Also if this fix breaks something, can it be reversed ?