LS and DNS Question

[R3dSk1ns]

I have a question about when LS scans. Under the premium version with Active Scanning it will get computernames from Active Directory. It then will do a DNS query to find that computer (at least that is what appears to happen). Once it finds a computer and scans it stores the last known IP address. My question comes in to when LS goes to scan again...Does it use the last known IP address or does it query DNS by hostname or FQDN each time it scans? Does it do WINS look ups? I understand it uses the Host it is running on to do the queries. Is there any host caching that should be cleared regularly (like ipconfig /flushdns and/or nbtstat -R)?

I have seen an issue within our network about it overlapping computers and IP addresses. For example:

ComputerA gets scanned and has the last known IP of 192.168.1.1
ComputerB gets scanned and has the last known IP of 192.168.1.30

All looks good at this point then a wrench...

ComputerA changes IP addresses to 192.168.2.5 - went to another location.
ComputerB still looks good.
ComputerC gets scanned and has IP address 192.168.1.1 but has the description and other information that ComputerA had.
ComputerA name is no longer in the LS DB.

So with this when the IP address goes to another computer, it may not neccessary return or update the database correctly. Should I see this? I guess my ultimate question is when LS updates scans how does it check to see what is in the DB and just update that information?

Now I have also found some issues with scavenging our internal DNS. I am cleaning that up now but I was wondering if I am missing to understand some logic in the LS DB.

Any help would be great.

[R3dSk1ns]

Thanks. We are running the beta now. I know one of the fixes was for the DNS issue I described, so does this go back and resolve the issue we already had so it shows the right computer or does it have to scan the computers again before it updates the output correctly?

[Hemoco]

R3dSk1ns wrote:
Thanks. We are running the beta now. I know one of the fixes was for the DNS issue I described, so does this go back and resolve the issue we already had so it shows the right computer or does it have to scan the computers again before it updates the output correctly?

You need to wait until the affected computer gets rescanned, easiest would be to just delete it from the database.
This update will warn you about the wrong DNS/IP setting ans will stop scanning so you can fix the dns problem.

[Hemoco]

It's right here : http://www.lansweeper.com/forum/yaf_postst1939_Lansweeper-352-beta.aspx

[R3dSk1ns]

Can I download the Beta?

[Hemoco]

Basically it's just replacing the service executable to fix your problem.
So far there were no problems reported with the beta the last month.

[R3dSk1ns]

Thanks for the quick response. Since I am still evaluating LS - should I try the 3.5.2 Beta?

[Hemoco]

R3dSk1ns wrote:
My question comes in to when LS goes to scan again...Does it use the last known IP address or does it query DNS by hostname or FQDN each time it scans?

Lansweeper does a dns lookup each time.

The problem with the incorrect data is fixed in the last 3.5.2 (beta)

[R3dSk1ns]

We use both DNS and WINS.

[Anonymous]

Do you use WINS? Usually that happens if WINS keeps the records.