After Winodws 10 upgrade i cannot see pcs accross MPLS or VPN

I currently have  windows 2008 AD with mostly windows 7 machines. DNS and Wins are setup so you can see other site computers from wherever you are.
I upgraded two pcs to windows 10 and now they can no longer see those computers under the network. I can type \\<server name> to get to them but most users are lost with this methodology. I would prefer not having to send out shortcuts and wonder why it stopped working.
Under sharing i made sure \domain i have network discovery and file and print sharing were on.
any ideas why this stopped working?
Had any luck correcting yourself?
wwtcoadminIT MangerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Aireal LiddleSystems and Security AdministratorCommented:
Hello wwtcoadmin,

I have run into this issue myself after having users upgrade to windows 10. I am sure this is probably now the greatest answer, but it's the only once I was able to get to work.

Go to "This PC" and right click under "Devices and drives" then select "Add a network location".

This will bring up the Add Network Location Wizard. If you select next, it will bring up a window where you can browse the network to add a drive.

You can add any drive you want, because once you do it, you will have access to the whole network. (At least that is what happened when I did it.) Once I added one network location, I was able to see all of the computer and drives on the network under the network drop down.

I realize this solution isn't perfect, but it's the only way I've been able to do it since the Win 10 roll out.

Please let me know if this helps you or if you find a better solution.

Thank you!!!
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Make sure WINS still works and the server(s) are set up to appear in the W10 clients. Though it should not be necessary to use WINS if DNS works, and you are in the same domain, it helps (as you certainly know already).
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Also make sure the Computer Browser service is not running on W10, as those might take over the Master Browser role. This (wrong master browser election) has been an issue since as long as I can remember, and hence I always disable the Browser service on clients, leaving it running on servers only.
wwtcoadminIT MangerAuthor Commented:
All good suggestions
ThatNerdyLady only issue is it has to be run on each system which is about 75 and one server has 8 different shares. That would be quite a few links.
Qlemo yes it is supposed to only run off dns but seems when routers come in Wins is required or at least seems that way.
No changes once i changed those settings

I wonder if it is different on a windows 2012 Active Directory Domain?
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
You won't see results that fast if having to deal with browser.
WINS is great if you have to cross routers, like with VPN - that is true. And the reason we still have WINS enabled.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.