RE: Samba

The biggest knock on SAMBA is related to security in my view. Netserver
follows IBM i security exactly. SAMBA has its own model that in my view is
not as robust as Netserver.

That having been said, having SAMBA on the platform is a great addition to
the already strong toolkit administrators have to utilize the resources of
the POWER platform, and the SAMBA admin needs to know SAMBA not IBM i. Add
in SWAT and/or WEBMIN, PHP, pick your WEB content management tools and
you've about clobbered any reason for an Intel network. Remember IBM i
already does LDAP so you don't even need Active Directory really. (Yea, I
know AD has more than just LDAP but those tools are all on IBM i as well)

Also since the 80GB restriction on the load source for a virtualized V7R2
partition has been lifted you can virtualize servers some much easier to the
size you need, and with NFS in the tool kit, now you can really lock down
data if you want to. (To counter my earlier point about security)

Would I pick SAMBA over Netserver, maybe, maybe not? It depends on the
customer requirements.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Richard Schoen
Sent: Monday, March 30, 2015 8:26 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Samba

Right, both NetServer and Samba use SMB. That's just fact :-)

You would pick Samba over NetServer if you wanted a more reliable file
serving experience from IBM i I guess. I started the conversation to get IBM
to bring a Samba server onboard to the i several years back, but given the
timeframe for rollout and lack of information on installing and configuring
it, we will most likely stick with NFS until it becomes easier.

We've had good luck with NFS so we've recommended NFS since it's been
predictable and stable.

As far as using SMB over WAN, it may not be the most efficient, but many
companies hook up and use SMB over a WAN.

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx www.rjssoftware.com

----------------------------------------------------------------------

message: 1
date: Mon, 30 Mar 2015 07:08:09 -0400
from: rob@xxxxxxxxx
subject: Re: Samba

And SMB affects both NetServer and Samba, right? And is not specific to
either one?
And the point of that is what?
- Advise having distributed local servers?
- Suggesting another technology, such as NFS?

And why does it perform horribly over WAN?
- Is it generally because of the large volume of data in BLOB stream files?
- Is it because of some default blocking size often set in WAN's?
- Is it because of some difference between local blocking size and that of
ISP's?

Steve, not jumping on your case, really. Just trying to get the most
benefit out of such a broad statement.


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
http://www.dekko.com





From: "Steve Landess" <sjl_abc@xxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 03/27/2015 11:55 PM
Subject: Re: Samba
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Be forewarned that SMB protocol performs horribly over WAN's...
-sjl



Confidentiality Notice: This email, including attachments, may include
confidential and/or proprietary information, and may be used only by the
person or entity to which it is addressed. If the reader of this email is
not the intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of this
email is prohibited. If you have received this email in error, please notify
the sender by replying to this message and delete this email immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.