0
NetBIOS name prioritized over DNS name? If I have samba installed on a Debian 12 based system, Advanced IP Scanner (AIS) shows the NetBIOS name not the DNS name.
For example, see the attached file:

The first two entries are Debian 12 (Pi OS) without Samba. The last two entries are ethernet and wifi interfaces for another Debian 12 (Pi OS) that happens to have Samba installed. Seems to me DNS should take priority over NetBIOS.
DNS hostname is set correctly and resolves correctly for all systems, including the Windows 11 Pro system where AIS is run in this example. The only difference I can see is that Samba is or is not installed when comparing the systems.
Even the Windows 11 Pro system (not shown above) does not show any reference for WORGROUP, and its DNS name is referenced in the scan, which is interesting since it the only other system that as active SMB support.
03/17/202523:0603/17/2025
0
I have used Advanced IP Scanner for several years. I have the latest version installed and have obtained reliable results until recently. My View tab settings only have show alive checked. When I perform a scan of my IP range, 192.168.20.x, all 254 possible connections now show as alive with content displaying for truly live connections. I have cleared my saved items, but most scans display in this manner. Every once and awhile, the scan will yield the results I have historically received, i.e. only actual "live" connections being listed. .
02/04/202520:5902/04/2025
0
ok so I have encountered this problem frequently with Advanced IP scanner and because of which I can no longer trust this to be my "go to" scanner. But I really like it and want it to work

especially this is one of the free scanners which are totally portable.
Problem:I can ping a device on a cmd line just fine.
But this software shows it as "unknown". (I have to enable "show unknown" first, otherwise it does not even show the device.
I have deleted the cache and scanned the whole subnet again, but results are the same.
If it helps, some of these rogue devices are a APC UPS which is not responding to any SSH, telnet or HTTP, but it does respond to ping requests.
01/29/202519:1801/29/2025
0
Scan range: 192.168.1.127/25
Options: none of the additional resources
The resulting scan always lists the Broadcast address 192.168.1.127 as active,
(in my case) with the name belonging to IP 192.168.1.19 (name twice in the list) and
with the MAC address of the scanning Windows computer (MAC twice in the list).
This item "127" in the scanned list is shown as active (blue icon) but of course not reachable by ping.
In my opinion this entry should have no name or should be signed as broadcast, show something like FF:FF:FF:FF:FF:FF as MAC address and maybe get an extra icon. Then it would be easier for everyone to understand.
Or you could leave it out completely which would at least be better than showing false information.
Consequently it could be a good idea to implement an extra check if the scanned data belong to any broadcast address.
At least it is easy to fill the list correctly in the case of a correctly given scan range like in my example.
01/28/202511:4101/28/2025
0
Hello,
After scanning, found devices have a blue or gray monitor icon. I am attaching a screenshot.
What does this mean?
01/24/202511:2901/24/2025
0
Why do you offer a dutch translation when it is just blasfemy
01/18/202522:3901/18/2025