Some Computers are not Actively scanned

[tony_joseph]

I have enabled Active scanning.Lansweeper configuration utility shows all the computers in domain but some are shown in red(details missing).when I checked the webconsole it shows

RPC server unavilable(understood it is due to firewall issues.Made the windows firewall off on the client)
WMI(enabled WMI)
edited local computer policy to enable Remote Administration Exception

These steps have worked for some but not for all.

Regards,
Tony

[Hemoco]

For this you need to restart the service.

[wmjstu]

How do I clear the que to get the stuck computers out so that I can scan the fixed ones? Can I do it directly from the SQL table? (and which one, if so)

[Fred_Tran]

3.5.2 Fresh install. I am experiencing the same problem. Several pcs in the same OU are not getting scanned. Lstrigger will only work if they were scanned previously. Manual lsclient will work though and they will show up. Is there a time limit?

Thanks

[Hemoco]

Fred_Tran wrote:
3.5.2 Fresh install. I am experiencing the same problem. Several pcs in the same OU are not getting scanned. Lstrigger will only work if they were scanned previously. Manual lsclient will work though and they will show up. Is there a time limit?
Thanks

Workstation contact the dc's every half hour
Member servers normally once a day.

So it might be normal that you miss some computers when the service first starts.

[wmjstu]

Have you gotten a chance to remote in and take another look at this? My MIS is agitating to drop LANSweeper entirely, and I'd rather not.

[Hemoco]

Please contact us by e-mail lansweeper@hemoco.com

We'll help you find the cause of this issue.

[wmjstu]

Most configuration items on most machines have never been successfully scanned - I have a long row of red Xs down the right hand side, with a few black clocks.

Have tried restarting the service, setting "Scan Every X Days" to 0, deleting computers so they can be picked up from scratch, running lsclient from the workstation; so far no luck.

gpudate /force doesn't appear to be any help with the RPC policy. Connection Tester can reach most of the machines with RPC errors.

I think the problem with applying the GPO may be Network Determination:

http://technet.microsoft.com/en-ca/library/bb878049.aspx

Our DHCP does not hand out a Connection Specific Suffix. I have an RFC in to our MIS to let me add one, but so far it's not in there. Do you think this could be related?

This is a great tool, but I'm only getting it to successfully scan a small portion of our computers.

[wmjstu]

DNS appears to be correct.

[wmjstu]

I'm still having issues with it taking forever to scan through the systems, even those with no apparent RPC problems