KVR Audio

pljones · Post by **pljones** » Tue Mar 26, 2019 6:41 pm

Hi all,

Just wondering if anyone here can help on this one.

I've two desktops running Win10.

One was an 8.1 box upgraded. It's an AMD CPU (ASUS M5A99X EVO R2.0 mobo) and is happily running the latest Win10 1809 release. (More or less, network browsing is flaky.)

The other one was a Win10 box from day 1. It's an Intel CPU (ASRock Z370M-ITX/ac mobo). I'd been happily keeping up to date until Win10 1809 hit. Of course, it didn't get 1809 for a long time. However, when it did, suddenly I had no access to CIFS shares from my Linux box. (CIFS to our other QNAP NAS remained okay.) So I reverted to 1803 (which worked - I was shocked; so shocked I risked doing it again a few months later, hoping the issue had been fixed...).

Nothing I've seen suggested elsewhere has fixed it. I've seen other reports of the same ... or, at least, a similar ... issue. What's not clear from what I've read is whether it's a "known issue", as the references I've read to tickets at Microsoft end up being not exactly what I'm seeing.

Is this basically some screw-up in the Intel chipset Networking stack with Win10 1809? Or is it something else - i.e. am I just missing something?

Thanks,

-- Peter

telecharge · Post by **telecharge** » Tue Mar 26, 2019 6:55 pm

Have you checked to see if SMB 1.0/CIFS File Sharing Support is turned on in Windows features?

pljones · Post by **pljones** » Wed Mar 27, 2019 7:25 am

As far as possible, I've triple checked settings between the two boxes are the same when on 1809. Once a few more suggestions in, I'll do the upgrade again and have another pass through everything.

telecharge · Post by **telecharge** » Wed Mar 27, 2019 1:22 pm

I'm not sure if it is turned on by default in 1809, but you can check by going to Control Panel > Programs and Features then clicking on Turn Windows features on or off.

stratum · Post by **stratum** » Wed Mar 27, 2019 9:13 pm

If you have access to the linux shell you can also do:

sudo mount -t cifs url_goes_here mount_directory_goes_here -o rw -o username=your_user_name,password=your_password,vers=2.1,uid=your_user_id

pljones · Post by **pljones** » Thu Mar 28, 2019 6:19 pm

This is on the box where 1809 works - i.e. can access the remote share:

WindowsFeatures1809-AMD.png

telecharge · Post by **telecharge** » Thu Mar 28, 2019 7:48 pm

Looks like you don't need CIFS support. If you haven't already, I would check out Event Viewer for any warnings/errors and QNAP's support resources.

pljones · Post by **pljones** » Sat Mar 30, 2019 8:39 am

What are you on about?

metamorphosis · Post by **metamorphosis** » Sat Mar 30, 2019 10:54 pm

Common problem, and yes, it's a 1809-specific problem to do with network shares.
The workaround might differ for you because you're accessing a linux share not a win10 share-
for the win10 shares the solution I found was to create a .bat which turned off, then on, all three networking services, and put it in the startup folder. Can't find the link for which services, pretty sure BITS was one of them.
Literally nothing else worked in my case.

Also resetting the network ('Reset Networking' in settings) can help with some computers.
Otherwise, there's plenty of suggestions on google.

pljones · Post by **pljones** » Sun Mar 31, 2019 7:45 am

Thanks - I'd not seen the "turn it off and on" (for the services) -- if you can dig out what they were, I can give that a go. I think I tried the Reset Networking but I'll give it another go, too.

I've seen a lot of problems reported with 1809 networking but most, when looked into, aren't the same as this. Most get solved - it's only where the server is Linux I'm seeing the unsolvable.

pljones · Post by **pljones** » Mon Apr 08, 2019 4:59 pm

Had another go, still no difference. 1803 sees the server fine, 1809 on the Intel doesn't, settings checked.

Win10 1803 vs 1809 -- Linux CIFS issue