Bitzu

N10-009 ยท Troubleshooting services and performance

IP configuration issues

Address pool exhaustion, wrong default gateway, wrong or duplicate IP address, wrong subnet mask.

Key points

  • 169.254.x.x: no DHCP answer, host fell back to APIPA; check the scope (exhausted pool, long leases), relay, VLAN.
  • Wrong default gateway (or outside the host's subnet): local traffic works, remote fails.
  • Wrong subnet mask: host misjudges what is local.
  • Duplicate IP: intermittent failures, conflict warnings; keep static addresses outside the scope or use reservations.
  • Start with ipconfig /all (Windows) or ip addr (Linux).

Source: https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/ipconfig

Practice questions

Single choice

A workstation shows the address 169.254.17.8. What does this indicate?

  1. It could not reach a DHCP server and self-assigned an address
  2. The DNS server is returning bad records
  3. An administrator set a static address
  4. The gateway is in a different VLAN
Show answer

Answer: A. It could not reach a DHCP server and self-assigned an address

169.254.0.0/16 is the APIPA range a client assigns itself when no DHCP server answers. It does not mean DNS is down or that the address was statically set.

Select all that apply

New devices keep ending up with 169.254.x.x addresses because the scope is full. Which actions relieve the pool?

  1. Shorten the lease time on the guest scope
  2. Enlarge the address range of the scope
  3. Change the DNS server address
  4. Make clients rely on APIPA
  5. Delete reservations for retired devices
Show answer

Answer: A. Shorten the lease time on the guest scope, B. Enlarge the address range of the scope, E. Delete reservations for retired devices

A larger range adds addresses, a shorter lease on a churning guest scope returns them sooner, and removing stale reservations frees them. Changing the DNS server or enabling APIPA does not add leases.

True or false

A host whose default gateway is outside its own subnet can still reach remote networks normally.

Show answer

Answer: False

False. A host sends remote traffic to the gateway at Layer 2, so the gateway must be reachable directly inside the host's own subnet.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More N10-009 topics in this module