Difference between revisions of "Windows WINS and Network Neighborhood"

m
 
Line 34: Line 34:
Whatever device is handling DNS name resolution for a subnet / network, if a DNS Zone is configured for the same DNS Suffix configured for client computer, make sure of the following: Eliminate all wildcard entries.  IE, if a name from this zone is checked and it doesn't exist, it should return no answer.  If it doesn't, Windows will never move down it's list of how it does name resolution and will never arrive at the WINS or broadcast step: https://support.microsoft.com/en-us/topic/microsoft-tcp-ip-host-name-resolution-order-dae00cc9-7e9c-c0cc-8360-477b99cb978a
Whatever device is handling DNS name resolution for a subnet / network, if a DNS Zone is configured for the same DNS Suffix configured for client computer, make sure of the following: Eliminate all wildcard entries.  IE, if a name from this zone is checked and it doesn't exist, it should return no answer.  If it doesn't, Windows will never move down it's list of how it does name resolution and will never arrive at the WINS or broadcast step: https://support.microsoft.com/en-us/topic/microsoft-tcp-ip-host-name-resolution-order-dae00cc9-7e9c-c0cc-8360-477b99cb978a


== Weird Stuff ==
==Weird Stuff==
 
=== Network Discovery ===
Network Discovery keeps turning itself off after it is turned on: https://www.itechguides.com/network-discovery-keeps-turning-off-server-2016/
Network Discovery keeps turning itself off after it is turned on: https://www.itechguides.com/network-discovery-keeps-turning-off-server-2016/


In short, there are several services that need to be enabled, by setting them to "automatic startup" and / or starting them;
In short, there are several services that need to be enabled, by setting them to "automatic startup" and / or starting them;


* DNS Client
*DNS Client
* Function Discovery Resource Publication
*Function Discovery Resource Publication
* SSDP Discovery
*SSDP Discovery
* UPnP Device Host
*UPnP Device Host
 
=== NetBIOS over TCIP ===
Even if it enabled everywhere, when ''ipconfig /all'' is used, it still shows as disabled.  No solution has been found.  Even this detailed solution didn't work: https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/netbios-over-tcpip-broken-since-upgrade-to/fd141dd9-8500-419d-b8e7-ac7255f44ec0
 
In the end, NetBIOS is related to the name of a computer.  NetBEUI is the protocol for resource sharing (or it used to be a long time ago).  NetBIOS name resolution will still work via broadcasts, but if computers are on different subnets, well, the solution still hasn't been found.