Agree with David. The VPN is at Level three in the network stack while
IBM i Access is an application and works in the higher layers. First
assure the VPN is working then IBM i Access should work just fine.
Absolutely check name resolution as that's critical. Use NSLOOKUP
server.domain.tld to verify resolution. This also tells you the name
server IP address that responded. This can also be important because
many VPN connections change your DNS server(s). This is so you get
private IP addresses for the services across the VPN while still
getting public IPs for the google et. al.
That said be aware that many VPNs block ICMP traffic (PING et. al.) so
don't panic if PING doesn't work. Instead use CWBPING
server.domain.tld to veryify the connection. This program attempts to
connect to each of the required servers including telnet and reports
success or failure on each port.
- Larry "DrFranken" Bolhuis
On 12/14/2013 10:55 AM, David Gibbs wrote:
On 12/13/2013 10:23 PM, Booth Martin wrote:--
Is there a tutorial or instructions on how to connect with VPN?
I have Client Access, iSeries Navigator, and RDi. I have used VPN
with Client access but that setup was in 2009 and I have no idea how
I did it back then,
The VPN I am trying to use to connect is: SHREW SOFT VPN CLIENT That
installed, and it shows as connected when I start it. But I can't
figure out what to do next.
There's nothing special (that I know of) about using CA with a VPN.
The key is getting the VPN to work correctly.
If you can connect to the host on port 23 using a standard telnet
client, you should be able to use CA.
Can you ping the host? Does it's hostname resolve to an IP?
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at