NAT gateway setup problem

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.

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.

"flekso" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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.
>
>

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

"Dave" <(E-Mail Removed)> wrote in message
news:%23%(E-Mail Removed)...
> 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.
>
> "flekso" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> 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.
>>
>>
>
>

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" <(E-Mail Removed)> wrote in message news:<##(E-Mail Removed)>...
> 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.
>
> "flekso" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > 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.
> >
> >

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" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> 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" <(E-Mail Removed)> wrote in message
news:<##(E-Mail Removed)>...
> > 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.
> >
> > "flekso" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > 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.
> > >
> > >

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...

"Bill Grant" <not.available@online> je napisao u poruci interesnoj
grupi:ez%(E-Mail Removed)...
> I would agree with that. PPPoE is hard going, even with RRAS and a
> server OS.
>
> "Dave" <(E-Mail Removed)> wrote in message
> news:%23%(E-Mail Removed)...
>> 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.
>>
>> "flekso" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> 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.
>>>
>>>
>>
>>
>
>

The first icon is your 'ethernet' connection with the ISP. Usually, with
Ethernet, once you're plugged in (with a DHCP assigned address) you're
online. However, DSL uses Point To Point Protocol to authenticate and
encapsulate becuase of the phone line setup (the long distances
decrepidation etc). So your second icon creates a PPP scripted tunnel
through the Ethernet connection. PPP over Ethernet. Two icons. You could
always get yourself a DSL adapter with an Ethernet port on it. In that
situation, the adapter does all the dial up etc. internally. So you have a
little router doing all you're NAT for you. Once you use USB, you will have
to use the manufacturers drivers and their two icon system.

XP's ICS is perfect for you unless you want more than 250 hosts on your
network. It supports DHCP & DNS - but I don't think you can configure them.

I have set up two 2000 servers with RRAS and Dial up using USB ADSL adapters
(I hate them) and they work pretty good. 2000 sees them as a Dial Up
connection. (you can ignore the Superfluous-third-nipple-of
a-dodgey-Ethernet connection in 2000 RRAS. Just use your real internal card
as Internal and set the Dial Up connection as your dial up. Been a while,
but I think you have to go in and add it as a connection or adapter or
something in RRAS.

Blah blah blah.

"Steve Ireland" <Sandy-deleteme-(E-Mail Removed)> je napisao u poruci
interesnoj grupi:%(E-Mail Removed)...
> The first icon is your 'ethernet' connection with the ISP. Usually, with
> Ethernet, once you're plugged in (with a DHCP assigned address) you're
> online. However, DSL uses Point To Point Protocol to authenticate and
> encapsulate becuase of the phone line setup (the long distances
> decrepidation etc). So your second icon creates a PPP scripted tunnel
> through the Ethernet connection. PPP over Ethernet. Two icons. You could
> always get yourself a DSL adapter with an Ethernet port on it. In that
> situation, the adapter does all the dial up etc. internally. So you have a
> little router doing all you're NAT for you. Once you use USB, you will
> have to use the manufacturers drivers and their two icon system.
>

But I have an ethernet DSL adapter (at home), and two icons...?

> XP's ICS is perfect for you unless you want more than 250 hosts on your
> network. It supports DHCP & DNS - but I don't think you can configure
> them.
>
> I have set up two 2000 servers with RRAS and Dial up using USB ADSL
> adapters (I hate them) and they work pretty good. 2000 sees them as a Dial
> Up connection. (you can ignore the Superfluous-third-nipple-of
> a-dodgey-Ethernet connection in 2000 RRAS. Just use your real internal
> card as Internal and set the Dial Up connection as your dial up. Been a
> while, but I think you have to go in and add it as a connection or adapter
> or something in RRAS.
>

But I don't have the option to select my WAN miniport connection(Dial up),
only the internal one.

> Blah blah blah.

Don't hold out on me maan..