"v_iron" <(E-Mail Removed)> wrote in message news:f0pi0r$s0q$(E-Mail Removed)...
> Robert L (MS-MVP) :
>> If the RRAS has an issue to access the DHCP for releasing the IP, it will
>> assign 169.254 IP. This search result may help,
> I change DHCP to fixed addresses so server now have 192.168.1.10 and
> client 192.168.2.11 but this is not issue.
>
>> routing issues on vpnResolutions: 1) if you have two NICs in the VPN
>> server, you may need to enable IP Routing. To do this, go to the RRAS>the
>> Properties of the server>IP, ...
>> http://www.chicagotech.net/routingissuesonvpn.htm
> Here is no rras.msc in Windows XP Pro. I set HKEY_LOCAL_MACHINE
> \SYSTEM\CurrentControlSet\Services\Tcpip\Parameter s "IPEnableRouter" to 1
> but no result.
> And I found some peoples have the same problem as me but nobody answers
> that to do in this situation.
>
> Additional questions: can VPN route traffic without "Default gateway" set
> in parameters? I mean this place (see my first message):
> -->8------------------------------------------------------
> ...
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 169.254.55.208
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . : <------
> -->8------------------------------------------------------
No, you cannot route between subnets without a default gateway set. And
with an APIPA address (ie 169.254.x.y) you will not get a default gateway
address. APIPA is a fallback for people who accidentally leave the network
config set to automatic but do not have a DHCP server. APIPA will give them
local networking by default.
The basic problem is that your XPPro "server" is not getting addresses
from DHCP to use for the remote connection, forcing it to use APIPA
addresses (which won't route). If you cannot find out why this is not
working, delete the incoming connection and set it up again from the New
Connection wizard. Instead of using DHCP, set up a pool of addresses to use
(in the TCP/IP settings). The pool must have at least two IP addresses in it
(one for the remote client and one for the server itself). Use addresses in
the same IP subnet as the LAN machines are using. You could use IP addresses
from the high end of your DHCP scope, like 192.168.1.241 to 192.168.1.246 .
If the client gets a 192.168.1.x IP from RAS it will also get the same
IP address as its gateway address. The remote client can then see the
machines on the LAN because all 192.168.1.x traffic goes across the PPP link
and is delivered on the LAN. The server does proxy ARP on the LAN to receive
packets addressed to the remote client and forwards them across the PPP
link. It will never work with APIPA addresses.