This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Lansweeper Community
- Forums
- Archive
- False RPC Errors
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Register to ask a question, start a topic or share an idea
Join the Community
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-17-2011 07:50 PM
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......
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......
Labels:
- Labels:
-
Archive
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-22-2011 09:04 AM
please contact us at support@lansweeper.com for this problem
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-18-2011 01:47 PM
It does
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-18-2011 09:06 AM
Can you check if the fqdn name of the workstation resolves to the correct IP.
New to Lansweeper?
Try Lansweeper For Free
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now
Related Content
