RE: (no subject)

Good question.  We just installed a new firewall this past week, so
we're still in "tweak" mode.  When I get home tonight, I'll check it
out.

Thanks for the tips!

Brian.

-----Original Message-----
From: Chris Bipes [mailto:chris.bipes@xxxxxxxxxxxxxxx] 
Sent: Thursday, November 24, 2005 3:24 PM
To: Midrange Systems Technical Discussion
Subject: (no subject)

I doubt it is a routing issue but a firewall issue.  Correct me if I am
assuming to much here.  What you are doing is connecting from the
outside to your VPN unit and then cannot connect to your AS400?  The
inside IP of the VPN is 192.168.0.20.  When you connect from the
outside, what IP is the client assigned?  For instance our VPN assigns
IP's on a different subnet than our inside network so we have a route on
the servers we want to be reached via VPN.

Client -->VPN -->Inside
Public-->public/Private-->private 
100.1.1.1 --> 28.1.1.1 --> 192.168.1.1 / 255.255.255.0
192.168.2.1 assigned to vpn client
Route on inside server = 192.168.2.0 / 255.255.255.0 ---> 192.168.1.1

Our VPN serves up a different private subnet than our inside network.
How is yours configured?


Christopher Bipes

IS Director

CrossCheck, Inc. 

707.586.0551, ext. 1102

707.585.5700  FAX

Chris.Bipes@xxxxxxxxxxxxxxx
www.Cross-Check.com



Notice of Confidentiality: This e-mail, and any attachments thereto, is
intended only for use by the addressee(s) named herein and may contain
legally privileged and/or confidential information.  If you are not the
intended recipient of this e-mail, you are hereby notified that any
dissemination, distribution or copying of this e-mail, and any
attachments thereto, is strictly prohibited.  If you have received this
e-mail in error, please immediately notify me by e-mail (by replying to
this message) or telephone (noted above) and permanently delete the
original and any copy of any e-mail and any printout thereof.  Thank you
for your cooperation with respect to this matter.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Piotrowski
Sent: Thursday, November 24, 2005 11:57 AM
To: Midrange Systems Technical Discussion
Subject: RE: TCP/IP Route Question

(Fingers hit SEND too quickly)

That explains it.

I tried to add another route as direct because for some reason our
VPN/firewall does not see our AS/400 when you log in (it's
192.168.0.20).  I wanted to add a direct route to the AS/400 to see if
that would make a difference, so that's why I was trying to add
192.168.0.141 to the route table (which is the IP of our VPN/firewall).