Hello there!
An IP range scan will contact the asset on its IP address before handing over the asset to the Windows scanning routine, the rescan button will contact the asset by its NetBIOS name, so perhaps there is a difference there.
If this issue persists in the latest version of Lansweeper, I would suggest reaching out to the support team: support@lansweeper.com
The following information would be nice to have:
- Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on your Lansweeper scan server.
- Screenshots of one problem client machine's Lansweeper webpage - after a manual rescan. Show us the following tabs:
- Summary
- Scan Time
- Scan Issues (if it exists)
- Screenshots of one problem client machine's Lansweeper webpage - after a scheduled IP scan. Show us the following tabs:
- Summary
- Scan Time
- Scan Issues (if it exists)
- Screenshot of a connection test performed to the same problem client machine with testconnection.exe, which can be found in Program Files (x86)\Lansweeper\Actions on your Lansweeper server. Perform the test from your Lansweeper server to the client machine (on NetBIOS name), submit the same credential used by Lansweeper to scan the client, and show us the entire test window.
- Screenshot of a connection test performed to the same problem client machine with testconnection.exe, which can be found in Program Files (x86)\Lansweeper\Actions on your Lansweeper server. Perform the test from your Lansweeper server to the client machine (on IP address), submit the same credential used by Lansweeper to scan the client, and show us the entire test window.
We recommend compressing these files into an archive (zip/rar/7z) prior to sending them to drastically reduce their size.
