I think this is an "it depends" kind of thing - on how the VPN is set up, on name server, as Larry mentioned.

I have an app for VPNing to corporate - it seems to have some web-based flavor - others do, as well.

Once I'm connected, I'm fully in the Windows network and domain and all we have at work.


On 12/14/2013 11:28 AM, Jon Paris wrote:
Heaven forbid that I should disagree with David and Dr. F but ... actually "disagree" is not the right word - "explain to a fellow know-little like myself" would be more appropriate.

I seem to recall that the primary difference when configuring a VPN connection is that I need to use the system name, IP, whatever that I would use _inside_ the local network. Not necessarily the same as the one I would normally use to connect from outside. In my case to connect from outside I use systemideveleloper.com - within the confines of the VPN I simply use ideveloper as if I were on the local LAN. That almost certainly an over simplification but it is the way that I remember it.

On 2013-12-14, at 11:08 AM, DrFranken <midrange@xxxxxxxxxxxx> wrote:

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

Jon Paris


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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