configuring RRAS to automatically find the default gateway to clie

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

Guest

I am trying to configure Windows 2000 server as a router (using Routing and
Remote Access Service), then configuring the Windows 2000 server and the 2000
Pro station so that the station will automatically detect its Default Gateway
(neither specifying the default gateway manually on the station, nor using
the DHCP service on the server to specify the default gateway).
Note: I know that the server needs to be sending multicast packets to the
client computer but not sure how to configure the server nor the client
 
vtmtl said:
Pro station so that the station will automatically detect its Default
Click to expand...
Gateway

Not gonna happen.
Note: I know that the server needs to be sending multicast packets to the
client computer but not sure how to configure the server nor the client
Click to expand...

Multicast isn't relevant to the first thing you asked. Also, if sending
"multicast packets",..it isn't going to be sent to "the" client,...multicast
is sent to every client.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
-----------------------------------------------------
 
I know that it can happen with the server sending IGRP packets via the RAS
service for the auto discovery of the default gateway.

Phillip Windell said:
vtmtl said:
Pro station so that the station will automatically detect its Default
Click to expand...
Gateway

Not gonna happen.
Note: I know that the server needs to be sending multicast packets to the
client computer but not sure how to configure the server nor the client
Click to expand...

Multicast isn't relevant to the first thing you asked. Also, if sending
"multicast packets",..it isn't going to be sent to "the" client,...multicast
is sent to every client.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
Click to expand...
 
vtmtl said:
I know that it can happen with the server sending IGRP packets via the RAS
service for the auto discovery of the default gateway.
Click to expand...

IGRP (Interior Gateway Routing Protocol) is used between multiple Routers to
"trade" routing information between themselves so that the routing tables in
each router remain up-to-date in a network with multiple redundant "pathes"
to the same destination.

If the network has only one router, then there is no need for IGPR.

If the network has multiple routers but only one path to each destination,
then IGRP is still not really needed, RIP would serve to purpose just fine.

None of this has anything to do with workstations and their "default
gateway" setting.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
-----------------------------------------------------
 
what about configuring the client(s) to be able to acquire the IGRP packets?
The IGRP packets contains the address of the router and should be able to be
transferred to the client's field for the default gateway.

Phillip Windell said:
vtmtl said:
I know that it can happen with the server sending IGRP packets via the RAS
service for the auto discovery of the default gateway.
Click to expand...

IGRP (Interior Gateway Routing Protocol) is used between multiple Routers to
"trade" routing information between themselves so that the routing tables in
each router remain up-to-date in a network with multiple redundant "pathes"
to the same destination.

If the network has only one router, then there is no need for IGPR.

If the network has multiple routers but only one path to each destination,
then IGRP is still not really needed, RIP would serve to purpose just fine.

None of this has anything to do with workstations and their "default
gateway" setting.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
Click to expand...
 
vtmtl said:
what about configuring the client(s) to be able to acquire the IGRP packets?
The IGRP packets contains the address of the router and should be able to be
transferred to the client's field for the default gateway.
Click to expand...

I am not sure about that. But why do you want to make things so extremely
complicated? A LAN will run prefectly fine without any routing protocols at
all. Use DHCP,..that is what it is for, that is what everybody is doing with
it. It is simple, clean, and works virtually trouble free and maintainence
free.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
-----------------------------------------------------
 
I found out how to configure this.
http://www.microsoft.com/technet/itsolutions/network/deploy/depovg/tcpip2k.mspx

ICMP Router Discovery

Windows 2000 can perform router discovery as specified in RFC 1256. Router
discovery provides an improved method of configuring and detecting default
gateways. Instead of using manually- or DHCP-configured default gateways,
hosts can dynamically discover routers on their subnet. If the primary router
fails or the network administrators change router preferences, hosts can
automatically switch to a backup router.

When a host that supports router discovery initializes, it joins the
all-systems IP multicast group (224.0.0.1), and then listens for the router
advertisements that routers send to that group. Hosts can also send
router-solicitation messages to the all-routers IP multicast address
(224.0.0.2) when an interface initializes to avoid any delay in being
configured. Windows 2000 sends a maximum of three solicitations at intervals
of approximately 600 milliseconds.

The use of router discovery is controlled by the PerformRouterDiscovery and
SolicitationAddressBCast registry parameters, and it defaults to DHCP
controlled in Windows 2000.

Setting SolicitationAddressBCast to 1 causes router solicitations to be
broadcast, instead of multicast, as described in the RFC.



Phillip Windell said:
vtmtl said:
what about configuring the client(s) to be able to acquire the IGRP packets?
The IGRP packets contains the address of the router and should be able to be
transferred to the client's field for the default gateway.
Click to expand...

I am not sure about that. But why do you want to make things so extremely
complicated? A LAN will run prefectly fine without any routing protocols at
all. Use DHCP,..that is what it is for, that is what everybody is doing with
it. It is simple, clean, and works virtually trouble free and maintainence
free.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
Click to expand...
 
Back
Top