Re: Client Access to VPN'd system

Just some random thoughts:

1. Is the 400 on the 192.168.0.0 subnet? If not, you'll need gateways set
up on your Windows machine, I think.
2. I used to work where we connected with VPN and then used, I don't know,
Rumba and/or WRQ Reflection. No problem.
3. CA, no matter what version, WILL want a HOSTS file, IIRC.
4. The 400's got to be in the same network as you are, or reachable with a
next hop/gateway.
5. Port should not matter, IMO.

At 04:57 PM 3/26/02 -0500, you wrote:
>Using CA v3r2 to access several systems.  I am using CA v3r2 vs. CAE because
>of lowest common denominator factors.
>
>Our shop also uses ViewNow, which is able to connect to remote AS/400s thru
>a VPN setup.  In ViewNow, I set up a session with an internal IP address
>like 192.168.x.xx and port 8045.
>
>CA v3r2, when setting up a connection, it only asks for the IP address.
>Obviously, it's not going to find a 400 at that address.  Strangely enough,
>the client (Personal Communications WorkStation Program) gives the
>opportunity to specify a port (and I see this in the session.WS file as
>well) via the Communication menu, then Configure option.  On a whim, I
>change the port number from the default 23 to 8045.  But this doesn't work;
>no connect.
>
>Is this beyond the capabilities of CA v3r2?  Or is there a tweak I missed?
>I trust CAE can do this?
>
>Dan Bale
>SAMSA, Inc.
>989-790-0507
>DBale@SAMSA.com
>   Quiquid latine dictum sit altum viditur.
>   (Whatever is said in Latin seems profound.)
>
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.