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?

[Hemoco]

Pollak wrote:
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

Pollak,

Di you try recreating the service as others suggested?

[DGoodwin]

I was baseing my reply on the first post as an alternative place to look to fix errors. Sorry if there is any confusion.

[DGoodwin]

I had the same problem with only about 3 computers not showing up as scanned. The fix I found was related to the operating system on the client. The services for "server" "workstation" "Computer Browser" and their dependencies were not working. Basically they (users) could get out on to the network, but we could not get back to them. LS would show them as "Reverse lookup failed" or "The network path was not found" even though we could ping them and they could see out with no issues. The fix was to re-extract the files "c:\windows\system32\SRVSVC.dll" and "c:\windows\system32\drivers\srv.sys" from the xpsp2 cd and reboot. Then they worked fine after that.
Hope this helps someone.

LS 3.2
450 Clients Workstations in 11 states

[Hemoco]

DGoodwin wrote:
I had the same problem with only about 3 computers not showing up as scanned. The fix I found was related to the operating system on the client. The services for "server" "workstation" "Computer Browser" and their dependencies were not working. Basically they (users) could get out on to the network, but we could not get back to them. LS would show them as "Reverse lookup failed" or "The network path was not found" even though we could ping them and they could see out with no issues. The fix was to re-extract the files "c:\windows\system32\SRVSVC.dll" and "c:\windows\system32\drivers\srv.sys" from the xpsp2 cd and reboot. Then they worked fine after that.
Hope this helps someone.

LS 3.2
450 Clients Workstations in 11 states

So this was basicly an client problem and not a scanning "bug"?

[Hemoco]

I'm glad it's solved, but I don't see how recreating the service could have done it.

[Hemoco]

Your original service was problably called "lansweeper30.exe" and you copied lansweeper32.exe over lansweeper30.exe thus renaming it, correct?

[gsvarney]

Lansweeper wrote:
Your original service was problably called "lansweeper30.exe" and you copied lansweeper32.exe over lansweeper30.exe thus renaming it, correct?

Correct, this is what I originally did, as with the config file.

[Hemoco]

Did you also ran the sql scripts?

[sbartley]

I only stoped the service and overwite the lansweep30 file

[Hemoco]

Which steps did you do for the upgrade to 3.2?