RE: Netserver problem

The exposure is known and tolerated at this time. (Notice that I did not
publish the IP address?)

I think we will really need the ability to see the system remotely. AFAIK,
we want to move to VPN soon. For now we rely on AS/400 security, knowing
full well that more protection is needed. And we'll get there.

I have used various ways of getting data to & from, including Client Access
file transfer and FTP. I'll see how much others are relying on the
NetServer function now.

We are also looking at some way to mange software change, maybe cvs, and
this might work nicely with IFS access via NetServer.

I'll be discussing it further and bringing up your points. Thanks for your
input.

At 03:13 AM 4/21/02 -0600, you wrote:
>On Sat, 20 Apr 2002, Vernon Hamberg wrote:
>
> > Yes, ETHERNET is the NT domain when I look in NetServer setup in Ops Nav.
> >
> > Someone else said that my ISP (ATT Broadband, in the Twin Cities,
> > Minnesota) filters NETBIOS. So I'm stuck with if I use plain vanilla
> TCP/IP.
> >
> > Would VPN protect me from the filtering? I think we want to get that going?
> > Do you recommend any Win98 clients?
>
>Running file sharing (meaning windows SMB or NFS) over the internet is
>completely nuts.  Both are fairly chatty protocols and are not designed
>for the kind of latentcies and problems that go along with the internet.
>But worst of all both are massive security risks.  Both protocols depend
>on trust relationships between computers.  Neither protocol contains
>methods for verifying that a certain machine really is who it claims to
>be.  This is why the SMB protocol is rightfully blocked.
>
>The security problems can largely be overcome through implementation of a
>VPN.  A VPN can encrypt and redirect your filesharing traffic in a way
>that can be transparent to both your client and the server.  This won't
>solve the problem of the high bandwidth requirements of both SMB and NFS.
>
>James Rich
>james@eaerich.com
>
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.