cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
David_Elliott
Engaged Sweeper II
Background info: AD environment. Firewall off by GPO. Active scanning set to 11am every day. Scanning target is nearest domain controller.

I inherited this install from a former employee and have begun work on cleaning up the data. Last week I deleted all the computers from the Lansweeper DB using the manager tool.

This week, my RPC errors are through the roof. Sitting at around 98% daily. Previous scanning was set to midnight so I adjusted to work hours hoping it would hit more machines that were turned on. Number hasn't really improved.

But here's what's weird. When I look at the top of the RPC error list and then do a test connection, Lansweeper has no trouble communicating with the workstation. I then trigger a full scan and everything populates like it should.
I've attached screen shots to show this happening in a matter of minutes.

Scratching head......
3 REPLIES 3
Hemoco
Lansweeper Alumni
please contact us at support@lansweeper.com for this problem
David_Elliott
Engaged Sweeper II
It does
Hemoco
Lansweeper Alumni
Can you check if the fqdn name of the workstation resolves to the correct IP.