On 13 Jul 2018 02:51:42 GMT, Arlen Holder wrote:

That transceiver is set to "Bridge" mode - and it may be blocking the
NETBIOS broadcast packets (I don't know that for a fact yet though).

BINGO!

That is the problem!
http://img4.imagetitan.com/img.php?image=18_pubshare07.jpg
The *cause* of the NETBIOS name-resolution issue has been *identified*!

*The transceiver is apparently blocking the NETBIOS broadcast packets!*

The proof is that simply lugging the computer a few floors down to the
router, and plugging the computer directly into the router, instantly
solved all the SMB NETBIOS name-resolution problems.

Woo hoo! I love figuring out what the problem is!
*Thanks to all your purposefully helpful advice*

NOTE: I usually mark a thread SOLVED but this isn't solved so much as it is
IDENTIFIED as to why one Win10 computer wasn't recognized on the LAN by
other WIN10 computers using SMB NETBIOS name resolution.

It bothered me that almost never on the net did I find anyone who actually
identified the problem where everyone threw commands at the problem until
one of them worked - which I did too - but none of them worked!
(Well, the HOSTS & LMHOSTS will work - but those are hacks.)

NOTE: Yes I could figure out how to use tcpdump & wireshark to sniff out
the packets, but it's crystal clear now what is happening since simply
eliminating the outdoor transceiver temporarily solved the problem
instantly.

The outdoor transceiver is blocking the SMB NETBIOS broadcast packets!

There are a bunch of possible solutions:
1. Figure out how to set the transceiver to pass NETBIOS packets
2. Figure out how to set up a WINS server (which seems like overkill)
3. Or, add a WiFi card to the desktop (I don't have a spare though)
4. Or, just put the static IP address in the LMHOSTS or HOSTS file

I'll first read up on the transceiver software, to see if it's easy to get
the transceiver to pass SMB Netbios broadcast packets, and then, if that
doesn't pan out, I'll do one of the other three solutions.

Since none of those solutions involved Windows 10, per se, this thread is
pretty much over with from a Windows 10 standpoint.

Thanks everyone for your purposefully helpful advice!
(I won't need to post back unless a new solution comes to mind.)