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.
Server name cannot be resolved
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Server name cannot be resolved
im_msvistalog is a Windows machine.
You should be able to see what server sent the log in the host field
You should be able to see what server sent the log in the host field
Re: Server name cannot be resolved
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.
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Server name cannot be resolved
You should be able to see the same messages in the domain controller if you look at the event viewer