I've done something similar, but use 127.0.0.1 rather than 0.0.0.0 and include the 'testip' tag. I forget exactly why I do this, but as I recall I found an odd interaction between xymonnet and unresolvable hostnames when using 0.0.0.0.
-- Do things because you should, not just because you can.
John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska
On 8/4/2015 4:49 PM, Kris Springer wrote:
I have a number of clients behind firewalls like that. Here's how I enter them into my Xymon Server's hosts.cfg file.
0.0.0.0 PC-Name # noconn dialup
I then make sure the BBwin config on the client machine is setup correctly to send it's data to my Xymon server. This gives me all the info I need about the client machine. What it doesn't do is 'ping' it. But client machines are always turning off and on anyway so I don't really care if I can ping it. Hope this helps.
*Kris Springer* *Innovate! Inc.** * *Systems Admin & Support* *(Google, Salesforce, SharePoint, JungleDisk, MS Office, Internal Servers, Network, User Hardware/Software, Win/Mac)* /=======================/ / /
On Tue, Aug 4, 2015 at 3:22 PM, Nicolai Hviid NiRu.dk <nicolai at niru.dk <mailto:nicolai at niru.dk>> wrote:
Hi, I want to use the bbwin client from outside my network and have multiply clients reporting data to my xymon server at 1984. But how do I add them to the list when they are reporting from the same ip but with diffrent names ? Med venlig hilsen/Best regards Nicolai Hviid