
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-10-2020 01:17 PM
I had difficult times to get one of my secondary LS server updated to the last LS release. In the end the issue was about, for some reason th SQL server was wrongly defined when all my other secondary LS servers were OK.
Now I can scan my IP range as previously but I get most (not all) my assets with status inactive when actually the scan was done. They get the correct 'last seen' and 'last scan' date.
Any idea? Thanks.
Now I can scan my IP range as previously but I get most (not all) my assets with status inactive when actually the scan was done. They get the correct 'last seen' and 'last scan' date.
Any idea? Thanks.
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:07 PM
I think we've got the same problem after upgrade to 7.2.106.48
A lot of non-active PCs, although they are active (ping is ok)
We don't work with LSAgent, only AD scanning.
I discovered in the tab Comments, that the device seems to change the name from Netbios Domain name to DNS Domain name. At the next scanning back to Netbios and so on. We didn't have this before.
A lot of non-active PCs, although they are active (ping is ok)
We don't work with LSAgent, only AD scanning.
I discovered in the tab Comments, that the device seems to change the name from Netbios Domain name to DNS Domain name. At the next scanning back to Netbios and so on. We didn't have this before.
