Troubleshooting / symptôme

A post receives an address 169.254.x.x

The post n, obtained no DHCP lease and switch to APIPA tying.

⌚ About 3 min read
View my favorites
Real-world problem · V2

Quick troubleshooting view

What you are seeing

The post n, obtained no DHCP lease and switch to APIPA tying.

Likely causes
  1. DHCP inaccessible.:.
  2. Invalid VLAN.
  3. unstable network link.
First checks
  1. Control ipconfig.
  2. Test the VLAN.
  3. Renewing the lease.
Recommended actions
  1. Correct DHCP relay or scope.
  2. Correct VLAN/port.
  3. Repairing Physical Connectivity.
Start Symptom → Cause →
& DHCP Network.Intermediate.

The post n, obtained no DHCP lease and switch to APIPA tying.

Important: relevez toujours le message d’erreur exact et l’heure du problème avant de modifier la configuration. Les actions proposées doivent être adaptées à votre environnement.

Causes probables

  • DHCP inaccessible.:.
  • Invalid VLAN.
  • unstable network link.

Diagnostic étape par étape

  1. 1

    Control ipconfig.

    Check the address, gateway and DHCP server.

  2. 2

    Test the VLAN.

    Compare with a functional position on the same port/SSID.

  3. 3

    Renewing the lease.

    Release and renew after network correction.

Commands utiles

ipconfig /all.
ipconfig / ipconfig /renew.

Solutions possibles

  • Correct DHCP relay or scope.
  • Correct VLAN/port.
  • Repairing Physical Connectivity.
Quand escalader ?

Crack if multiple VLANs are affected or the DHCP server is unavailable.

♡ 0