Old IP address still used after change of DNS entry

[Mogens_Olsen]

I just had this scenario:

- ran lsclient on a pc with ip .171
- at that time the DNS entry for the pc showed ip .132
- the pc was addes to the database, but failed with "wmi access denied" stating ip .132
- I then corrected the DNS entry, checked on the ls server that nslookup showed correct ip
- ran lsclient again, but same problem
- restarted the ls service, ran lsclient, but same problem
- deleted the pc from the ls database
- ran lsclient, and now all okay

It could seem, that ls tries to contact the pc using the first seen ip address? Why does ls scan try to contact the pc on a false ip?

I am using version 3.5.2.3 on a fresh database, but have been using 3.5.1 for some time. In that period I had several pc's showing the correct logged on user and ip, but everything else was data from a completely different pc. I therefore decided to upgrade and start with a fresh database.

[Hemoco]

Could you please try downloading http://www.lansweeper.com/upgrade352beta.zip
And replace your service by the one included (3.5.2.4)

[Mogens_Olsen]

The problem is with 3.5.2. I do not know whether it was there in 3.5.1 too. If it should have to do with DNS caching, then restarting the service should help, I assume. Also note that I logged on to the ls server and used nslookup to verify that the correct ip was returned.

[Hemoco]

Does this dns behaviour occurs with 3.5.2 or is this problem solved with 3.5.2?

Normally the service does a dns query each time the pc is scanned.
If the old ip is still cached in the dns server or locally it will be used.