RAS: Getting Beyond The Local Subnet

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I've gotten the RRAS service running on XPE. But when I dial in, I can only access the local subnet of the XPE machine. The XPE machine itself has no trouble reaching its default gateway and beyond. But the machine dialing in cannot get beyond the subnet

On the dialing PC, I've tracert'ed each ping, and they all are going to the dialed-up XPE machine (as they ought) and not to some other interface (the local Ethernet is disconnected). The tracert for beyond-the-subnet addresses times out after hitting the dialed-up XPE machine. The tracert for within-the-subnet addresses succeeds, even resolving to a valid machine name

I cannot find a setting that tells the XPE machine to use the known default gateway to resolve pings coming in from the RAS interface

What is up, here
 
Theophilus,

Assuming you included "Dial-up Server for Windows" component (otherwise, you
wouldn't get RRAS running), can you check if "Network Routing" component is
also included?
Also, including these components may help: "Routing Common Files", "Routing
Table Library".

KM
I've gotten the RRAS service running on XPE. But when I dial in, I can
Click to expand...
only access the local subnet of the XPE machine. The XPE machine itself has
no trouble reaching its default gateway and beyond. But the machine dialing
in cannot get beyond the subnet.
On the dialing PC, I've tracert'ed each ping, and they all are going to
Click to expand...
the dialed-up XPE machine (as they ought) and not to some other interface
(the local Ethernet is disconnected). The tracert for beyond-the-subnet
addresses times out after hitting the dialed-up XPE machine. The tracert for
within-the-subnet addresses succeeds, even resolving to a valid machine
name.
I cannot find a setting that tells the XPE machine to use the known
Click to expand...
default gateway to resolve pings coming in from the RAS interface.
 
The image has all of those components. Any other ideas? Any resources out there (or on Microsoft's site) that might shed light on why it doesn't work as it should

----- KM wrote: ----
Assuming you included "Dial-up Server for Windows" component (otherwise, yo
wouldn't get RRAS running), can you check if "Network Routing" component i
also included
Also, including these components may help: "Routing Common Files", "Routin
Table Library"
 
Theophilus,

You may search in this NG archive.

E.g., make sure you've got all the components mentioned here:
http://groups.google.com/[email protected]&rnum=7

Also, check out "Dial-up Server for Windows" registry data section. Maybe something under
[HKLM\SYSTEM\CurrentControlSet\Services\RemoteAccess\RoutingTableManager] you can reset or modify.

If you got it working under XP Pro, you may dial-in with Regmon running to see what registry entries are accessed. Then you can
always find the missing components that hold the registry.

--
Regards,
KM
The image has all of those components. Any other ideas? Any resources out there (or on Microsoft's site) that might shed light on
Click to expand...
why it doesn't work as it should?
 
Back
Top