Lansweeper not working after 3.2 to 3.5 update

[Dov]

I'm running Lansweeper on a 2003 server in vmware; followed the update instructions and received no errors but only some clients would check in, even with a manual launch of the client from various workstations and servers (lsclient.exe vm-sweeper), the client shows it's connected but still no luck. Doing NETSTAT shows the client trying to connect to port 9254 on the server, but the state shows TIME_WAIT; on the server it shows no connection to/from the client.
Since it's running in VMware, I reverted to the snapshot before the update to 3.5, and once again followed the instructions for the update; still facing the same issues, most machines are not showing as checking in to the server, something which did not happen at all under version 3.2
Any suggestions?

[Hemoco]

Could you check if table tbladcomputers and tbladusers are updated.

[Dov]

Actually, none. I removed one of the computers which showed an error in the log from the database, and launched the lsclient from the PC; it still shows the error in the log, but the computer scanned just fine.

[Hemoco]

which info is missing from your scan?

[Dov]

Negative, all our users are domain users. The Lansweeper service account is not only a domain admin to the local domain (which scans fine), it's also a domain admin to 4 of our other domains. Also, name resolution is not a problem; I can ping from the machine the Lansweeper service is running on all the machine names it has problems scanning.

[Hemoco]

When you get the Name translation: Could not find the name or insufficient right to see name. (Exception from HRESULT: 0x80072116) error, which info is missing from your scan?

Is it possible that you run lsclient from a locally logged on user (instead of a domain user)

[Dov]

Has anyone else had this problem?
Also, off-topic, I'm registered as a freeware user; how do I get registered as a premium user, since we've purchased the program ..?

[Dov]

I went on one of the clients and manually launched lsclient.exe, got the same error.
The three machines below are from 3 different domains, all of which the lansweeper service account has full domain admin rights.
It seems the only machines I can scan are from the local domain.

3/13/2009 3:04:04 PM: NCHWS10 Name translation: Could not find the name or insufficient right to see name. (Exception from HRESULT: 0x80072116)

3/13/2009 3:13:20 PM: ALPCOXP4 Name translation: Could not find the name or insufficient right to see name. (Exception from HRESULT: 0x80072116)

3/13/2009 3:57:13 PM: MDTS1 Name translation: Could not find the name or insufficient right to see name. (Exception from HRESULT: 0x80072116)

[Dov]

Ok, screengrab works, thanks. The account running the service is a domain admin, and is also a domain admin for the other domain.
The command I have set in the Custom actions is: \\vm-sweeper\ls-tools\lstrigger\lstrigger.exe vm-sweeper {computer} {domain}

[Hemoco]

Dov wrote:
Ok, screengrab works, thanks. The account running the service is a domain admin, and is also a domain admin for the other domain.
The command I have set in the Custom actions is: \\vm-sweeper\ls-tools\lstrigger\lstrigger.exe vm-sweeper {computer} {domain}

When the computer is scanned without lstrigger, do you still get this error?

[Hemoco]

The screengrabber should be placed accessible from the workstation where you are logged into the webconsole. (something like c:\windows\system32 always works, same for lstrigger)

Could you show me the exact command of lstrigger that is giving problems.
Does your account running the service has "read" permissions on the target active directory?