Windows 10: Win 10 pro still got networking problems ??

First of all an apology if I have missed anything after looking at a huge number of websites/forums over the past 4 days but I have come to the end of my tether on this much written about problem.

This relates to win 10 pro 1511 10586 420 and happened after updates KB3149135 or KB3163018. All my networking set up was trashed and had to use netcfg -d to get it back into some form of working order.

I have a desktop PC and several client computers on my network including an old XP machine. All Laptops run Win 10 HOME. I can see all the computers on the network on the Desktop PC and they are correctly identified. All client computers can access all other computer shares and the Desktop PC as well BUT the desktop PC can access the XP PC perfectly but cannot get at the shared drives on the client computers. If it try the normal method to access the clients Win 10 machines I get the usual error
Windows 10 pro Network Error Code: 0x80070035 Windows cannot access\\__
but I can ping all computers and connect to the win10 machines via IP addresses and access all shared folders etc.
Now I can assure you that everything is set up correctly on all machines so please do not assume that I am a newbie as I have over 30 years experience !!
Can anyone shed any light on what may be causing this common problem. I have tried everything I have come across via Google but still have the problem. The IP address access route works but cannot get anywhere with any other means.
Thanks in advance*Sad

:)

 

Windows 10 upgrade fail

Tried 1 last time. Got Win 10 to install finally, but lost network adapter, USB drives and sound. Fixed some of the issues but system still not fully functional under Win 10. Rolled back to Win 7 Pro. Big mistake to try to upgrade to 10.

 

no devices

finally got the icon to get Windows 10, got a message "no supported networking devices connected", what does this mean? can't get win 10 because ...........????? (Now running Win 7 Pro, Google Chrome)

 

That problem that you are having is posted in a very long thread at the top of the list of topics in this forum. It was created by Microsoft wanting to remove "Guest" access, to protect the end user. In turn they broke the OS.

 

Have you added Windows Credentials to the desktop PC?

ctrl panel\Credential Manager\Windows Credentials\Add a credential.
First box enter the compname of the comp you want to access
Second box enter the username of the user who owns the shares in this form:- compname\username
Then enter password of client user.

Good luck!

 

This is the problem that started with 7 and it got grossly worst with 10, when Microsoft started to tighten up security protocols for networking. Part of it had to do with 6:4 Toredo Tunneling. Do not know why it reared its even uglier head with 1511, but for some reason, only certain chipsets for networking are getting the error, while others do not. It started with Netstat and NB-Session-IN (Ports 139 and 445). Some have found just disabling NetBios over TCP has solved the issue.

 

Thanks for the reply---yes, I have tried setting up credentials but unless I am doing something wrong I still cannot connect. By the way all win10 computers use MS accounts so what do I use for a user name as my user login is the email address plus password.
Am giving up now and will have to use direct access with IP address !
Thanks

 

No, no, the username you need is not your email address. It is c:\Users\username

And the user credential is not yours but the one on the comp you are trying to access.

Have another go!!

 

Hi--Thanks. I have not been using the e mail address---it was just a question. however if I enter the user name as per your message of C:\Users\username it generates a error message that it is too long or not in the correct format !!
Cheers

 

Here's a little snippet for you.

Ignoring the desktop PC my other win 10 home machines talk to each other correctly so for an experiment I deleted all windows credentials and then started form afresh. When I attempted to go to the shares an these computers I was asked to complete the credentials form which of course asked for username and password. Now bearing what I said earlier on that I use MS Account login I entered my MS A/c username which WAS the e mail address and the correct user password and it worked perfectly and when I checked up on the stored window credential there was indeed my e mail login.
I have never ever been asked to fill in credential data from the desktop computer.
Thanks

 

Well, you have taught me something. Indeed, credential manager will accept the email address as the username!!

Wonder if the fact that the desktop doesn't ask for credentials is the key? Was win 10 on the desktop a clean install or an upgrade?

Check the registry a la this post- Solved Network Shares not seen with MS account - Windows 10 Forums

To confirm, does desktop display all the shared comps with explorer/Network?

Set windows explorer view to 'Details' then rt click on the header line and tick to display Discovery method.

Presuming you can see all the other comps, what is the discovery method? Mine show WSD for other comps and NetBIOS for NAS and Printer.

Keep at it!!

Just want to check your displays against mine.

 

Hello again .OK to first answer your questions.

All network computers are shown in explorer with WDS as discovery method

My system was an upgrade from Win 8.1 pro

Now the best bit !!

Reading the thread that you mentioned there were no SMB entries under Lanman server parameters which I believe is correct for win 10 but in that thread it referenced another thread

https://support.microsoft.com/en-us/kb/2696547

Now being an inquisitive person I enabled the SMBv2 and SMVb3 with the following commands as per the thread

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto

Rebooted and IT WORKS !!!!

I can now access the shares on all computers

So I have not got a clue as to why but someone out there may know but a big thanks for suggesting that thread
*chuckle

 

Good to know you have success but those sc.exe commands shouldn't be necessary with an up-to-date system. MS fixed this problem with an update.

If desktop has all updates it is still a puzzle, but, can't argue with success!

Cheers.

 

Ok---my computers are all bang up to date with all the updates and as I mentioned in my opening comments one of two updates broke my system. This desktop win 10 Pro PC has never had any network problems at all since Win 10 first put on it. We will never know why it "broke" but at least it is now restored again to full order irrespective of what I did and what changed.
That I am afraid is "Windows" !!!
Regards to all