Updated network scans

[mtaggart]

How often does LAN Sweeper by default scan a network? I ask because in looking at the list of computers it has found, there are quite a bit that haven't been rescanned since the initial scan which was 10+ days ago.

I thought it would scan all computer a little more often than that. Is there a way to either reduce the amount of time between scans or possible schedule when the network scan will happen and how often?

Mike

[mtaggart]

we're not worrying about that domain - just madixinc.com

Also, we do not have any DNS issues.

[Hemoco]

mtaggart wrote:
we're not worrying about that domain - just madixinc.com

Also, we do not have any DNS issues.

Please mail us at lansweeper@hemoco.com for an updated service.

[Hemoco]

zzlabzz.com The server is not operational
Is most likely a problem with active directory, make sure that the dns name can be resolved.

[mtaggart]

it's been uploaded.

[mtaggart]

It's both computers and servers not being updated/rescanned since we installed the product back on 2/23/2010 ...

[Hemoco]

mtaggart wrote:
It's both computers and servers not being updated/rescanned since we installed the product back on 2/23/2010 ...

Could you upload (or mail to lansweeper@hemoco.com) your errorlog.txt file please.

[Hemoco]

mtaggart wrote:
How often does LAN Sweeper by default scan a network? I ask because in looking at the list of computers it has found, there are quite a bit that haven't been rescanned since the initial scan which was 10+ days ago.

I thought it would scan all computer a little more often than that. Is there a way to either reduce the amount of time between scans or possible schedule when the network scan will happen and how often?

I assume you mean active scanning:

How active scanning works:
lansweeper queries all domaincontrollers every 15 minutes to search for recently logged on computers.
The computers are then scanned if they weren't scanned in the last 8 hours.

Workstations connect to dc's almost every hour, servers can take some more time.

Are the computers with the problem servers or workstations?