Cormac
4234
The delivery options connecting to other computers are deactivated already. Though checking the update page it seems like its decided to install 1903 right now and is at 7%…
EDIT:
Ok, I’ve looked at the update log and in the past 2 months its installed about 12 updates (Win 1809 & .NET frameworks & cumulative updates). Since I only use the laptop every 2 weeks, its probable that as soon as I turn it on, it gets busy with those damn updates and I have a slowdown and want to throw it against a wall!
My gaming PC has been stably chugging along on 1803 for over a year now. Why can’t they leave my laptop alone like they do this one?
Windows’ antimalware stuff is really making Thunderbird hard to use since sometime this year or last. It’s awful. :(
Oh gosh. Let’s see. Basically VoiceMeter becomes your primary Windows Mixer. You first set speakers (up to three) and then set input channels, such as a microphone or, in my case, line in for my midi units. You can then mix each of these individually, including your overall desktop volume. It’s a bit complicated at first, I had to watch a few videos to get it to click, but once you figure it out, it’s a godsend.
The FancyZones toy could be pretty useful
Demorve
4238
Had a Microsoft fucked me moment. It started last night, my wife was watching her shows on her computer when all of a sudden she lost all internet connections. She also lost the ability to use our nas drive. I tried the usual things like updating drivers, deleting the adapters and forcing a driver reinstall and etc. nothing worked, however I did use a usb ethernet dongle I had and got her access to the internet, but not the nas drive. Before I go any further I will mention that she is using my old Surface Pro 3 with a docking station. She loves it because it’s super quiet and doesn’t put out a lot of heat. Anyway back to the fuck me moment. This morning before our morning bicycle ride I did a reset of the computer. When we got back home the docking station ethernet wasn’t working, but the wireless did work and I was able to connect to the internet, but not the nas drive. I fussed with it for an hour more before letting her watch her shows. This evening when she was busy I tried to figure out what was wrong. I finally got her computer to actually see the nas drives buy enabling smb1, but I still couldn’t access them. After much googling (it should be noted that it was established in another thread that I’m a shitty googler) I found instructions that had me use the cmd prompt and type in the ip address of the nas drive. I got a message back that said access was blocked due to organizational security policy. After a little bit I found a document from Microsoft that said they turned off access to all requests that don’t have the credentials that windows 10 expect by default. Googled some more and found out how to turn off that setting. Finally I got her access to the nas server and the internet and everything seems to be working fine. So the moral of the story is you might as well enjoy getting fucked over by microsoft because they are going to do whether or not you want them to.
Do you have a link to instructions for turning that setting off? I’ve been having trouble with access to a network drive on our home network.
stusser
4241
My guess is it’s SMB v1, windows doesn’t let you use it by default as it’s insecure.
And yet it is often not possible to enable SMB2 or 3 at all. I’ve even tried directly editing the registry and it still won’t recognize them.
stusser
4243
SMBv2 and SMBv3 are both enabled by default on Win10. If they don’t work for you something is seriously awry.
Enabling SMBv1 is kind of like turning off your firewall or AV - sure, you could be ok for a while or even a long time but it’s an inherently vulnerable scenario and just a matter of time & chance before getting burned.
https://www.us-cert.gov/ncas/current-activity/2017/01/16/SMB-Security-Best-Practices
rei
4245
I had a Buffalo NAS that only used SMBv1 so I stopped using it.
Indeed, but Plex appears to need SMB1 to talk to my NVidia Shield properly. I finally just have up and copied all of my music to portable 2TB drive and attached it to the USB port on the Shield and run it off Plex installed on the Shield instead. But it is baggy that way.
Support for SMB1 was deprecated in operating systems years ago because it’s so inherently insecure. Are you sure you’re doing Plex right? Are you using an old installation of Windows that was upgraded over time?
A clean install of any Windows 10 version 1709 or later will not have SMB1 included.
SMB1 is definitely NOT on the server, but I’ve tried every suggestion I can find on the web to get the server to communicate with the Shield and had minimal luck. So now I’ve abandoned that approach and just attached the external drive directly.
Definitely not an old version of Windows, and no, I’m not sure Plex is all correct. Plex documentation is dreadful. But what I have now works, it is just laggy.
stusser
4249
Nah, SMBv1 is perfectly fine on your home LAN. I wouldn’t use it in a multi-user environment or certainly expose it to the internet.
His problem is that the ShieldTV only supports SMBv1, so he needs to enable support for it on his fileserver.
Demorve
4250
Here’s the short story on what I had to do;
- enable smb v1 just to see the nas drives in windows explorer.
- enable insecure guest logons to actually access the nas drives ( use windows key + r to open the run box, then type gpedit.msc to open the group policies window. Then navigate to “computer configuration\administrative templates\network\lanman workstation\enable insecure guest logons”).
Now for a little more information. The Surface Pro 3 was updated to 1903 and I had to do step 1 and 2 to get access to the nas servers. My gaming computer is build 1809 and I don’t need to step 1 and 2. So something changed in the 1903 build. My nas servers are less than a 2 years old and both are Western Digital. If anyone has any ideas on how to get my wife’s computer to see the nas drives without turning on smb v1 I’d greatly appreciate it. I had to turn on smb v1 just to get my wife’s computer to even see the drives and enable insecure guest logon in order to access the nas drives.
Thanks, Stusser, that sums it up. And while there are a myriad walkthroughs on the web on how to enable it, they just don’t work. Windows is apparently smart enough to block it even if added at the regedit level.
stusser
4252
Shrug, the googleable solution worked fine for me. I have SMBv1 enabled right this very minute. I didn’t use regedit either, just the enable windows features thing.
Pod
4253
Why would this problem happen in the middle of using the NAS?
Hypothetically, perhaps there was a job running in the background that checked if the insecure setting was enabled. I’m pulling that answer from the nether regions so take if for what’s it worth.