No subject

ipconfig /all
....
stuff deleted
....
Ethernet adapter E100B1:

        Description . . . . . . . . : Intel EExpress PRO/100B PCI LAN
Adapter
        Physical Address. . . . . . : 00-A0-C9-0A-FC-3E
        DHCP Enabled. . . . . . . . : No
        IP Address. . . . . . . . . : 192.168.9.2
        Subnet Mask . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . : 192.168.9.1
        Primary WINS Server . . . . : 192.168.9.2
        Secondary WINS Server . . . : 192.168.9.2

PPP adapter NdisWan5:

        Description . . . . . . . . : NdisWan Adapter
        Physical Address. . . . . . : 00-00-00-00-00-00
        DHCP Enabled. . . . . . . . : No
        IP Address. . . . . . . . . : 192.168.9.15
        Subnet Mask . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . :

C:\>

NOTE: MS ipconfig does not show the ip address of the endpoint, just the
"localip" equivelent. Using RAS manager, I was able to determine that
192.168.9.16 was handed out from the DHCP scope during my test. BTW: I wish
PopTop/PPPD could be configured to use a DHCP scope.

Now from the same W2K desktop...
C:\>tracert -d 192.168.9.16

Tracing route to 192.168.9.16 over a maximum of 30 hops

  1   <10 ms   <10 ms   <10 ms  192.168.9.2
  2   201 ms   210 ms   210 ms  192.168.9.16

Trace complete.

C:\>

Notice that each time, the ip address  of the ethernet device that is listed
as the proxyarp for the VPN answers the arp request (as it should). Thus
packets are first routed to the ethernet interface of the PPTP server and
then routed to the appropiate "virtual" PPTP interface to be encapsulated
and then routed through the tunnel.

Steve Cowles