|
Agree with Jim wholeheartedly...should never share the root. Just because someone is seasoned doesn't make he or she immune from mistakes or oversights. Development systems are usually fairly lax on security yet still hold production data to test with.--
Steve Pitcher
iTech Solutions Group, LLC
p: (203) 744-7854 Ext. 176 | m: (902) 301-0810
www.itechsol.com | www.iInTheCloud.com
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Thomas Garvey
Sent: Wednesday, September 25, 2019 7:31 PM
To: raul <raul@xxxxxxxxxx>; Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: SMBV1 issue
This box is used strictly for development by two seasoned developers.
I see the screen shot didn't make it through.
Here's the text of that...
/The mapped network drive could not be created because the following
has occurred:// //You can't connect to the file share because it's not
secure. This share// //requires the obsolete SMB1 protocol, which is
unsafe and could// //expose your system to attack.// //Your system
requires SMB2 or higher. For more info on resolving this issue, see:
https://go.microsoft.com/fwlink/?linkid=852747/
It works on my v7r3 partition. Is there something that can be done to get it to work on this old v5r4 partition?
Seems like it must be some protocol on the server, no?
Best Regards,
Thomas Garvey
On 9/25/2019 4:47 PM, raul wrote:
It is very dangerous to map the root directory to a pc--
El 25-09-2019 17:37, Thomas Garvey escribió:
Hi,-- Este e-mail fue enviado desde el Mail Server del diario ABC Color
Tried to map a network drive on my Windows 10 PC to the root of one of our IBM i servers (running v5r4).
Got the following message...
I used to be able to do this.
I saw a note on the archives from Rob Berendt about this but it wasn't clear to me what needs to be done, or if it would work on my old v5r4 server.
Since it's a protocol located on my PC, it seems it's a Windows 10 issue.
Anybody else dealt with this?
-- Best Regards, Thomas Garvey
-- -- Verificado por Anti-Virus Corporativo Symantec --
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
