
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-06-2014 03:42 PM
Hi,
I couldn't find any documentation on how the "ping status" orb determines it's status on the asset page. I suspect a server-side script runs a ping to the fqdn of the asset in order to determine if the asset is available or not. Can someone confirm this ?
If it indeed pings the fqdn, is there any way to change this behaviour to ping the ip-address ?
I couldn't find any documentation on how the "ping status" orb determines it's status on the asset page. I suspect a server-side script runs a ping to the fqdn of the asset in order to determine if the asset is available or not. Can someone confirm this ?
If it indeed pings the fqdn, is there any way to change this behaviour to ping the ip-address ?
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-06-2014 03:48 PM
The online status indicator is based on a ping request performed from the server hosting your Lansweeper web console to the client machine.
- If the client machine is a Windows computer, we ping the machine's NetBIOS name, not the FQDN. (Old Lansweeper releases pinged the FQDN.)
- If the client machine is non-Windows, we ping the IP address.
Customizing the online status indicator is not possible.
- If the client machine is a Windows computer, we ping the machine's NetBIOS name, not the FQDN. (Old Lansweeper releases pinged the FQDN.)
- If the client machine is non-Windows, we ping the IP address.
Customizing the online status indicator is not possible.
4 REPLIES 4

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2015 04:05 PM
Thanks for the information

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2015 12:02 AM
It would be very helpful if there was an option to use just the IP address instead of the machine's netbios name.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2015 03:39 PM
joseph.cunningham wrote:
It would be very helpful if there was an option to use just the IP address instead of the machine's netbios name.
We chose the NetBIOS name for better results in DHCP enabled networks. Not sure whether an option will be added to allow you to customize the status indicator.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-06-2014 03:48 PM
The online status indicator is based on a ping request performed from the server hosting your Lansweeper web console to the client machine.
- If the client machine is a Windows computer, we ping the machine's NetBIOS name, not the FQDN. (Old Lansweeper releases pinged the FQDN.)
- If the client machine is non-Windows, we ping the IP address.
Customizing the online status indicator is not possible.
- If the client machine is a Windows computer, we ping the machine's NetBIOS name, not the FQDN. (Old Lansweeper releases pinged the FQDN.)
- If the client machine is non-Windows, we ping the IP address.
Customizing the online status indicator is not possible.
