
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2009 06:57 PM
Little help required...
We have LSclient running on most of our PC's and its been working fine for a number of years..
We havejust upgarded to verison 3.5 as it can now be restricted to specific OU's..
We have pointed the service at the the OUs we want to scan..
My quesiton regarding this is:
1) Will it matter if a PC reports back via LSClient, and then picked up in the Active Scan? Will it just be skipped?
2) Can the OU filter be restricted to pc that match a specific filter? (eg starts UK**** )
Secondly is the Lansweeperservice.exe.config file still used?
If so is the line below not casuing it to go and scan anything it can see?
<add key="Activescanning" value="1" />
regards
dave
- Labels:
-
Archive

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-14-2009 03:31 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-14-2009 05:11 PM
Lansweeper wrote:
Most likely the problem is caused by the dns records not yet updated (or the location not accessible due to firewall settings)
That would fit.. out DNS takes days to update.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-13-2009 09:33 PM
Except for the vpn users.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-13-2009 10:20 PM
Lansweeper wrote:
Is there anything not working at the moment (no scans done)?
Except for the vpn users.
seems to be just remote people...
Or people at very remote locations..

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-12-2009 09:04 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-12-2009 09:22 PM
Lansweeper wrote:
The "System.DirectoryServices.Protocols.LdapDirectoryIdentifier The operation was aborted because the client side timeout limit was exceeded" error is caused by timeouts to your domain controllers
Is there anything I can do?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-12-2009 02:57 PM
The VPN comment was mainly regarding will be the be detected..
Regards

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-12-2009 02:30 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-12-2009 11:00 AM
Should be the latest
