We are running 6.0.0.22 and have rescanned our assets but are still experiencing the same problem as the OP in a previous post on this topic (http://www.lansweeper.com/Forum/yaf_postst12838_Ip-Range-Location-problem.aspx#post46037) – any suggestions?
[The ranges were imported from AD and there are NO overlaps]
UPDATE: Any manual changes to assets trigger an IP Range Location refresh resulting in them being correctly identified – but it would be a pain to manually update a few thousand assets.
