Re: dsl dilemna

[ron_adams@xxxxxxxxxxxxxx]

Sounds like you have some conflicting routes set up.

Try a 'tracert' to see if you can determine the path it's following. 
Sometimes this will help you see where it's going.

Ron Adams





"Jim Franz" <franz400@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/28/2005 08:53 AM
Please respond to Midrange Systems Technical Discussion

 
        To:     <MIDRANGE-L@xxxxxxxxxxxx>
        cc: 
        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.