This article was previously published under Q159684
This article has been archived. It is offered "as is" and will no longer be updated.
This article will explain general configuration and usage of dial up linkswith Routing and Remote Access Service Update.
When a Routing and Remote Access Service router connects to anotherRouting and Remote Access router as a demand-dial router, both routerswill obtain an IP address for their local WAN interface from the distantrouter. To establish this two-way address assignment, the interfaces needto be configured correctly.
When adding a demand-dial interface, the username, configured from theInterface Credentials screen, must match the name of the interface thatyou will be dialing into and be a valid RAS user account on that system ordomain. If the username does not match the name of the interface, you willconnect as a client and not as demand-dial. To verify the type ofconnection, click Active Ports and Connections in the tree view and lookin the type column in the list view on both routers. The type will beclient for normal PPP clients or demand-dial for Routing and Remote AccessService routers. The router's connections must show up as demand-dial forthe routing protocols to run over the connection. The router being calledalso needs the appropriate interface credentials. The calling router willalso try to validate the router being called. This mutual authenticationcan be turned on or off from the Security tab for the demand dialinterface.
For example, you have a router in Portland and a router in Seattle. Bothsides want the ability to demand-dial the other location. You could makeone interface named PORT_SEATTLE on both routers. The username would alsobe PORT_SEATTLE for both routers. The username could be PORT_SEATTLE ofthe Portland Domain and PORT_SEATTLE of the Seattle Domain, or it could bea valid dial-in account on the local routers. In other words, even thoughthe username is the same, it is not actually the exact same account.