The "Router" checkbox is to configure the Routing and Remote Access service
for the router role, which includes allowing you to configure packet
filtering (the Network Interfaces node in the snap-in) and demand-dial
interfaces for multiple protocols (in the case of Windows 2000, both TCP/IP
and IPX/Windows Server 2003 Routing and Remote Access does not support IPX).
The "Enable IP Routing" check box on the IP tab selectively enables
forwarding just for TCP/IP. Because a remote access server (dial-in or
VPN-based) is performing IP forwarding, this check box is available even
even though the "Router" check box on the General tab is disabled.
"John Crowley" <(E-Mail Removed)> wrote in message
news:BFD8FFF1-C0B0-405A-B543-(E-Mail Removed)...
> This has bugged me since Windows 2000 server was released, and still seems
to be in Windows 2003, which I haven't found an explanation for.
> In the Routing and Remote Access applet, the proprties page for the
server, there is a General tab, which has a checkbox for "Router" which then
enables the "Local Area Network routing only" and "LAN and Demand-dial
routing."
> Then there is an IP tab which has an Enable IP Routing checkbox.
> For the life of me, I cannot find a good explanation of how these are
different, or the same. It seems to me they are redundant or contraditory
depending on how you set them... How can you enable IP routing if the
machine is not a router, or vice-versa (which the dialog allows)? What
effects do these checkboxes have that are the same or different?
> (Hoping for some kind of explanation in tracking down something else...)
>
|