Browsing shares from W10 (2004) on a domain
-
Started having trouble with Win10 (2004) seeing local shares on the network recently. Computers randomly show up in "Network". The proper services are enabled and running per MS documentation:
Function Discovery Resource Publication
Function Discovery Resource Publication
SSDP Discovery
UPnPFirewall is set properly but it doesn't work even if you disable the FW temporarily.
Network Discovery is enabled, and of course the network is private as it is on a domain. It should work without enabling SMB 1.0/CIFS. Users can connect to shares by entering \servername in the file explorer with no issues.
At this point it may be easier to add a startup script that maps the shared drives. Problem is - the users are so used to browsing to the resource they need manually via the 'network' section within explorer.
Thoughts?
-
I had the same problem last Friday. Had to TOGGLE all the relevant settings.
Use Control Panel\All Control Panel Items\Network and Sharing Center\Advanced sharing settings
EXPAND Private Network
SELECT Turn OFF Network Discover
DESELECT Turn on automatic setup of network connected devices
SELECT Turn OFF file and print sharing
CLICK Save Changes
Now reverse the process
SELECT Turn On Network Discovery
SELECT Turn on automatic setup of network connected devices
SELECT Turn ON file and print sharing
CLICK Save Changes
Hope it works for you
Credit to this thread:
https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/windows-10-network-cannot-connect-to-other/05c63394-422f-4b6c-8634-1e3a1258bba8?page=13 -
@brandon220 said in Browsing shares from W10 (2004) on a domain:
Started having trouble with Win10 (2004) seeing local shares on the network recently. Computers randomly show up in "Network". The proper services are enabled and running per MS documentation:
Function Discovery Resource Publication
Function Discovery Resource Publication
SSDP Discovery
UPnPFirewall is set properly but it doesn't work even if you disable the FW temporarily.
Network Discovery is enabled, and of course the network is private as it is on a domain. It should work without enabling SMB 1.0/CIFS. Users can connect to shares by entering \servername in the file explorer with no issues.
At this point it may be easier to add a startup script that maps the shared drives. Problem is - the users are so used to browsing to the resource they need manually via the 'network' section within explorer.
Thoughts?
Receive Segment Coalescing (RSC). Disable that on your file server's pNIC/vNIC and on the desktop/laptop adapters(s) that support it.
-
@brandon220 said in Browsing shares from W10 (2004) on a domain:
At this point it may be easier to add a startup script that maps the shared drives. Problem is - the users are so used to browsing to the resource they need manually via the 'network' section within explorer.
Thoughts?
thought = that's crazy!
Map a drive.
-
@brandon220 said in Browsing shares from W10 (2004) on a domain:
Thoughts?
Create a shortcut on the desktop for our user to get to the shares they need. If AD is setup, use GP to add them.
