Server name cannot be resolved

This support forum board is for support questions relating to Nagios Log Server, our solution for managing and monitoring critical log data.
Locked
telecotek
Posts: 2
Joined: Tue Feb 26, 2019 11:10 am

Server name cannot be resolved

Post by telecotek »

Hello,

been trying to track down this error.

The server name cannot be resolved.

Error: The object was not found.

Server name: t:300

Guidance:
The client cannot resolve the server address in DNS or WINS. This issue often manifests immediately after joining a ...

I get it multiple times a day from different server names always starting with t: and then a random number example t:100 t:300. the SourceModuleType is im_msvistalog.

I thought this might have something to do with nxlog running as googling that name brings up a bunch of nxlog hits.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Server name cannot be resolved

Post by scottwilkerson »

im_msvistalog is a Windows machine.

You should be able to see what server sent the log in the host field
Former Nagios employee
Creator:
ahumandesign.com
enneagrams.com
telecotek
Posts: 2
Joined: Tue Feb 26, 2019 11:10 am

Re: Server name cannot be resolved

Post by telecotek »

The host is the domain controlled and this is where this error is coming from. The server name is t:300 and I don't have anything like that on my network that I'm aware of. So strange.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Server name cannot be resolved

Post by scottwilkerson »

You should be able to see the same messages in the domain controller if you look at the event viewer
Former Nagios employee
Creator:
ahumandesign.com
enneagrams.com
Locked