RE: dsl dilemna

["Chris Payne" <CPayne@xxxxxxxxxxxxxxx>]

2 things, the first might just be nitpick, but 172.x.x.x is not all
valid private address it needs to be 172.16.0.0 through 172.31.255.255.
from your description of what is going on is sounds like a routing
problem on your dsl router. Packets make it as far as the router, but
then disappear. What does the routing table look like on your dsl
router?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Thursday, April 28, 2005 9:53 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: dsl dilemna

Customer has added a vpn access to local lan to get to iSeries.
Remote pc can log into vpn (Cisco client), and even ping the dsl
router's inside address 10.10.10.11
Cannot ping iSeries 10.10.10.10 or any other 10.x.x.x device. 
iSeries has a *dftroute route to the 10.10.10.11 dsl router and can 
ping it. I'm no network expert, but had someone else attempt
vpn and he says dsl router is natting user a 172.x.x.x address.
Is this the problem? We had asked the nat pool to be to 10.10.10.70 thru
90,
but Bellsouth tech gets quiet when i say "nat pool". 
btw-There is a separate router/firewall for T1 into same lan switch. 
jim 
-- 
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.