|< Day Day Up >|| |
Your organization’s private network provides employees access to many important resources, including file servers, application servers, and intranet Web servers. These resources contain a great deal of confidential information, and you probably have taken steps to keep people outside your network from accessing them. There are many times, however, when your organization’s employees will be outside your offices and need access to these resources.
Microsoft Windows Server 2003 and previous versions of Windows server operating systems have included a component called Routing And Remote Access. Routing And Remote Access enables a server to act as a remote access server capable of connecting remote workers to your organization’s private networks. Allowing legitimate users remote access poses a risk, however, because an attacker could potentially use the remote access server to access your confidential data remotely. To minimize the risk of uninvited guests using remote access, you must first choose between dial-up and VPN remote access and then configure appropriate authentication and encryption protocols.
If you fulfilled the requirements for the previous chapters, you already have the necessary hardware and software configured. You can use the computers in the state they were in after completing the previous chapters, or your can install the software from scratch. To do the practices, examples, and lab exercises in this chapter, you must have:
A private network that is not connected to any other networks. This network should not have any production computers connected to it.
One computer with two network interface cards (NICs). On this computer, perform a Windows Server 2003, Enterprise Edition installation with default settings, and assign the computer name Computer1. Configure one NIC with the IP address 192.168.3.1, configure the other NIC with the IP address 192.168.4.1, and use the subnet mask 255.255.255.0 for both.
Add the Domain Controller role to the computer with the default settings, and specify the domain name cohowinery.com. Configure the computer to use itself as its own primary Domain Name System (DNS) server. Add the Application Server role. Raise the domain functional level to Windows Server 2003.
One computer with a single network interface card. On this computer, perform a Microsoft Windows XP Professional or Windows Server 2003 installation with default settings, and assign the name Computer2. Configure the NIC with the IP address 192.168.3.2, and connect that NIC to Computer1’s NIC with the IP address 192.168.3.1 by using a hub, switch, or crossover cable. Add the computer to the cohowinery.com domain as a member computer. Configure the computer to use Computer1 as its primary DNS server.
|< Day Day Up >|| |