|
midrange.com
John,
I did not know of the existence of CWBPING, so I have not tried it - yet!
:-)
I know enough about TCP/IP to be dangerous, and am on my own in this small
shop. 2 of the 3 of us know a little TCP/IP but not enough to fix the
problem. And the problem is mine alone, as the others dial up to signon
and support the 400. I have DSL and have for the last few years supported
through the VPN.
I will try this when I get the opportunity.
Thanks!
At 10:00 AM 10/17/2005 Monday, you wrote:
Have you tried CWBPING instead of PING? CWBPING does the same thing as
the iSeries Access "Verify Connection" - it tries to talk to each of the
iSeries Access services and reports what worked & what failed.
Sample:
C:\Windows>cwbping xxx.xxx.xxx.xxx
IBM iSeries Access for Windows
Version 5 Release 3 Level 0
Connection Verification Program
(C) Copyright IBM Corporation and Others 1984, 2003. All rights
reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
Licensed Materials - Property of IBM
To cancel the CWBPING request, press CTRL-C or CTRL-BREAK
I - Verifying connection to system xxx.xxx.xxx.xxx...
I - Successfully connected to server application: Central Client
I - Successfully connected to server application: Network File
I - Successfully connected to server application: Network Print
I - Successfully connected to server application: Data Access
I - Successfully connected to server application: Data Queues
I - Successfully connected to server application: Remote Command
I - Successfully connected to server application: Security
I - Successfully connected to server application: DDM
I - Successfully connected to server application: Telnet
I - Connection verified to system xxx.xxx.xxx.xxx
--
John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[ mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Essinger
Sent: Monday, October 17, 2005 12:29 AM
To: Midrange Systems Technical Discussion
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=nas1acc12fda96496e4b8625668
f007ab75f&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
------------------------------------------------------------------------
----------------------
--
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 email is for the use of the intended recipient(s) only. If you
have received this email in error, please notify the sender immediately
and then delete it. If you are not the intended recipient, you must not
keep, use, disclose, copy or distribute this email without the author's
prior permission. We have taken precautions to minimize the risk of
transmitting software viruses, but we advise you to carry out your own
virus checks on any attachment to this message. We cannot accept
liability for any loss or damage caused by software viruses. The
information contained in this communication may be confidential and may
be subject to the attorney-client privilege. If you are the intended
recipient and you do not wish to receive similar electronic messages
from us in the future then please respond to the sender to this effect.
--
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 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.
