Understanding Automatic Private IP Addressing APIPA Ymz
12. You are the systems administrator for a small network of fewer than 10 users on a single network segment, which is configured for peer-to-peer network resource sharing.You are using Windows XP and Windows 2000 on all of your client desktops and you decide to avoid the hassle of installing DHCP or manually configuring static IP addresses by using APIPA.You are using two file servers, both running Windows Server 2003, which also have the ability to use APIPA. Everything is running smoothly and you applaud yourself for implementing such an easy alternative for IP distribution. As your small network grows, however, you start to see your single segment network begin to outgrow itself.You decide to add another segment to your network, and you do so, setting up a network router.You add five new employees and plug their computers into the switch that is attached to the new subnet. All these employees' computers are configured to use APIPA and are able to communicate with each other immediately. However, when the new users try to access anything on the network servers, they are unable to connect. They are also unable to connect to any existing shares on the original network. What have you overlooked in your use of APIPA as an IP alternative?
A. APIPA works only if you have fewer than 10 workstations.
B. APIPA has not been configured properly on the new workstations.
C. The router is not able to forward BOOTP/DHCP broadcasts.
D. APIPA cannot be routed.
Post a comment