2023.7.8.0

[BornToBeRoot]

📄 Changelog
📖 Documentation

---

File	Checksum [SHA256]
Setup	05FC29A3895826A59E4B0AF4EB5D27466308823FDDBCF19A51E5F31E6414413C
Portable	440D8F08D784F9A2B2B58CAB24076F0AA735DF550DD9970ECB4061D3CB5A85FC
Archive	EF6BCDEFEDA23150F8CA2F0292E512E4D5F00BDADA3CDD1BD308B04C9D92C721

System requirements

• Windows 10 / Server x64 (1809 or later)
• .NET Desktop Runtime 6.x (LTS)

---

This discussion was created from the release 2023.7.8.0.

[Hammerfest]

Didn't want to file an issue until I was sure I wasn't missing something but documentation is mum on details to tell me I am wrong or its a bug

IP Scanner, the Hostname field, is there a reason it doesnt resolve for local systems? In your example in documentation on the website it also doesnt show local hostnames.

Any other IP Scanner I use resolves/displays hostnames but NETworkManager does not.

(Portable Version if thats related but think not due to documentation screenshot showing the same)

[BornToBeRoot]

Hi, for me it's working:

You can check if the PTR record is set correctly on the DNS server:

> nslookup
> server <DNS_SERVER_IP>
> <IP_ADDRESS>

You can also try to enable this to show the error message:

[Hammerfest]

Yep, thats set, absolutely nothing.
Your results also don't look like just hostnames either (for windows with its 15 character limit) but a FQDN on something other then a basic network.

Images to follow

Images added, as you can see NETworkManager sees none of the hostnames (names field in advancedipscanner) but others do (AngryIP scanner and one whos name i dont recall for 3 off the top)

[BornToBeRoot]

The 16 chars limitation is only for Windows and the NETBIOS implementation... Maybe the Advanced IP Scanner checks the NETBIOS protocol instead of DNS (or as fallback)...

DNS can have 63 chars for the hostname and max 253 chars for the FQDN (See https://datatracker.ietf.org/doc/html/rfc1035#section-2.3.4).

Does your client resolve the hostname with nslookup?

Example:

nslookup 192.168.x.x

[Hammerfest]

this does seem to be the case, nslookup returns no results registered

This is both on my home network and lab network at work so something is in play to keep registration off.

Ill make a feature request for netbios fallback