→ Celebrate SysAdmin Day 2024 with Lansweeper Enter our Giveaway here

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
mdevylder
Engaged Sweeper
We are evaluating Lansweeper (great program!) for tracking fileservers on our vessels.
All our vessels have their own local windows 2003 domain. The server is running at the head office, with a different domain name.
Running lsclient.exe at the vessel side transfers the hostname to the server resulting in registering only the hostname in the computers table.
If you use the ping option afterwards from the 'Action' screen, that hostname will not be resolved as the vessels' domain is different and the DNS lookup fails. For the lstrigger command to work from the main server side, you have to enter fully qualified domain name or you cannot resolve the server name of the vessel.
To make things work, i had to add the vessel's hostname in the etc\hostname file, but that is not the right way to proceed.
Any ideas?
Greetings from Belgium

3 REPLIES 3
Hemoco
Lansweeper Alumni
The lansweeper server should be able to resolve all DNS names or active directory lookups will fail.

See last part of: http://www.lansweeper.com/kb/untrusted.aspx
mdevylder
Engaged Sweeper
Thanks for the fast answer. Not sure about the fqdn, the main domain is not aware of the local domain names. Wouldntt it be better if the lsclient.exe sends the fqdn so that the record gets created correctly from the beginning?
Regards
Michel
Hemoco
Lansweeper Alumni
Try: lsclient /scanonip

In the custom actions you can change {computer} by {fqdn}

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now