Windows 2000 Server
You install the Routing and Remote Access service on a Windows 2000 Server computer in your network. Your network is not directly connected to the Internet and uses the private IP address range 192.168.0.0. When you use Routing and Remote Access to dial in to the server, your computer connects successfully, but you are unable to access any resources. When you try to piiig servers by using their IP addresses, you receive the following message: "Request timed out." When you run the ipconfig command, it shows that your dial-up connection has been given the IP address 169.254.75.182. What should you do to resolve the problem?
Ensure that the remote access server is able to connect to a DHCP server that has a scope for its subnet
None of above
Configure the remote access server to act as a DHCP Relay Agent
Authorize the remote access server to receive multiple addresses from a DHCP server
Configure the remote access server with the address of a DHCP server
Create a second GPO in the OU. Add the Managers group to the access control list. Allow the managers group to apply the Group Policy. Deny the Authenticated Users group permission to read and apply th
Add the Managers group to the access control list of the GPO. Deny the permission of the managers group to read and apply the Group Policy
Create a second GPO in the OU. Add the Managers group to the access control list. Allow the managers group to apply the Group Policy. Disable the Authenticated Users group permission to read and apply
Add the Managers group to the access control list of the GPO. Disable the permission of the managers group to read and apply the Group Policy
Configure a Group policy for the Domain that blocks all unsigned drivers
Do nothing, this is the default setting
Configure a Group policy for the Default Domain Controller to block all unsigned drivers
Configure the Windows 2000 file servers, Windows 2000 print servers, Windows 2000 professional computers and Windows 2000 file servers to block unsigned drivers