Lansweeper Service attempting to communicate to the internet

[TribuneLanSweep]

We're hearing from our security people, Lansweeper, with Active Scanning enabled, is trying to make connections outside of our network thru port 135. Needless to say, the security folks are watching this very carefully. We know 135 is used to make the initial connection by DCOM to the remote machine being scanned. We can't understand why it would also attempt access to the internet. We're running 3.5.1 upgraded from 3.5 which was upgraded from 3.2.

Everything else is behaving nicely (Excpet, we can't talk to NT machines)

Thanks in advance

[TribuneLanSweep]

Thanks for the help! We have a place to start

[TribuneLanSweep]

Thanks for the quick reply. The issue isn't that lansweeper's having problems finding clients thru ACTIVE SCANNING. Active scanning is enabled and it appears to be functioning. Machines are being discovered and the DB is growing. The issue is there seems to be traffic from lansweeper trying to access the internet. At least this is what I'm hearing from network security. There are some AD domain namespaces within our enterprise with the .COM in the namespace. Could that factor in to this?

[Hemoco]

TribuneLanSweeper wrote:
There are some AD domain namespaces within our enterprise with the .COM in the namespace. Could that factor in to this?

I understand your issue.

If the dns is somehow misconfigured it's possible.
We had one client who had this problem with one subdomain ending on .net. (all subdomain ended on "company.net" but the settings for this one subdomain solved the problem)
As a result several other problems they didn't know they had were solved meanwhile.

[Hemoco]

Is this with active scanning or with lsclient?
Active scanning gets the computer's FQDN name from active directory and tries to scan this first.
If this fails it tries the netbios name and the IP address (queried from dns) (both these 3 on port 135 first)

It could be that:

A fqdn is misconfigured
DNS lookups is misconfigured.

To which IP is Lansweeper connecting?
Maybe you can do a reverse lookup to find out the domain name.

You could take a look at your error table to see which computers are failing.

PS.
only win2000 and above is supported.