Page 1 of 1

Server name cannot be resolved

Posted: Tue Jun 18, 2019 4:13 pm
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.

Re: Server name cannot be resolved

Posted: Tue Jun 18, 2019 4:20 pm
by scottwilkerson
im_msvistalog is a Windows machine.

You should be able to see what server sent the log in the host field

Re: Server name cannot be resolved

Posted: Wed Jun 19, 2019 1:39 pm
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.

Re: Server name cannot be resolved

Posted: Wed Jun 19, 2019 1:42 pm
by scottwilkerson
You should be able to see the same messages in the domain controller if you look at the event viewer