You are a desktop administrator for ABC.com. Your organization is made up of three sites, two of
which are remote offices and one is the company headquarters. The two remote locations are
made up of four subnetworks each, interconnected internally by layer 2 switches and connected to
one another and headquarters by routers. The main company headquarters consists of eight
subnets interconnected internally by layer 3 switches.
The client systems on your network are running a number of operating systems including Windows
98, 2000, XP, and Server 2003. There are two WINS servers and two DNS servers local to each
subnet, and the clients are always configured to use those servers for name resolution only.
Recently, new server hardware was installed for SRV007 to replace a legacy system, and there
have been reported issues with incoming connectivity to the server. The serve itself seems to be
able to initiate connections to systems fine. You attempt to PING SRV007.ABC.com, and you
receive the following error:
Pinging SRV007.ABC.com [149.88.72.19] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for PING SRV007.ABC.com:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
You then log in to SRV007.ABC.com and run ipconfig and review the output
Ethernet adapter Wireless Connection:
Connection-specific DNS Suffix .ABC.com
IP Address . . . . . . . . . . . . : 149.88.72.91
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 149.88.72.1
What are the most likely reasons that this system cannot be connected to, but the system itself
can make outbound initiating connections? Each answer presents a possible solution. Select the
two best answers.
A.
The server’s IP address is not assigned correctly.
B.
The default gateway is incorrect.
C.
The IP address entry for the DNS server is incorrect.
D.
The subnet mask is invalid for this subnet
E.
Routing for the network is inconsistent or beginning to fail.