When To Ignore Dial-in Properties

By Author: Jessee
Total Articles: 286
Comment this article

Sometimes you'll have a need to ignore dial-in properties. You might need to do this because clients such as those using an 70-297 Exam authenticating switch or wireless connection might not understand some parts of the dial-in user account properties and therefore would disconnect a legitimate session. You can configure a remote access policy to ignore the dial-in properties by configuring the Ignore-User-Dialin-Properties attribute of the Advanced tab of the profile settings of the remote access policy. You can even choose to apply this condition for some types of connections and not for others. By setting the attribute to false, you allow dial-in to be used; by setting the attribute to true, you prevent dial-in from being used. A good example of such a use is to create two remote access policies—one for wired connections, and one for wireless. If authorized remote access user Kevin F. Browne uses a wired connection, the properties of his user account dial-in page are considered. When he uses a wireless connection, they are not.
Note Windows Server 2003 computers also ...
... have dial-in property pages in their computer accounts. Computers can be authorized to remotely connect and be authenticated as if they were users. For example, an 802.Ix Ethernet client uses EAP-TLS and an installed computer certificate to authenticate to an authenticating Ethernet switch. For more information about CCNA certification and wireless connections to Windows Server 2003 networks, see Chapter 13.

Exam Tip User accounts in a Windows NT 4.0 domain or a Windows Mixed domain functional mode domain can be configured only for the Allow, Deny, and Allow Callback options.
Assign a Static IP. A static IP address can be entered in the property pages and used by the client when accessing resources on the network.
Apply Static Routes. The static routes defined in the property pages are added to the routing table of the RRAS server when the connection is made by this user.
This page specifies choices for client IP address assignment and is where IP packet filters can be defined if desired. There are four possibilities for IP address assignment. The choices are: the access server must supply the address; the client can request an IP address; address assignment is speci?fied by the access server; or a static IP address is listed in the profile. If there is an IP address in the user account, it overrides the profile setting. IP packet filters are defined on this page and apply to remote connection traffic. Both output, which is the traffic to the client, and input, which is the traffic from client packet filters can be written. IP packet filters are not applied to security+ certification dial-on-deman