NAT gateway setup problem

[flekso]

I've found this netsh script that allows me to install NAT on a WinXP
machine (undocummented feature):

netsh routing ip nat install
netsh routing ip nat add interface "external" full
netsh routing ip nat add interface "internal" private

....but now i have another problem, mainly because my internet
connection is based on dial-up PPPoE aDSL, so i have two icons in
network connections, one that represents a WAN miniport(this one i
click to connect), and the other that represents NIC that connects to
my aDSL modem.
The problem is my WAN miniport(PPPoE) gets assigned with the external
IP, and the NIC gets an automatic private address(whatever that means)
in the 169.254 range, but netsh won't accept the PPPoE as an interface(says
it not a real interface),
so i must use the one that's detected as local(at least by netlimiter)...

Any clues ? Maybe i can fool the netsh into thinking that PPPoE is a real
NIC ? Why are there two icons anyway ?

Thanks.

 

[Dave]

isn't that just a hard way to setup 'internet connection sharing'. ics does
nat for the internal network as well as other services needed to share an
internet connection. try reading up in the help on 'ics' or 'internet
connection sharing' and see if the gui that sets it up doesn't do a better
job than a couple netsh commands.

 

[Bill Grant]

I would agree with that. PPPoE is hard going, even with RRAS and a
server OS.

 

[flekso]

Yup, but i would like to install a dhcp & dns services on this gateway
so ICS is likely to cause more pain than worth...

 

[Dave]

sounds like you already have plenty of pain, so carry on if you must. but
if you don't like how ics handles dhcp and dns you may want to look at one
of the third party connection sharing solutions to see if they provide you
the control you want.

 

[flekso]

Could you share the version with RRAS and server, that is my actual
destination setup (XP+VMware is my test machine), plus one difference:
there's an USB modem with PPPoE (yet more complication), so i can't even
imagine what the second icon in network connections represents...