this issue has plagued me forever since windows 10, and even slightly in windows 8.1. this issue would come randomly and i cant connect to internet even if i were a point blank in front of the router. its extremely annoying and in windows 10 its way more frequent. running the troubleshooting does not fix it. the only way to fix it most of the time is to disable the wifi adapter for about 2 minutes and re enable it again. in some cases only a reboot can fix it and in rare cases it can only be fixed by uninstalling the wifi drivers and starting over.
i have tried with 3 different wifi adapters, 2 computers and 2 routers.
it seems to struggle the most with connecting to optimum wifi/Xfinity wifi (which my laptop is added to my account) its mainly this optimum wifi here causing issues making router itself a issue but still. the other router is my 4g sprint hotspot, sometimes on rare occasion the same thing happens.
You do realize that this is something that has been overly discussed on here and is because Microsoft in their infinite wisdom, decided that they needed to cripple Network by making changes to SMB. Disabling SMB 2 & 3 sometimes works. Brink has a tutorial on this.
This error only appeared on the rollout from January. It was not an issue until the last update. It has nothing to do with your provider or the Gateway you are using.
i read this from M$
is it dangerous to disable smb?
i use symbolic links on my system btw
Why would it. All that you are doing is fixing their mistake. They tightened their version of Samba, because some idiot in sales thought that there was a security risk with it.i read this from M$
is it dangerous to disable smb?
i use symbolic links on my system btw
It was not until 10546 rolled out, that they broke their own OS.
As long as you do not completely disable SMB/CFS. Just disabling SMB 2 & 3 seems to work. Also if you upgraded with a pre-existing Security suite, that has also been a headache for a lot of users.
OK thanks, I'll give it a try and monitor it for a while.
yea it didn't work
Something else is the problem. Just running Windows Defender, turn off Windows Firewall, disabling SMB 1 & 2 worked for me on the desktop I use for software testing when I ran 10 on it.
It saw all Linux machines and my NAS after that and the Linux Machines saw it.
I do not run any kind of firewall on any machines on my network. I have a good hardware firewall built into the Cisco RV-320 thatI use, along with the U-Verse Gateway that uses IPTables.
