Computers not scanning in 3.2

[taeratrin]

I have several computers showing up as Never Scanned. When I run the connection tester on them, everything returns OK. No errors reported when I view the details on the site.

Any ideas?

[Pollak]

Where can I find the srvinstw tool?


Thanks,
Niles

[Hemoco]

Pollak wrote:
Where can I find the srvinstw tool?


Thanks,
Niles

http://www.lansweeper.com/debug/srvinstw.zip

[Pollak]

Where can I find the srvinstw tool?


Thanks,
Niles

[Hemoco]

TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

This is caused by vista and XP.

Windows servers don't have this limit (that's why there is a difference in licensing and price)

[Hemoco]

Are you running the lansweeper service on a windows XP machine or on a server?

[gsvarney]

Lansweeper wrote:
Are you running the lansweeper service on a windows XP machine or on a server?

It's running on Vista Business 32bit.

[gsvarney]

I initially believed that this issue was resolved for me by recreating the service. However, after clearing all of the computers that were not scanned, I still have 106 out of 545 still showing as not scanned. On some there is the RPC error, but on many there are no errors. I just checked the services for one of them and found everything running. These same machines mostly all scanned fine previously using lsclient. I'm going to run this on a few and see if that makes any difference.

[gsvarney]

gsvarney wrote:
I initially believed that this issue was resolved for me by recreating the service. However, after clearing all of the computers that were not scanned, I still have 106 out of 545 still showing as not scanned. On some there is the RPC error, but on many there are no errors. I just checked the services for one of them and found everything running. These same machines mostly all scanned fine previously using lsclient. I'm going to run this on a few and see if that makes any difference.

OK, lsclient is no different. The connection tester on this machine shows:

Ping test OK
-----------------------------------------------
Remote registry test OK
-----------------------------------------------
Remote WMI access test OK
-----------------------------------------------
Remote \\cjohnson-a\c$ access test OK

I see a bunch of DCOM errors in the event log on the server, but those all seem to be due to RPC failures. This example does not show that.

I also saw this in the log:

TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Could the limit be getting reached by the scanning service?? I restarted the service again and *some* of the unscanned scanned, like happened after I recreated the service. Maybe that didn't help but restarting the service does. Still a number not scanning that have no RPC error. I don't see any TCP/IP limit being reached.
I now have 82 out of 546 unscanned. Perhaps more service restarts will yield more scans....

[Pollak]

I now have 1546 "Not scanned" computers. No description (e.g. model, OS, memory, software, etc...) of any kind is given in the web interface. None of the listed "Not scanned" computers have the "Error" tab indicating that there was an error. Server, Workstation and Computer Browser services are running on all workstations and servers.



Please advise,
Niles