This is a combination of questions really that hinge on peer-to-peer network Name Service or lack thereof.
With the release and installation of Windows 10 1803, this has become more critical.
Now, I know that NetBIOS has been deprecated and that Name Service on peer-to-peer networks runs on NetBIOS. So, it *may* be that Name Service is deprecated as well.
It's a little hard to believe that this could be the case but perhaps so.
I also know that a server-based architecture could take care of this issue. But sometimes that isn't going to happen or, at least, not happen quickly.
I also understand that some believe that the Network list of computers is unneeded and is indicative of a bad architecture or practices. I can only respond by noting that we don't live in a perfect world. Rather, we live in a world that must be dealt with as it presents itself to us. Not that we are powerless but there *are* practical limits.
Did I cover enough already?
OK - so I'm dealing with situations that depend on having access to file-serving computers that normally would be accessed using the Network list. Except now they are missing.
I've asked a number of times but it all seems to fold back into NetBIOS being deprecated - so give up??
Examples of this arising include application software that gives a browse capability that can't show everything and/or won't allow typing anything (such as an IP address precursor to a path).
Workarounds that sometimes work are:
- mapping network drives into a local drive letter. I don't like this but it's sometimes necessary.
- shortcuts that don't use up connections unless in use.
Any tips and tricks that might be useful to know?