Win10 1511 network problem

Topic

New Reply

When I was on W10 ver 10240 ( W7 Pro HP laptop upgraded to W10 on 8/4/15 ) all my network shares ( with my W7 machines ) were listed in File Explorer>network. I went to W10 ver 1511 last week and the only computer listed ( on the W10 laptop ) is the W10 laptop itself. It doesn’t see the other W7 machines now BUT the W7 machines see the W10 computer and list it in Windows Explorer>network and I can access the W10 machine from them.
This isn’t a homegroup setup, W7 computers all have assigned IP’s and W10 is auto which worked fine on ver. 10240. Network and Sharing settings are the same on all machines.
After reading Susan’s article in the last newsletter I see that this seems to be a bug for many and there seems to be no definite fix from MS at this time. There were many little tweaks posted that seemed to work for a few but not all. She posted this link:
https://social.technet.microsoft.com/Forums/en-US/2131750e-d589-41f0-b6a3-1c7dac2361d9/cannot-connect-to-cifs-smb-samba-network-shares-shared-folders-in-windows-10-after-update?forum=win10itpronetworking

Has anyone else on these forums experienced this behavior and if so, have you been able to resolve it? If so, how?

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Replies

Yes it started back with the Nov build release. I Used insider build 11102 and the problem was resolved.
Joe

Reply | Quote

Thanks Joe S but unfortunately I’m not on the “Insider Program”. In another thread, Coochin mentioned the same results on the insider build. Hopefully MS will fix this problem for the rest of us soon.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Following suggestions by RG & Coochin from a different thread, I typed in one of the win 7 computers names in the address bar of the W10 computer and it displayed in File Explorer>Network.
I could access it just as before, but when I close file explorer and re-open it, the win 7 computer is gone. So I know that the network is still intact but W10 just won’t show the rest of the network to make easy access to it.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

My laptop has Win10 “Version 1511 (OS Build 10586.71)”, which I think is the same as yours lumpy.

Other computers on my network are showing as expected under Network in File Explorer.

Reply | Quote

My laptop has Win10 “Version 1511 (OS Build 10586.71)”, which I think is the same as yours lumpy.

Other computers on my network are showing as expected under Network in File Explorer.

So if I understand you correctly Coochin, you have the same problem as I do with ver. 1511 on a laptop with W10?

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

So if I understand you correctly Coochin, you have the same problem as I do with ver. 1511 on a laptop with W10?

No, on my Win10 laptop the other computers on my network are shown and I can access them under Network in File Explorer.

If I understand what you have previously posted 1511 Build 10586.71 on your laptop is not showing other computers on your network under Network in File Explorer.

Reply | Quote

No, on my Win10 laptop the other computers on my network are shown and I can access them under Network in File Explorer.

If I understand what you have previously posted 1511 Build 10586.71 on your laptop is not showing other computers on your network under Network in File Explorer.

Correct. As I posted in #4, I can type in the name of another computer in the address bar of W10 file explorer ( example: \other computer ) and then it will show until I close file explorer. It won’t be there when I re-open file explorer so I have to go through the procedure again to see/use other computer.
Something changed in showing all my computer shares on the W10 laptop when it upgraded from 10240 to 1511. I have all the same settings in “Network and Sharing” as before. I also checked in the firewall to make sure that “File and Printer Sharing” is checked.
I’m really stumped as to why all the other computers stopped showing under Network in W10 file explorer.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

…I have all the same settings in “Network and Sharing” as before…

Are there any errors to do with networking in “Event Viewer”? It sounds like a needed service is not running.

You could try running “Windows Repair” from: http://www.tweaking.com/content/page/windows_repair_all_in_one.html

Reply | Quote

Are there any errors to do with networking in “Event Viewer”? It sounds like a needed service is not running.

I don’t see anything in the event viewer specifically stating “Network error”. There could be errors related to network but I am not smart enough to know what they are.
I had hoped that today’s WU might resolve the problem ( it went to build 10586.104 ) but it didn’t. If I can’t get this resolved, I may just go back to 10240 which worked fine or just put up with the inconvenience.
Kind of a pain though either way.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

I had a network problem like yours involving a laptop (WIN 10) and my desktop (WIN 10).
The laptop couldn’t “see” the desktop for some unknown reason. I googled this fix that worked.
Go to CONTROL PANEL>ADMINISTRATIVE TOOLS>SERVICES
Stop, start, and set to automatic start the following:
DNS Client
Function Discovery Provider Host
Function Discovery Resource Publicaton
Peer Networking Grouping
HomeGroup Provider
Home/group Listener
SSDP Discovery
UPnP Device Host

Save and apply all changes.
HTH
Preston

Reply | Quote

I had a network problem like yours involving a laptop (WIN 10) and my desktop (WIN 10).
The laptop couldn’t “see” the desktop for some unknown reason. I googled this fix that worked.
Go to CONTROL PANEL>ADMINISTRATIVE TOOLS>SERVICES
Stop, start, and set to automatic start the following:
DNS Client
Function Discovery Provider Host
Function Discovery Resource Publicaton
Peer Networking Grouping
HomeGroup Provider
Home/group Listener
SSDP Discovery
UPnP Device Host

Save and apply all changes.
HTH
Preston

Didn’t work for me so I guess I will try to change everything back and hopefully not make a mistake.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Thanks Preston, I will give it a try.
Another strange thing happened though today. 1 of the computers on the network that I seldom have on ( an old win 7 Pro 32 bit desktop ), was turned on today because of WU day and Lo & Behold, it shows up in the W10 laptop File Explorer>Network listing. So for some reason the old 32 bit win 7 shows up but the other 2 win 7 64 bit computers don’t.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Thanks Preston, I will give it a try.
Another strange thing happened though today. 1 of the computers on the network that I seldom have on ( an old win 7 Pro 32 bit desktop ), was turned on today because of WU day and Lo & Behold, it shows up in the W10 laptop File Explorer>Network listing. So for some reason the old 32 bit win 7 shows up but the other 2 win 7 64 bit computers don’t.

This may be too simplistic, but I also had similar problems when one of my LAN’s pc’s was upgraded to win 10. My issues were very simply resolved by adding a local (admin) account to the win 10 pc with the same login credentials as it had with win 7, as well as the MS acount login.

Reply | Quote

Thanks petermat, but I already have a local account with the same login as the other machines.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

From what I have read so far, MS is “supposedly” working on some type of fix for this problem, possibly to be released in March.
In the meantime, I have found a short term work-around by opening file explorer, clicking on network, typing in the sharename ( \workstation ) in the address bar, hit enter and then drag the sharename to the desktop ( creating a shortcut on the desktop ). I did that for all the other computers on my network. It’s a pain but it works and beats having to type it in everytime.
Just thought I would post this in case others have the same problem since it seems that some do and some don’t for some reason.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

I decided to run perfmon /report and found that a service had “unexpectedly stopped” ( Net.Tcp Listener Adapter ) due to Error 1068. So I went to services.msc and found that service is set to automatic so I tried starting the service and got Error 1068 saying that windows couldn’t start it on the local computer. Could this be the problem with not finding the other computers in file explorer>network?
43635-perfmon-1 43636-perfmon-2 43637-perfmon-3 43638-services-error-W10

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

This thread seems to have come to a halt so I posted a question on another forum about this problem. Is it ok to leave this thread as-is until I can find an answer or should it be closed even though it is unsolved?

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

This thread seems to have come to a halt so I posted a question on another forum about this problem. Is it ok to leave this thread as-is until I can find an answer or should it be closed even though it is unsolved?

See rule #14 at: http://windowssecrets.com/forums/faq.php?faq=rules_vision#crossposting

In particular the link in the second paragraph “A message to cross posters”.

Reply | Quote

Thanks Coochin. If I understand that link correctly, I need to include a link to this thread in the other forum then, or do I have it backwords and need to include a link from the other forum in this thread?

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Thanks Coochin. If I understand that link correctly, I need to include a link to this thread in the other forum then, or do I have it backwords and need to include a link from the other forum in this thread?

As I understand it the intention is to let other posters know what has been posted in both forums, so I would post a link to this thread in the thread in the other forum, and a link to the thread in the other forum in this thread.

This allows anyone who wants to see everything that has been posted.

Reply | Quote

I posted here :
http://www.cnet.com/forums/discussions/workgroup-networking-after-1511/

and here:
http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/after-1511-update-other-network-computers-dont/73a072fe-e96a-4faf-9a73-55d37e313667

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Just to clarify why I tried posting my question to another forum in addition to this forum. I have been getting good sound advice for a loooong time here and it has always been appreciated, but this particular problem seems to be un-fixable at this time so I decided to spread it out to see if there are any more ideas out there. I certainly don’t want to upset anyone here and not get answers to questions anymore.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Today W10 updated with KB3140743 and KB3139907 taking it to build 10586.122 and now the other computers show up in file explorer>network.
So I will mark this as solved.
Thanks to all that tried to help.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote