Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-30-2015 09:44 PM
I am the desktop admin here at a firm with around 200 assets and me and my SNI team have been struggling mightily to come up with a way to remove this error. We are getting it when we scan for computers and trying to make deployments so far. We changed the firewall settings to the liking of the instructions on Lansweeper which didn't change anything. The workaround we have so far is putting some script in our group policy that pushes a scan to the Lansweeper program, so for now everytime someone logs into their machine it shows up and is scanned. However, when trying to scan and deploy things from the Lansweeper users end we have been struggling to figure out. Has anyone had this problem or seen something similar?
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2016 10:27 PM
Some additional information for anyone having issues with this: RPC errors do usually point to firewall issues. Lansweeper pulls most Windows computer data from WMI (Windows Management Instrumentation), a management framework built into Windows operating systems. WMI inherently - this is true for all applications querying WMI - sends its data over random ports in the 1025-5000 or 49152-65535 range. For agentless scanning and deployments, you should allow *all* WMI traffic. Configuration instructions for Windows Firewall can be found here, but third-party firewalls may need to be reconfigured as well.
On computers running Windows Vista or higher, you could set up a fixed WMI port, as explained in this Microsoft article. To get a successful scan, you could scan locally with our LsPush scanning agent as well, though this will not resolve the deployment errors. (Deployments are always triggered remotely.)
On computers running Windows Vista or higher, you could set up a fixed WMI port, as explained in this Microsoft article. To get a successful scan, you could scan locally with our LsPush scanning agent as well, though this will not resolve the deployment errors. (Deployments are always triggered remotely.)
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2016 10:41 PM
Thanks for the help everyone someone on our team resolved the issue. There was a conflicting rule in the group policy for computers that enabled a weird function on the windows firewall while we had Symantec Endpoint Protection turned on or not which was what was giving us a hard time. Changing the group policy ended up doing the trick for us.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2016 10:27 PM
Some additional information for anyone having issues with this: RPC errors do usually point to firewall issues. Lansweeper pulls most Windows computer data from WMI (Windows Management Instrumentation), a management framework built into Windows operating systems. WMI inherently - this is true for all applications querying WMI - sends its data over random ports in the 1025-5000 or 49152-65535 range. For agentless scanning and deployments, you should allow *all* WMI traffic. Configuration instructions for Windows Firewall can be found here, but third-party firewalls may need to be reconfigured as well.
On computers running Windows Vista or higher, you could set up a fixed WMI port, as explained in this Microsoft article. To get a successful scan, you could scan locally with our LsPush scanning agent as well, though this will not resolve the deployment errors. (Deployments are always triggered remotely.)
On computers running Windows Vista or higher, you could set up a fixed WMI port, as explained in this Microsoft article. To get a successful scan, you could scan locally with our LsPush scanning agent as well, though this will not resolve the deployment errors. (Deployments are always triggered remotely.)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-30-2015 11:18 PM
Are you able to scan the machines with this credential?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-30-2015 09:58 PM
It appears that your scanning credentials are incorrect.
Creating and mapping scanning credentials
It looks like you are using a local admin account on your lansweeper server to scan domain computers.
-Kris
Creating and mapping scanning credentials
It looks like you are using a local admin account on your lansweeper server to scan domain computers.
-Kris
