• Chapter 1. Installing and Configuring Windows Server 2003
  • software development Company Server 2003
  • Chapter 1. Installing and Configuring Windows Server 2003
  • New Features in Windows Server 2003
  • Best Practices
  • Moving Forward
  • Version Comparisons
  • Hardware Recommendations
  • Installation Checklist
  • Functional Overview of Windows Server 2003 Setup
  • Installing Windows Server 2003
  • Post Setup Configurations
  • Functional Description of the Windows Server 2003 Boot Process
  • Correcting Common Setup Problems
  • Chapter 2. Performing Upgrades and Automated Installations
  • New Features in Windows Server 2003
  • NT4 Upgrade Functional Overview
  • Upgrading an NT4 or Windows 2000 Server
  • Automating Windows Server 2003 Deployments
  • Moving Forward
  • Chapter 3. Adding Hardware
  • New Features in Windows Server 2003
  • Functional Description of Windows Server 2003 Architecture
  • Overview of Windows Server 2003 Plug and Play
  • Installing and Configuring Devices
  • Troubleshooting New Devices
  • Moving Forward
  • Chapter 4. Managing NetBIOS Name Resolution
  • New Features in Windows Server 2003
  • Moving Forward
  • Overview of Windows Server 2003 Networking
  • Name Resolution and Network Services
  • Network Diagnostic Utilities
  • Resolving NetBIOS Names Using Broadcasts
  • Resolving NetBIOS Names Using Lmhosts
  • Resolving NetBIOS Names Using WINS
  • Managing WINS
  • Disabling NetBIOS-over-TCP/IP Name Resolution
  • Chapter 5. Managing DNS
  • New Features in Windows Server 2003
  • Configuring a Caching-Only Server
  • Configuring a DNS Server to Use a Forwarder
  • Managing Dynamic DNS
  • Configuring Advanced DNS Server Parameters
  • Examining Zones with Nslookup
  • Command-Line Management of DNS
  • Configuring DHCP to Support DNS
  • Moving Forward
  • Overview of DNS Domain Structure
  • Functional Description of DNS Query Handling
  • Designing DNS Domains
  • Active Directory Integration
  • Configuring DNS Clients
  • Installing and Configuring DNS Servers
  • Configuring Secondary DNS Servers
  • Integrating DNS Zones into Active Directory
  • Chapter 6. Understanding Active Directory Services
  • New Features in Windows Server 2003
  • Active Directory Support Files
  • Active Directory Utilities
  • Bulk Imports and Exports
  • Moving Forward
  • Limitations of Classic NT Security
  • Directory Service Components
  • Brief History of Directory Services
  • X.500 Overview
  • LDAP Information Model
  • LDAP Namespace Structure
  • Active Directory Namespace Structure
  • Active Directory Schema
  • Chapter 7. Managing Active Directory Replication
  • New Features in Windows Server 2003
  • Replication Overview
  • Detailed Replication Transaction Descriptions
  • Designing Site Architectures
  • Configuring Inter-site Replication
  • Controlling Replication Parameters
  • Special Replication Operations
  • Troubleshooting Replication Problems
  • Moving Forward
  • Chapter 8. Designing Windows Server 2003 Domains
  • New Features in Windows Server 2003
  • Design Objectives
  • DNS and Active Directory Namespaces
  • Domain Design Strategies
  • Strategies for OU Design
  • Flexible Single Master Operations
  • Domain Controller Placement
  • Moving Forward
  • Chapter 9. Deploying Windows Server 2003 Domains
  • New Features in Windows Server 2003
  • Preparing for an NT Domain Upgrade
  • In-Place Upgrade of an NT4 Domain
  • In-Place Upgrade of a Windows 2000 Forest
  • Migrating from NT and Windows 2000 Domains to Windows Server 2003
  • Additional Domain Operations
  • Moving Forward
  • Chapter 10. Active Directory Maintenance
  • New Features in Windows Server 2003
  • Loss of a DNS Server
  • Loss of a Domain Controller
  • Loss of Key Replication Components
  • Backing Up the Directory
  • Performing Directory Maintenance
  • Moving Forward
  • Chapter 11. Understanding Network Access Security and Kerberos
  • New Features in Windows Server 2003
  • Windows Server 2003 Security Architecture
  • Security Components
  • Password Security
  • Authentication
  • Analysis of Kerberos Transactions
  • MITv5 Kerberos Interoperability
  • Security Auditing
  • Moving Forward
  • Chapter 12. Managing Group Policies
  • New Features in Windows Server 2003
  • Group Policy Operational Overview
  • Managing Individual Group Policy Types
  • Moving Forward
  • Chapter 13. Managing Active Directory Security
  • New Features in Windows Server 2003
  • Overview of Active Directory Security
  • Using Groups to Manage Active Directory Objects
  • Service Accounts
  • Using the Secondary Logon Service and RunAs
  • Using WMI for Active Directory Event Notification
  • Moving Forward
  • Chapter 14. Configuring Data Storage
  • New Features in Windows Server 2003
  • Functional Description of Windows Server 2003 Data Storage
  • Performing Disk Operations on IA32 Systems
  • Recovering Failed Fault Tolerant Disks
  • Working with GPT Disks
  • Moving Forward
  • Chapter 15. Managing File Systems
  • New Features in Windows Server 2003
  • Overview of Windows Server 2003 File Systems
  • NTFS Attributes
  • Link Tracking Service
  • Reparse Points
  • File System Recovery and Fault Tolerance
  • Quotas
  • File System Operations
  • Moving Forward
  • Chapter 16. Managing Shared Resources
  • New Features in Windows Server 2003
  • Functional Description of Windows Resource Sharing
  • Configuring File Sharing
  • Connecting to Shared Folders
  • Resource Sharing Using the Distributed File System (Dfs)
  • Printer Sharing
  • Configuring Windows Server 2003 Clients to Print
  • Managing Print Services
  • Moving Forward
  • Chapter 17. Managing File Encryption
  • New Features in Windows Server 2003
  • File Encryption Functional Description
  • Certificate Management
  • Encrypted File Recovery
  • Encrypting Server-Based Files
  • EFS File Transactions and WebDAV
  • Special EFS Guidelines
  • EFS Procedures
  • Moving Forward
  • Chapter 18. Managing a Public Key Infrastructure
  • New Features in Windows Server 2003
  • Moving Forward
  • PKI Goals
  • Cryptographic Elements in Windows Server 2003
  • Public/Private Key Services
  • Certificates
  • Certification Authorities
  • Certificate Enrollment
  • Key Archival and Recovery
  • Command-Line PKI Tools
  • Chapter 19. Managing the User Operating Environment
  • New Features in Windows Server 2003
  • Side-by-Side Assemblies
  • User State Migration
  • Managing Folder Redirection
  • Creating and Managing Home Directories
  • Managing Offline Files
  • Managing Servers via Remote Desktop
  • Moving Forward
  • Chapter 20. Managing Remote Access and Internet Routing
  • New Features in Windows Server 2003
  • Configuring a Network Bridge
  • Configuring Virtual Private Network Connections
  • Configuring Internet Authentication Services (IAS)
  • Moving Forward
  • Functional Description of WAN Device Support
  • PPP Authentication
  • NT4 RAS Servers and Active Directory Domains
  • Deploying Smart Cards for Remote Access
  • Installing and Configuring Modems
  • Configuring a Remote Access Server
  • Configuring a Demand-Dial Router
  • Configuring an Internet Gateway Using NAT
  • Chapter 21. Recovering from System Failures
  • New Features in Windows Server 2003
  • Functional Description Ntbackup
  • Backup and Restore Operations
  • Recovering from Blue Screen Stops
  • Using Emergency Management Services (EMS)
  • Using Safe Mode
  • Restoring Functionality with the Last Known Good Configuration
  • Recovery Console
  • Moving Forward
  • Who Should Read This Book
  • Who This Book Is Not For
  • Conventions
  • Acknowledgments
  • About the Author
  • About the Technical Reviewers
  • Index
  • Index A
  • Index B
  • Index C
  • Index D
  • Index E
  • Index F
  • Index G
  • Index H
  • Index I
  • Index J
  • Index K
  • Index L
  • Index M
  • Index N
  • Index O
  • Index P
  • Index Q
  • Index R
  • Index S
  • Index SYMBOL
  • Index T
  • Index U
  • Index V
  • Index W
  • Index X
  • Index Z
  • Preface
  • Previous Section Next Section

    Configuring Internet Authentication Services (IAS)

    Windows Server 2003 IAS is fully compatible with Windows 2000, so you can mix and match components as you upgrade your system.

    If you have an existing third-party RADIUS implementation, you need to check the UDP ports used by the RRAS servers and the RADIUS servers. The current RADIUS standard uses UDP port 1812 for authentication and UDP port 1813 for accounting. Older RADIUS implementations used port 1645 for authentication and 1646 for accounting. If you have existing RADIUS servers or network access servers, they may use the old port number. You can configure IAS to use the old port number if the port conflict does not impact your current operations.

    A server meeting the minimum memory and CPU requirements for Windows Server 2003 can handle tens of thousands of users. Ordinarily, you should install IAS on a domain controller. This eliminates any network delays in the transactions between the IAS service and Active Directory. This is not a requirement, however. IAS can process a large number of authentication requests per second regardless of whether it is running on a domain controller or as a standalone server. A Global Catalog (GC) server should be available in the same site as the IAS server.

    Installing IAS

    When you've chosen the server to act as the IAS server, install the IAS service using the Add or Remove Programs applet in Control Panel. There is no need to restart. After the service is running, you can configure logging and remote access policies, register the server with Active Directory so it can perform authentication transactions, and configure it to accept RADIUS requests from the RRAS server.

    Configuring IAS Logging and Remote Access Policies

    Figure 20.44 shows the default configuration of the IAS management console, Ias.msc. This console is listed under ADMINISTRATIVE TOOLS in the START menu.

    Figure 20.44. IAS management console.


    The RADIUS Clients folder is used to configure relationships between the IAS server and RRAS servers. This is covered in the next section.

    The Remote Access Logging folder contains the configuration interface for the RADIUS accounting feature. This takes the form of a Local File icon. The log file controlled by the accounting feature is stored under \Windows\System32\Logfiles. The configuration settings for the logging feature are exposed in the Properties window.

    Ordinarily, you would want to select all logging options. This ensures that you have a record if someone abuses her dial-up privileges or if an exploit occurs. The IAS log file can grow fairly large. The Local File tab has an option for changing the file's location and for creating new logs periodically, such as every day or week or month depending on the number of users and the size of the logs.

    When it comes to configuring remote access policies, you may be taken back a little by the large number of configuration possibilities in RADIUS. The standard was designed for ISPs that handle millions of users and need lots and lots of policies.

    Under normal circumstances, you only need a policy that grants dial-in access to users. This policy is created by default and resides in the Remote Access Policies folder.

    The default setting for this policy is to Deny Remote Access Permission. Change this to Grant when you are ready to permit dial-in connections. Before this policy takes effect, though, the user account in Active Directory must be configured to use remote access policies. This option is only available in Native.

    Registering an IAS Server with Active Directory

    An IAS server cannot use Active Directory to authenticate users until the IAS service has been "registered" in Active Directory. This registration consists of adding the computer account for the IAS server into the RAS and IAS Servers group.

    You can add the IAS server to the RAS and IAS Servers group manually, but you may find it more convenient to use the server registration feature in the IAS console. This only adds the server into the RAS and IAS Servers group in its own domain. If you have IAS servers in several domains and users need to cross-authenticate, you must manually add the IAS servers to the RAS and IAS Servers groups in all domains. Use the steps in Procedure 20.17 to register an IAS server in Active Directory.

    Procedure 20.17 Registering an IAS Server with Active Directory

    1. Right-click the Internet Authentication Service icon and select REGISTER SERVICE IN ACTIVE DIRECTORY from the flyout menu.

    2. A message appears notifying you that the computers that are running IAS must be authorized to read users' dial-in properties and prompting you to confirm that you want to do this. Click OK to confirm.

    3. A notice appears informing you that the server has been registered. You are also reminded that it must be added to the RAS and IAS Servers group in any trusted domains to authenticate users from those domains.

    At this point, the IAS server is ready to process authentications. Now, configure the RRAS server to be a client of the IAS server.

    Configuring IAS and RRAS to Support RADIUS Authentication

    Before an IAS server will accept RADIUS authentication requests from an RRAS server, there must be a trust relationship between servers. Like a classic NT trust, this trust has a secret password that the two machines share. This permits the IAS server to validate the identity of the RRAS server to prevent man-in-the-middle exploits. To configure an RRAS server as an IAS client, follow Procedure 20.18.

    Procedure 20.18 Configuring an RRAS Server as an IAS Client

    1. In the IAS console, right-click the Clients icon and select ADD CLIENT. The Add Client window opens.

    2. Enter the name of the RRAS server in the Friendly Name field. (This is used only for display.) The only available protocol is RADIUS.

    3. Click Next. The Client Information window opens. Under Client Address, enter the fully qualified DNS name or IP address of the RRAS server.

    4. Under Client-Vendor, select Microsoft. This tells the IAS server to use a Windows domain controller for handling incoming RADIUS authentication requests.

    5. Under Shared Secret, enter a password that the IAS and RRAS servers will share. This password is not changed dynamically, so make sure it is long and complex to prevent someone from setting up an RRAS server at the same IP address to spoof authentication requests.

    6. Click Next to save the changes.

    Now, configure the RRAS server to use RADIUS and point it at the IAS server by following Procedure 20.19.

    Procedure 20.19 Configuring RRAS to Use RADIUS Authentication

    1. In the Routing and Remote Access console, open the Properties window for the server icon.

    2. Select the Security tab.

    3. Under Authentication Provider and Accounting Provider, select the RADIUS options.

    4. Next to the Authentication Provider field, click Configure to open the RADIUS Authentication window. This holds a list of the RADIUS servers that will be used by this RRAS server.

    5. Click Add. The Add RADIUS Server window opens.

    6. Under Server Name, enter the fully qualified DNS name or IP address of the IAS server.

    7. Next to the Secret field, click Change to open the Change Secret window.

    8. Enter the password you entered in the client configuration at the IAS server and click OK.

    9. Click OK to add the IAS server to the list of RADIUS servers. The Initial Score column shows the default score of 30. The RRAS server will change this score based on how quickly it gets responses back from the RADIUS servers. There is seldom a need to set this value manually.

    10. Perform the same actions for the Accounting Provider.

    11. Stop and start the RRAS service to initialize the new providers.

    At this point, the RRAS server is ready to accept client connections. You can test the configuration by making a standard dial-in connection using a domain account. The RRAS server will authenticate using the domain credentials supplied by the IAS server.

      Previous Section Next Section