× 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.



   Thanks Kirk,

   I have checked and rechecked, and unchecked those - there are three
   different ones if I recall.  The VPN connects, I can confirm it on the
   Sonicwall side, but the traffic is not getting to the 400 side network.  I
   am going to temp install my old Dlink back and make sure it works with
   that unit.  Then I don't know what I will do. 

   I know the VPN worked from a hotel a few weeks ago, and I have others who
   come in from a sister company over the VPN.  I have not heard them
   complain about not being able to connect.

   Thanks again for your help - If I find an answer, I will post it.

   Jim

   At 12:27 PM 10/18/2005 Tuesday, you wrote:

     The only other thing I can think of is in the LINKSYS. There are a coupe
     of Checkboxes to allow PTPP and IPSEC vpn traffic.  I don't remember 
     the
     exact place in the LINKSYS but those boxes need to be set to ALLOW. If
     they are not set that way, the VPN will connect but won't pass traffic.

     _____________________
     Kirk Goins CCNA
     Systems Engineer, Manage Inc.
     IBM Certified i5 Solution Sales
     IBM Certified iSeries Solutions Expert
     IBM Certified Designing IBM e-business Solutions
     Office 503-353-1721 x106 Cell 503-577-9519
     kirkg@xxxxxxxxxxxxx      www.manageinc.com

     There are 10 types of people in the world:
     Those that understand binary, and those that don't.

     Jim Essinger <esinger@xxxxxxxx>
     Sent by: midrange-l-bounces@xxxxxxxxxxxx
     10/16/2005 10:28 PM
     Please respond to
     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>

     To
     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
     cc

     Subject
     Re: V5R3 iSeries Access ports needed for VPN from home

        Kirk,

        Thanks for your reply.  I agree that I should not have to open any
     ports.
        I have a confirmed connection to the SonicWall fire wall, I have
     looked
     at
        it from the AS/400 network side.  The VPN shows activity when trying
     to
        connect the iSeries Access 5250, but there is no response and it
     times
        out.  I have been working on this now for about 6 weeks (from home
     and
        when I have time) and have not been able to get it going.  Like I
     said
     in
        my original email, I have simply changed the fire wall on my home
     network
        from a Dlink to a  LinkSys.  I am now at a loss, as all else I can
     think
        of has remained the same.

        I have tried opening port 449, as well as 23 (normal telnet port) and
     I
        get the same results.  When I had the Dlink active, I was able to
     ping
     the
        AS/400 from home when the VPN was active. I get no response when I
     try
        now.

        I really don't want to go back to the Dlink as it has less security
     than
        the LinkSys.

        I guess that I will continue to poke and prod my way around this
     problem
        until I give up due to frustration, or find the solution.

        Thanks again for the link - it is what I was looking for, but for
     some
        reason could not find.

        Jim

        At 10:47 PM 10/15/2005 Saturday, you wrote:

          I'm confused... If you have a VPN you shouldn't need to open ports.
     A
          VPN should put you inside the network teh network structure so you
     can
          access resources like the 400.

          But here's the info you are looking for...
          If you are doing Telnet with some product like Mochasoft or
     BOSaNOVA
          then 23 is all you would need. If you want to use iSeries Access
     then
          you will need also need port 449 open. See this link for all the
     ports
          used in iSeries Access
         
     
http://www-1.ibm.com/support/docview.wss?uid=nas1acc12fda96496e4b8625668f007ab75f&rs=110

          Jim Essinger wrote:

            Hi all,

            I know that this has been covered, but I have LinkSys firewall
            appliance at home, and I am trying to get a VPN open to my
     iSeries
            running V5R3.  I have just put in the LinkSys at home, replacing
     an
            older Dlink firewall.  I have tried to open port 23 to allow for
     the
            iSeries Access client to talk over the VPN to my iSeries, but I
     never
            get the session to connect.  The VPN (Sonicwall) says that it is
            connected, and when I check from the iSeries side, the firewall
     does
            report that VPN as connected.  The LinkSys is not allowing, or I
     don't
            know what I'm doing, the 5250 session to connect.

            Is there a port other than 23 that needs to be opened for 5250 to
            work?  I did not change anything on the Dlink, and it connected
     just
            fine.  The only difference now is the change from the Dlink to
     the
            LinkSys.

            Any help will keep me from losing more hair!

            Thanks

      
     
----------------------------------------------------------------------------------------------
            Jim Essinger
            Senior Programmer/Analyst
            UnLtd Support Services
            PO Box 730
            Fruitland ID 83619
            208-452-4058 Ext 133
      
     
----------------------------------------------------------------------------------------------

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.