Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Manfred]

After a serious Win 10 Crash with the latest Win 10 Update, I had to restore Win to a previous backup point. I did a new install of MC and restored the library from my backup.
The server under Networks is no longer seen. Network= Private. Network Discovery= on.

I have two media renderers:
Server->MR (Living Room) | The one who does not seen the server under networks in the explorer
Server->MR (Office) | No Problem

Does MC require SMBv1?

How can I see my Server and the drives on the server if no SMBv1 is installed?

[Hendrik]

MC does not use such low level functionality. It uses SSDP for discovering DLNA servers and other Media Center instances, and it uses OS-provided functions to access file shares, if appropriate.

[Manfred]

Ok.

If I use M:\....\*.mkv in MC and I can not map the drive on my media renderer or it does't show up does it then create a problem?

[swiv3d]

It might be worthwhile going to settings>network and running the network troubleshooter.

[RoderickGI]

If you use "M:" in your MC Library, and M: was previously a mapped drive, but you can't map that drive now, then MC won't work.

I think you saw this thread that discusses how to mapped drives without SMBv1: https://yabb.jriver.com/interact/index.php/topic,114852.0.html

But MC doesn't need SMBv1 for Clients to see the Server, and visa versa, as Hendrik says.

Also, the Client doesn't need to see the M: drive in order to play. The Server does. However, if you are using the setting "Play local file if one that matches Library Server file is found", that functionality won't work unless your Renderer can also see the M: drive.

[Manfred]

RoderickGI: Thank you very much!

I did not see the thread but I googled the internet. Got my network shares back.

But after a Windows 10 monthly upgrade do the "Function Discovery Provider Host" and "Function Discovery Resource Publication" services to a Startup Type of Automatic (Delayed Start) stay at automatic?

It is definitely a workaround and not a user friendly Microsoft solution.

Video is back in MC and working. 

[fitbrit]

I'm finding that in every new install of Win 10 Pro 64 bit that I do, the Windows feature SMB 1.0/CIFS File Sharing Support is turned off as a default. Very frustrating when trying to see drives/shares on your network until you remember to go into Programs and Features to turn it on. The better option is to migrate all connected devices to newer standards instead of continuing to rely on an insecure version.

[Hendrik]

Do remember that SMBv1 is riddled with security issues. They are not turning it off willy-nilly. The better option is to migrate all devices to newer version of the protocol, instead of just re-enabling it forever and ignoring that fact.

[fitbrit]

Do remember that SMBv1 is riddled with security issues. They are not turning it off willy-nilly. The better option is to migrate all devices to newer version of the protocol, instead of just re-enabling it forever and ignoring that fact.

Thanks for that information.

[RoderickGI]

But after a Windows 10 monthly upgrade do the "Function Discovery Provider Host" and "Function Discovery Resource Publication" services to a Startup Type of Automatic (Delayed Start) stay at automatic?

They have switched to Automatic without the delayed start for me, but everything still works fine. I guess the delayed start isn't necessary for my environment.

Thanks for that information.

  Cheeky. Almost word for word! 

[fitbrit]

Cheeky. Almost word for word! 

I was being sincere.  ? ?
One of my rare serious moments

[RoderickGI]

I was being sincere.  ? ?
One of my rare serious moments

Oh! Sorry then. It just that I read this;

The better option is to migrate all connected devices to newer standards instead of continuing to rely on an insecure version.

and then this;

The better option is to migrate all devices to newer version of the protocol, instead of just re-enabling it forever and ignoring that fact.

and I thought some cheek was involved. But a bit of cheek is fine by me. 

[fitbrit]

Mine was a direct quote - Hendrik (or someone else?) must've edited it after I quoted it.
Makes sense now. I didn't know the original was now different.