This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
→ 🚀What's New? Join Us for the Fall Product Launch! Register Now !
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Lansweeper Community
- Forums
- General Discussions
- Re: rescan asset not using mapped credentials
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
‎09-02-2015 11:44 AM
We scan several domains with mapped credentials and the scheduled IP Address Range Scanning option.
When we want to re-scan an asset from the asset page or report page the scan is performed with the Global account instead of the mapped credentials.
Is this a bug or did i make a mistake in the config ?
If you need more info please let me know.
Greetings Barry
When we want to re-scan an asset from the asset page or report page the scan is performed with the Global account instead of the mapped credentials.
Is this a bug or did i make a mistake in the config ?
If you need more info please let me know.
Greetings Barry
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
‎09-03-2015 04:24 PM
Thank you, we received your mail. The mapping of credentials seems to be ok. The "Access denied" message can sometimes be caused as well through firewall issues. In order to perform WMI scans, port 135/TCP and the dynamic port range (49152-65535 on Windows Vista and more recent OS versions) need to be open between your scanning server and scanned computers. Possibly this range is blocked and therefore Lansweeper can't connect.
If you can't open that range, you could either configure a fixed WMI port on all affected target computers or scan them with LsPush. This is a small executable which scans the computer and sends the result back to your Lansweeper server using direct server connection (port 9524/TCP by default), file share or mail. You can find details here. It is possible to configure a scheduled task for running LsPush and deploy it via group policy.
Other possible causes of an "Access denied" message are explained in this KB article.
If you can't open that range, you could either configure a fixed WMI port on all affected target computers or scan them with LsPush. This is a small executable which scans the computer and sends the result back to your Lansweeper server using direct server connection (port 9524/TCP by default), file share or mail. You can find details here. It is possible to configure a scheduled task for running LsPush and deploy it via group policy.
Other possible causes of an "Access denied" message are explained in this KB article.
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-03-2015 04:24 PM
Thank you, we received your mail. The mapping of credentials seems to be ok. The "Access denied" message can sometimes be caused as well through firewall issues. In order to perform WMI scans, port 135/TCP and the dynamic port range (49152-65535 on Windows Vista and more recent OS versions) need to be open between your scanning server and scanned computers. Possibly this range is blocked and therefore Lansweeper can't connect.
If you can't open that range, you could either configure a fixed WMI port on all affected target computers or scan them with LsPush. This is a small executable which scans the computer and sends the result back to your Lansweeper server using direct server connection (port 9524/TCP by default), file share or mail. You can find details here. It is possible to configure a scheduled task for running LsPush and deploy it via group policy.
Other possible causes of an "Access denied" message are explained in this KB article.
If you can't open that range, you could either configure a fixed WMI port on all affected target computers or scan them with LsPush. This is a small executable which scans the computer and sends the result back to your Lansweeper server using direct server connection (port 9524/TCP by default), file share or mail. You can find details here. It is possible to configure a scheduled task for running LsPush and deploy it via group policy.
Other possible causes of an "Access denied" message are explained in this KB article.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-02-2015 02:53 PM
It should use the mapped credentials, please send us screenshots of your configuration/asset page. Support@lansweeper.com
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-03-2015 09:58 AM
Michael.V wrote:
It should use the mapped credentials, please send us screenshots of your configuration/asset page. Support@lansweeper.com
you got mail...
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
- HP iLo and scanning issue in General Discussions
- Credentials from "my credentials" not mapped to all scanning servers in General Discussions
- Mass Mapping of Credentials in General Discussions
- LS ignores windows credentials fallback in IP mapping credentials in General Discussions
- Lansweeper Health Checklist in General Discussions
