IP to String - Timing Issue with Windows 10

[Kyle97330]

Where I work it's common to have PCs with multiple network cards, one on the "real" network and another 1-4 that connect directly to equipment.  Because of this we can't use the simple "IP to string" node because it often returns the IP of one of the local equipment's network cards instead of the "real" network.

As such, we use this code to get either the PC name or fully qualified name:

[JLJ]

---

@altenbach wrote:
With dot notiation=false, the function requires an external DNS lookup that is not handled by LabVIEW, but by the OS. I doubt LabVIEW can do anything about this [...] Even some internet security software might intercept the DNS lookup and do their own checking against a database of e.g. malware sited. These things are not necessarily fast.

---

Thanks for the insight. That makes sense, and I expect the latter part of what you said explains what I am seeing. It is a company VPN, and there is not a ton of transparency as to what else is happening, but it seems very likely that security software is trying to do its job and slowing it down. Sounds like I can divert my frustration away form LabVIEW!

[JLJ]

Thanks @Kyle97330 for the snippet! It executes a lot faster on my system while on the VPN than the built-in IP to String (~0.5s vs. ~4.5s), while yielding the same fully-qualified domain name. May take some further investigation (using Wireshark per altenbach's suggestion) to better understand why.