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]

mbonal had a different problem btw.

[Dov]

I just included the computer account as a domain admin in the remote domain and will try to scan again.
To answer your question, yes, it's with the lsclient (or a triggered scan); I will try the active directory scanning.

[mbonal]

Receiving this error..

The specified domain does not exist or cannot be contacted.
at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context)
at LansweeperService.mdlActivescanning.ActiveScan()

The specified domain either does not exist or could not be contacted.

neither NT nor active directory work now since the upgrade!

[Hemoco]

Another question, is this with lsclient or with active scanning.

[Hemoco]

After taking a look at the code I can see that the problem is caused by the computer translation: domain\computer$

Could you take a look at the computer accounts in this domain. (permissions)

[Dov]

The account we're using is a domain admin for the local domain, as well as domain admin for the remote domains; any suggestions where to start looking? The account the lansweeper service is using can access admin$, ipc$ and c$ with no problems ..

[Hemoco]

Dov wrote:
The account we're using is a domain admin for the local domain, as well as domain admin for the remote domains; any suggestions where to start looking? The account the lansweeper service is using can access admin$, ipc$ and c$ with no problems ..

Accessing the computers is not really the problem, it's the service account that tries to lookup computers/users in active directory.

This part of the code uses the nametranslate object to translate domain\username into a path like ldap://cn=username,cn=domain,cn=local so it can be lookup up in active directory.

or it translates the computer accountname domain\computer$ into an adsi path

This translation part seems to fail.

Here is some technical explanation : http://www.rlmueller.net/NameTranslateFAQ.htm

[Hemoco]

This means that the active directory lookup for these accounts failed for the user running the lansweeper service.

[Dov]

Both those tables show users and computers only from the local domain (and one child domain); the tblComputers shows all computers.