We are getting an error message when scanning many PCs after a change we made in in our configuration:
The interface is unknown. (Exception from HRESULT: 0x800706B5) and then the PC name is listed. This error is listed three times, followed by a DCOM error that says "Cannot connect to DCOM port 135: Firewalled?" (our computers are NOT firewalled - we have a GPO that disables the firewall and I have checked some of the workstations in question and the firewall is indeed off.)
Here is some history and our setup:
We have two domains with a trust. We are in the process of migrating all of our computers from one domain to another. We had Lansweeper set to scan on both domains and it was working fine.
The Lansweeper service is running under the domain admin account of the old domain. We plan to change that in the future to a service account on the new domain, but first we need the scanning to work again.
The scanners for both domains are running under a service account and that has always worked. The service account has admin privileges on the local computer.
We renamed the server that Lansweeper was running on (that was our configuration change). We updated the server name in the console and in the Lansweeper config file and the web,config file.
All computers were scanning fine and reporting results until the server name was changed. Once we changed the server name, suddenly ALL computers that were joined to the new domain show this error when they are first scanned on the new domain. Rescanning does no good. In the past they did scan properly after being joined.
Any ideas of something to look for? Thank you for any help!
