Link to home
Start Free TrialLog in
Avatar of c7c4c7
c7c4c7Flag for United States of America

asked on

Win 10 network discovery problems - need help

This only happens on a single Win 10 Pro machine, brand new out of the box, in a workgroup, that has 7 machines.

Installing software with the installation software on a machine running Server 2012 R2, via shared folder.  All updates are installed.  The installation shows a menu so you can browse to where the data is.  The data is on the server but the installation cannot browse to the server.  I don't know the protocol used to build the list of available machines.

There were no error messages

I finally added the server to the available DNS locations for the workstation adapter.  

Then I had a similar problem on the same machine to install an HP printer on the network, using the HP installation software.  This problem was finally solved by using windows to add the printer using a fixed IP address

AVG pro is used as the AV and Firewall on all machines
All machines are connected via ethernet
Network sharing is turned on
Network discovery is turned on
I've turned off the AVG firewall just to make sure, then turned it back on after it didn't improve anything
Flushed the DNS
Workgroup name is correct
It is in a Private network

I'm running out of ideas, need some help
Avatar of Aaron Tomosky
Aaron Tomosky
Flag of United States of America image

any other machines running current versions of Windows 10? could be the lack of SMBv1 support
suggest disabling smb1 on your server, as long as the rest of the clients support 2 or 3
Avatar of c7c4c7


5 of the 7 machines are running win 10 Pro.  The other running Win7 Pro

I installed three machine on the same day all new out of the box.  All machines in the same workgroup, all had the same software installed all brand new out of the box, only one has the problem.
A question if I might, given you have windows server 2012 R2 running, why are you in a workgroup instead of joining the computers into an AD domain to then have central management of all systems and users?

The issue is with windows 10 and a "security setting"
Have you confirmed that the Function Discovery Resource Publication service is running on the server?

"I finally added the server to the available DNS locations for the workstation adapter": the server should be the ONLY DNS server listed on the workstation.  I'm assuming here that the server is configured (properly) as a DNS server.
Avatar of c7c4c7


arnold - I have no idea that's the way it was when I arrived

CompProbSolv - I understand your point and I'll check.  I agree with Arnold that its a Windows Security issue or it could be SMB  as stated originally by Arron.  I can't check this until the beginning of the week

Logically I don't understand why I only have a problem with one workstation.
Avatar of c7c4c7


Here are some of the things I have verified in services.  All of the following are running and changed to start automatically
Function discovery
SSDP Discovery

I've verified its not a firewall issue, I uninstalled AVG, problem persisted while AVG was off

Used the following Network Discovery command just in case the GUI has a problem for
netsh advfirewall firewall set rule prou="Network discovery" new enable=Yes
Problem persisted

Changed the workgroup name to Workgroup and back again to what it was suppose to be just to make sure some part of that hadn't gone bad.

Found several articles about machines not being visible in a Workgroup after Windows 10 version 1803 upgrade, where Microsoft got rid of Homegroup and turned off several services by default.  Turned them all back on

No machines are visible on the network and the HP printer install software still cannot find the printer
Avatar of c7c4c7
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I have had issues with browsing the network when using Workgroups.  AD works well.

Did you point the offending computer's DNS only at the Server 2012R2?

If all else fails (and you don't want to go to a Domain), consider accessing the server through IP address only.