
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-26-2019 04:33 PM
We upgraded the server in November to the latest version (7.2.106.35). Once we did that, we scanned all of our subnets and noticed that we had less computers discovered than we had previously. Due to that our report numbers changed and we cannot connect to some machines that are on our network, despite manually adding their IP range to the queue.
We have verified that the ranges are correct and that the account used to scan the machines is active and that the password is correct.
Since we depend on Lansweeper for report numbers, I am trying to troubleshoot what the issues are. For example, if you look at a report that we have for Windows 7 machines, you will see that the machines say they are non-active and the lastseen is the date right before we upgraded the server. However, if you use remote control through Lansweeper, you can connect to these machines.
Adam
We have verified that the ranges are correct and that the account used to scan the machines is active and that the password is correct.
Since we depend on Lansweeper for report numbers, I am trying to troubleshoot what the issues are. For example, if you look at a report that we have for Windows 7 machines, you will see that the machines say they are non-active and the lastseen is the date right before we upgraded the server. However, if you use remote control through Lansweeper, you can connect to these machines.
Adam
Labels:
- Labels:
-
General Discussion
1 REPLY 1

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-13-2020 05:12 PM
Probably the same problem as https://www.lansweeper.com/forum/yaf_postst19178_assets-seen-as--non-active--after-LS-server-upgrade.aspx#post61862
