Quick troubleshooting view
Some applications pass via IPv6 while IPv4 connectivity is broken.
- DHCPv4
- NAT IPv4
- default route
- Limit the impact.
- Collecting Evidence.
- Test the the simplest hypothesis.
- Correct the confirmed cause rather than the symptom.
- Document the change and result.
- Establish supervision if the defect can recur.
Contextual technician plan
Identify whether a position, service or entire site is affected.
ipconfig /all.The local IP configuration is coherent; test the next network layer.
Keep the message accurate, time, and associated logs.
“Collecting Evidence.” should produce an observation that clearly confirms or rules out “NAT IPv4”.
If the observation is normal, lower “NAT IPv4” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “NAT IPv4” first. Related action: Document the change and result.
Compare with equipment or functional path.
“Test the the simplest hypothesis.” should produce an observation that clearly confirms or rules out “default route”.
If the observation is normal, lower “default route” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “default route” first. Related action: Establish supervision if the defect can recur.
Apply only one change at a time and retester.
“Correct and validate.” should produce an observation that clearly confirms or rules out the targeted hypothesis.
If the observation is normal and continue with the next distinct check.
If the observation is abnormal, keep the evidence before broader changes.
Repeat the same validation test after the correction and confirm the original symptom is gone. Validate stability before closing the incident.
Before changing configuration, record the current value and a way back.
Cadader if the impact extends, if the data are at risk or if the cause involves irreversible modification.
Some applications pass via IPv6 while IPv4 connectivity is broken.
Causes probables
- DHCPv4
- NAT IPv4
- default route
Diagnostic étape par étape
- 1
Limit the impact.
Identify whether a position, service or entire site is affected.
- 2
Collecting Evidence.
Keep the message accurate, time, and associated logs.
- 3
Test the the simplest hypothesis.
Compare with equipment or functional path.
- 4
Correct and validate.
Apply only one change at a time and retester.
Commands utiles
ipconfig /all.Solutions possibles
- Correct the confirmed cause rather than the symptom.
- Document the change and result.
- Establish supervision if the defect can recur.
Cadader if the impact extends, if the data are at risk or if the cause involves irreversible modification.