New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Differences in Netbios vs. FQDN vs. IP

Votes:

0

Your Vote:

Up

Down

On new devices, we are seeing differences in the sensors added based on what we enter into the "IPv4 Address/DNS Name" field. Using the netbios name yields different results than the FQDN name. The IP address yields yet different results. While they all share many of the same sensors, they are not completely the same. The netbios name seems to result in the most sensors.

It is true that we can manually add the sensors, but depending on the name used, they may not all work. Specifically, we have challenges with WMI sensors when not using the netbios name.

I was under the impression that the "IPv4 Address/DNS Name" field was used for name resolution only. However, it seems to actually impact the results.

Why is this?

fqdn netbios wmi

Created on Jun 23, 2017 12:34:44 PM by  miller007 (0) 1



1 Reply

Votes:

0

Your Vote:

Up

Down

Hello there and thank you for your KB Post.

While it should be the same no matter what you use, we've seen that in reality it makes a difference. The "IPv4 Address/DNS Name" is used for name resolution only, but some protocols (especially WMI and Performance Counters) behave differently when establishing the connection/authentication with the target server. Using the netbios or IP also requires additional resolution/checks to be performed, the auto-discovery will skip sensors who's pre-deployment validation doesn't run/pass fast enough to avoid delaying the whole discovery process.

Our general recommendation is: Use only FQDN's whenever possible. This is the fastest to resolve, is stable and works very well with WMI/Perfcounter sensors. If you refer to our "my WMI Sensors don't work KB-Post you'll also notice the recommendation:

Sometimes, this error occurs when using an IP address to connect to a device. Try using the hostname or FQDN (Fully Qualified Domain Name) instead. In PRTG, please enter this information in the device's settings (section "Credentials for Windows Systems").

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Jun 23, 2017 1:22:49 PM by  Luciano Lingnau [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.