Cannot Scan Computers In Multiple Domains

[Mike_Large]

For legal reason, we have three seperate domains running on the same physical network at one location. They are all managed by our company but they are each in their own seperate domains; not part of a forest.

I have installed Lansweeper 3.5 on our primary domain domain1.net, member server aneas. I have activated Lansweeper Active Scanning for the other two domains (domain2.com & domain3.local) and set alternate domain credentials for all domains but no computers for the domain2.com or domain3.net domains are being scanned (see errors below).

From the error, it appears that domain1.net (domain controller) is being called to access the domain2.com & domain3.local domains but it cannot find them. It shouldn't find them because they are in a different domains and not part of the domain1.net AD or DNS. I would assume that Lansweeper would use the alternate domain credentials to gain access to the workstations. All machines are on the same physical network and submask.

I have run connectiontest against computers (using the workstations IP address) on all domains and the connectivity is working fine.

I ran lsclient on a workstation on the domain2.com domain and Lansweeper started the scan but ended up giving me a WMI error: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) ANE100 (192.168.2.217) \root\default. I know the workstation is configured correctly for scanning since it can be correctly scanned from our Lansweeper 3.5 Beta we had installed on domain2 earlier.

I was under the impression that Lansweeper 3.5 Premium now has the ability to access other domains.
Also, I know one of your new 3.5 features was that the lsclient is no longer needed but if we must use it that would not be the end of the world; we would just set it up in the domain2.com & domain3.net login scripts.

Can you provide me some guidance on what may be happening or what I may have configured incorrectly. We need to manage all of our computers from this single installation of Lansweeper if at all possible.


Our administive domain and where Lansweeper is installed: domain1.net
Other domains are: domain2.com & domain3.net

Error Log:
3/13/2009 10:07:57 AM: domain2.com anedc.domain1.net The specified domain does not exist or cannot be contacted.
at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context)
at LansweeperService.mdlActivescanning.ActiveScan()

3/13/2009 10:07:57 AM: domain3.local anedc.domain1.net The specified domain does not exist or cannot be contacted.
at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context)
at LansweeperService.mdlActivescanning.ActiveScan()

[Hemoco]

We are working on a service pack to make scanning of non-trusted domains available.

[Mike_Large]

I understand that I would not be able to access the computers on the other domains by hostname because they are in a different AD & DNS but I can access them by IP address and with the domain credentials in 3.5, I assumes we would be able to access & scan these computers.

I also understand that you may not be able to perform active scan in our situation because they are not in the same domain but I do not mind using lsclient at login if that will resolve the issue.

Thanks for all your help. The new release really added some nice features I am looking forward to using.

[Mike_Large]

I tried both the IP address (192.168.2.217) and the hostname (ANE100). The IP address worked fine but the hostname does not work.

I assume it is because I am running the connection tester on domain1 and ANE100 is on domain2 so it has no idea what ANE100 means.

[Hemoco]

Mike Large wrote:

I ran lsclient on a workstation on the domain2.com domain and Lansweeper started the scan but ended up giving me a WMI error: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) ANE100 (192.168.2.217) \root\default. I know the workstation is configured correctly for scanning since it can be correctly scanned from our Lansweeper 3.5 Beta we had installed on domain2 earlier.

Next to the other issues to which I will be come to later:

ANE100 (192.168.2.217) means that this computer is scanned based on IP address. (192.168.2.217) instead of hostname.
Did you try the connection tester using a hostname?