Updated: January 21, 2005
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Routing and Remote Access also includes support for demand-dial routing (also known as dial-on-demand routing). By using a demand-dial interface, the router can initiate a connection to a remote site when the packet to be routed is received by the router. The connection becomes active only when data is sent to the remote site. When no data has been sent over the link for a specified amount of time, the link is disconnected. By making a demand-dial connection, you can use existing dial-up telephone lines instead of leased lines for low-traffic situations. Demand-dial routing can significantly reduce your connection costs.
Routing and Remote Access also includes support for demand-dial filters and dial-out hours.
You can use demand-dial filters to specify what types of traffic are allowed to create the connection. Demand-dial filters are separate from IP packet filters, which you configure to specify what traffic is allowed into and out of an interface once the connection is made. For more information about configuring demand-dial filters, see Configure demand-dial filters.
You can set dial-out hours to specify the hours that a router is allowed to dial out to make demand-dial connections. For more information about configuring dial-out hours, see Configure dial-out hours.
You can configure when the router accepts incoming connections through remote access policies. For more information, see Introduction to remote access policies.
For more information about demand-dial routing and an example, see Understanding Demand-Dial Routing.