User Search not working

[eastersealsnh]

Good morning all,

We recently finished our test run with Lansweeper and moved it to production servers. Excellent software, it's been great! Thank you!

We're moving off of Novell and one of the features of Lansweeper that would be huge for our help desk would be username lookups that return the IP address of the machine they're logged into.

We've discovered that Computer Search and Software Search still work with full functionality but User Search has stopped working correctly. It only has results from users who login who have DOMAIN1 accounts. Unfortunately a very large majority of our user accounts are on DOMAIN2.

I did find the post: http://www.lansweeper.com/forum/yaf_postst545_User-Search-not-working.aspx

and would like to say that yes we have active directory and yes the service running under a domain account that has permissions to read active directory users details (a domain admin on DOMAIN1 w/ delegated control on DOMAIN2 to read all user details w/ an active trust between domains [not that you should need to delegate control to a domain admin... but it's one of the things we've been trying). We've also tried running it as a Domain Admin on DOMAIN2, no effect w/ delegated control the other way.


Here is the setup that worked for us as well as the setup we moved to.

-----------------------
Test setup: (works great!)
(single workstation)

WORKSTATION1(joined to: DOMAIN2)
Lansweeper service running under DOMAIN2\Domain Admin acct
Win XP SP2
IIS v5.1
MSXML v6 SP2
SQL Server Express 2005
.net framwork 3.5
Lansweeper 3.5
-----------------------

migrated to:
(two servers, both joined to DOMAIN1. [we have two domains, half our workstations are joined to DOMAIN2] There is an active trust between domains.)
-----------------------

SERVER1(joined to: DOMAIN1) (IIS and and Lansweeper service installed)
Lansweeper service running under DOMAIN1\Domain Admin acct. (Also tried running it under DOMAIN2\Domain Admin)
Win Server 2003 R2 SP2
IIS v6.0
MSXML 6 SP2
.net framework 2.0
Lansweeper 3.5

SERVER2(joined to: DOMAIN1) (DB installed here)
Win Server 2003 R2 SP2
SQL Server 2005
.net framework 2.0 SP1
MSXML 6 SP2
Lansweeper 3.5 (ran install to setup DB)
-----------------------

ERROR LOG:
4/28/2009 1:25:57 PM: Database connection successful, starting up service

4/28/2009 1:27:45 PM: DOMAIN2\L-NYC-$ Active directory computer lookup Name translation: Could not find the name or insufficient right to see name. (Exception from HRESULT: 0x80072116)

4/28/2009 1:28:02 PM: DOMAIN2\W-ROC-DTC-23$ Active directory computer lookup Name translation: Could not find the name or insufficient right to see name. (Exception from HRESULT: 0x80072116)

(all computers joined to DOMAIN2 log this error on running lsclient.exe)
-----------------------
(Errors don't seem to be related to: MS ARTICLE ON ERROR: http://support.microsoft.com/kb/317982 the software versions don't apply to us)

We also tried running the Lansweeper service under a domain admin account under DOMAIN2 (while the server was still joined to DOMAIN1) to see if that would resolve the error log errors "Name translation: Could not find the name or insufficient right to see name." thinking that maybe the domain admin on DOMAIN1 didn't have rights to see user details for accounts on DOMAIN2 as well as resolve the User Search functionality. No effect. It seems that the domain that the server is joined to also effects the ability to read active directory users details? We're not sure.

Connection tester shows a good connection w/ the domain controllers and clients and servers.

This is using LSClient.exe (not active scanning).


Does anyone have any suggestions? Or was http://www.lansweeper.com/forum/yaf_postst1296_Lansweeper-not-working-after-32-to-35-update.aspx ever resolved? that seems to be very similar,

Thank you very much in advance!

-Chris (sorry for the wall of text)

[eastersealsnh]

Thank you! The beta is working very well for us 😄

Best regards,

-Chris

[Hemoco]

Try the 3.5.1 beta, specify alternate credentials for the other domain, that should do the trick.