Your company has a main office and one branch office. You want to connect the main office to the branch office by using a site-to-site VPN connection. The main office has an ISA Server 2006 computer named ISA1. The branch office has an ISA Server 2006 computer named ISA2. The relevant portion of the network is configured as shown in the exhibit.
The main office network includes two network IDs: 192.168.1.0/24 and 192.168.2.0/24. The 192.168.1.0/24 network is directly connected to ISA1 and is configured as the default Internal network. The 192.168.2.0/24 network is connected to the 192.168.1.0/24 network by a router on the main office Internal network. You create two subnet network objects in the ISA Server Management console: one network for the 192.168.1.0/24 network and one for the 192.168.2.0/24 network.
The internal network adapter on ISA2 is on network ID 10.0.0.0/24. You create an access rule on ISA1 and on ISA2 to allow all traffic to and from the main office and branch office networks. You create an access rule on ISA1 to allow all traffic between the default Internal network and the branch office network. Users on network ID 192.168.2.0/24 report that they cannot connect to computers at the branch office.
You need to ensure that all users at the main office can connect to resources located on the branch office network.
What should you do?
A.
Add the addresses in network ID 192.168.2.0/24 to the default Internal network at the main office.
B.
Add the addresses in network ID 10.0.0.0/24 to the default Internal network at the main office.
C.
Remove the router connecting the two networks at the main office, and place both network IDs on a single Ethernet broadcast segment.
D.
On ISA2, create a subnet network object representing the 192.168.2.0/24 network. Add this network object to the list of destination computers that the branch office computers can connect to.