I would recommend checking out the forum thread in kanek's post, which explains what is causing this issue and how you can manually fix it. A fix is already built into the 6.0 beta release of Lansweeper I believe, but not in the 5.3 production release yet.