cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
d_i_saunders
Engaged Sweeper III
Hi,

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

14 REPLIES 14
Hemoco
Lansweeper Alumni
Most likely the problem is caused by the dns records not yet updated (or the location not accessible due to firewall settings)
d_i_saunders
Engaged Sweeper III
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.
Hemoco
Lansweeper Alumni
Is there anything not working at the moment (no scans done)?

Except for the vpn users.
d_i_saunders
Engaged Sweeper III
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..

Hemoco
Lansweeper Alumni
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
d_i_saunders
Engaged Sweeper III
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?

d_i_saunders
Engaged Sweeper III
Belive its all..

The VPN comment was mainly regarding will be the be detected..

Regards
Hemoco
Lansweeper Alumni
Do you get this error only when the vpn users log on or all the time using active scanning?
d_i_saunders
Engaged Sweeper III
3.5.2.4

Should be the latest