home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
General
Media Source
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="El_Nino" data-source="post: 1298191" data-attributes="member: 106732"><p>Hello there,</p><p></p><p>[USER=145639]@ge2301[/USER]</p><p>I have read this thread with interest, because I had something similiar with 2.4.1, tree viwe did not find anything (network credentials already entered) but manually adding the UNC path worked.</p><p>But are you really proposing to enable SMBv1?</p><p>Its marked "deprecated" for years, since Windows 10 there is version 3.1.1 available and in 2017 there was an update to deactivate and eliminate this protocol.</p><p>So we are talking about a change of more than 6 years ago.</p><p>SMBv1 is outdated and a security risk (see WannaCry).</p><p>Im a bit confused if its really a wamted solution to go on with SMBv1 instead of v2 or even v3.</p><p>Sorry for my nagging, but im really interested about the technical reasons.</p><p>Maybe there was no time to adapt it or its too difficult.</p><p></p><p>Greetings</p></blockquote><p></p>
[QUOTE="El_Nino, post: 1298191, member: 106732"] Hello there, [USER=145639]@ge2301[/USER] I have read this thread with interest, because I had something similiar with 2.4.1, tree viwe did not find anything (network credentials already entered) but manually adding the UNC path worked. But are you really proposing to enable SMBv1? Its marked "deprecated" for years, since Windows 10 there is version 3.1.1 available and in 2017 there was an update to deactivate and eliminate this protocol. So we are talking about a change of more than 6 years ago. SMBv1 is outdated and a security risk (see WannaCry). Im a bit confused if its really a wamted solution to go on with SMBv1 instead of v2 or even v3. Sorry for my nagging, but im really interested about the technical reasons. Maybe there was no time to adapt it or its too difficult. Greetings [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
General
Media Source
Contact us
RSS
Top
Bottom