× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



That is true, but then that also leads to other problems your company has,
like your IT guys in the remote locations not following rules.

"IF" policy is correct in all locations, there is fundamentally no
difference in a user over a WAN and a LAN.

I do see what you are saying and I agree it is better safe than sorry.
----- Original Message ----- 
From: "Jim Franz" <franz400@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, December 10, 2003 10:50 AM
Subject: Re: Network question.


> > I can understand opening ports to allow access from the internet, but
what
> > is the difference between accessing the as/400 via your lan and via a
> > company wan?
> I just see wans as each location increasing the potential to backdoor the
> server.
> (like corporate data center location can be tight but the remote location
> has
> backdoor dialup or broadband users into their remote lan, connected to the
> wan).
> Your remote sites need to be as tight as the corp home location, but
common
> practice is often not.
> jim
>
> ----- Original Message ----- 
> From: "Adam Lang" <aalang@xxxxxxxxxxxxxxxxxxxx>
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Sent: Wednesday, December 10, 2003 10:21 AM
> Subject: Re: Network question.
>
>
> > I can understand opening ports to allow access from the internet, but
what
> > is the difference between accessing the as/400 via your lan and via a
> > company wan?
> >
> > I don't think he ever mentioned internet or firewall, though.  Unless
> there
> > is a lot more details he is omitting, odds are it is just a default
route
> he
> > needs to set.
> > ----- Original Message ----- 
> > From: "Jim Franz" <franz400@xxxxxxxxxxxx>
> > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> > Sent: Wednesday, December 10, 2003 9:58 AM
> > Subject: Re: Network question.
> >
> >
> > > see the client access home page for your particular version of CA,
> > > and check the info apars for ports needed to be open in your firewall.
> > > It is more than just port 23 for telnet.
> > > http://www-1.ibm.com/servers/eserver/iseries/access/caiiapar.htm
> > > You should think very carefully about security accessing the 400
> > > via internet or wan.
> > > jim
> > >
> > > ----- Original Message ----- 
> > > From: "Shields, Ken" <kenshields@xxxxxxx>
> > > To: "'Midrange Mailing LIst'" <Midrange-L@xxxxxxxxxxxx>
> > > Sent: Tuesday, December 09, 2003 8:19 AM
> > > Subject: Network question.
> > >
> > >
> > > > Hello again group...
> > > > Have a peculiar problem involving TCP
> > > > Local AS400, and pc's work just fine, however; all pc's external to
> our
> > > router, time out when attempting
> > > > to ping the /400 here.
> > > > Is there something withing CFGTCP which I have to twig, in order for
> > > outside pc's to log onto this /400?
> > > > Thanks in advance
> > > >
> > > > Ken Shields
> > > > Oshawa systems group
> > > > Works 81, Oshawa Ontario
> > > > (905) 725-1144 Ext 326
> > > >
> > > > _______________________________________________
> > > > 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.
> > > >
> > > >
> > >
> > >
> > > _______________________________________________
> > > 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.
> >
> > _______________________________________________
> > 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.
> >
> >
>
>
> _______________________________________________
> 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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.