Greetings. Not going to address the many over the top statements in these
posts.
Yes, IBM is very much aware of this issue. The problem is the Windows
side has changed their behavior and is broken. They have put out a fix
for Windows 10 so this issues should not longer be occurring once you are
at their latest software level. We work very hard to help get these issues
corrected either making updates to the IBM i side where it makes sense, or
to help pursued others when its applies.
Tim
<midrange-l-bounces@xxxxxxxxxxxx>
message: 2
date: Thu, 29 Jun 2017 07:43:26 -0400
from: Rob Berendt <[1]rob@xxxxxxxxx>
subject: Re: Netserver SMB V1 and recommendations against ransomware
As much as I'd like to either immediately ignore or argue with Nathan on
this issue since I often get the impression that he asks questions not to
get an answer but to change your opinion, I'll pause.
Actually, in many ways Nathan is right on this. Not to the point of an
absolute though. IBM i isn't really the best system for straight file
serving. We used to do quite a bit of it on IBM i (and it's predecessors
such as OS/400). Users complained about the slow response time. We tried
integrated PC servers running on the same hardware (FSIOP, IXS, etc). They
were much faster. We came to the conclusion that IBM i just wasn't coded
right for file serving. We had a system with 9 IXS cards in it. All gone
now. IBM has made some improvements in file serving performance but it
doesn't rank yet with other platforms.
Most shops will have at least one Windows server on site. Like many shops
we have a plethora. Most shops are heterogeneous shops with multiple
operating systems. Use the strengths of each.
Now there are times when file serving off of the IBM i may make sense.
Cases in point include file import and export. Sure, you could send stuff
out as email. Or serve it up as a ftp site or web site. I feel the ftp
site and web site are onerous work arounds that add work to the end users
versus just a file share for simple data exchange. In a heterogenous shop
would you end all file serving on those other platforms and replace them
with FTP sites or web sites? Probably not.
But, in general, with IBM's intransigence regarding SMB2 I feel it is best
to move file serving off of IBM i. But I can see why some shops would
like to leave their data exchange file serving there for now.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
[2]
http://www.dekko.com
From: Arco Simonse <[3]arco400@xxxxxxxxx>
To: Midrange Systems Technical Discussion <[4]midrange-l@xxxxxxxxxxxx>
Date: 06/29/2017 07:16 AM
Subject: Re: Netserver SMB V1 and recommendations against
ransomware
Sent by: "MIDRANGE-L" <[5]midrange-l-bounces@xxxxxxxxxxxx>
Because it can?
Let me ask the opposite: Why would I move our files off the IBM i, which
is
our main server for the business applications. I'd like to keep it
together. And when I start moving things off from the i, where will that
end?
Best regards,
-Arco
2017-06-28 23:47 GMT+02:00 Nathan Andelin <[6]nandelin@xxxxxxxxx>:
> We haven't used Netserver since the 90's. This discussion piqued my
> curiosity; why are you allowing drive mappings to the IFS?
>
>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: [7]MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [8]
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [9]MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [10]
http://archive.midrange.com/midrange-l.
Please contact [11]support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: [12]
http://amzn.to/2dEadiD
</midrange-l-bounces@xxxxxxxxxxxx>
References
Visible links
1. mailto:rob@xxxxxxxxx
2.
http://www.dekko.com/
3. mailto:arco400@xxxxxxxxx
4. mailto:midrange-l@xxxxxxxxxxxx
5. mailto:midrange-l-bounces@xxxxxxxxxxxx
6. mailto:nandelin@xxxxxxxxx
7. mailto:MIDRANGE-L@xxxxxxxxxxxx
8.
http://lists.midrange.com/mailman/listinfo/midrange-l
9. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
10.
http://archive.midrange.com/midrange-l
11. mailto:support@xxxxxxxxxxxx
12.
http://amzn.to/2dEadiD
midrange.com
