earlonics

Hi raingeek.... I've Also been banging my head against the wall all day on this today 6 installs and reviewing group policies and Firewall settings, its been for me a result of the AD account password and the one I enter in the Reporting module.... it might well be something to do with password length, I had a repeatable…

Folks I had the Same problem it was fixed by me changing Yes Changing AD password, its either too long or my password contained a " speech mark once I changed my password to something simple I was able to login and run reports. Not sure why this should happen since i can login using my AD via the webportal no problem is…

Thanks for fast responce. This helps to explain things when creating the report and presenting information on to Senior Exec's

Nerdcentric, I know this is an Old thread and wondered if you or anyone has configured LEM to detect such an attack, I've noticed that this does provide some useful footprints when triggered such as creating Help_*.txt files in every folder it encrypts, so in my thinking if someone started reading files saving files and…