What This Category Covers
Networking tickets should separate physical/link state, IP assignment, DNS, routing, firewall policy, VLAN tagging, and application reachability. Test by IP and hostname before changing infrastructure.
First Layer to Isolate
IP layer first, then DNS, route, firewall/VLAN, and application port.
Useful Tools, Logs, and Portals
- ipconfig /all
- nslookup
- ping/tracert
- route print
- Firewall logs
- Switch/AP controller
- DHCP scopes
Before You Escalate
- Source/destination identified
- IP and hostname tests compared
- VLAN/firewall path checked
- Recent network changes reviewed
Articles in This Path
Pick the closest symptom and work from there.
Application publish rule works by IP not FQDN
Field Summary
Application publish rule works by IP not FQDN is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
- Read more about Application publish rule works by IP not FQDN
- Log in to post comments
New ISP circuit installed but outbound policy still uses old WAN
Field Summary
New ISP circuit installed but outbound policy still uses old WAN is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
Firewall HA pair syncs config but not session state
Field Summary
Firewall HA pair syncs config but not session state is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
Site to site tunnel up but only one subnet passes traffic
Field Summary
Site to site tunnel up but only one subnet passes traffic is a Firewalls & Routing ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
SSID visible but authentication fails for only one security group
Field Summary
SSID visible but authentication fails for only one security group is a Wi-Fi & Switching ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. Start with the exact sign-in attempt and policy result; password resets without log evidence often create a second problem.
Loop detected warnings after moving conference room switch
Field Summary
Loop detected warnings after moving conference room switch is a Wi-Fi & Switching ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
VoIP phones lose power after switch firmware upgrade
Field Summary
VoIP phones lose power after switch firmware upgrade is a Wi-Fi & Switching ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
Office guest Wi-Fi captive portal loops forever
Field Summary
Office guest Wi-Fi captive portal loops forever is a Wi-Fi & Switching ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
New switch stack forms but VLAN tagging is inconsistent
Field Summary
New switch stack forms but VLAN tagging is inconsistent is a Wi-Fi & Switching ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.
Wireless clients roam but lose Teams audio during handoff
Field Summary
Wireless clients roam but lose Teams audio during handoff is a Wi-Fi & Switching ticket where the visible symptom can be misleading. Network tickets should be split into link, IP assignment, DNS, route, VLAN/firewall policy, and application reachability. Green status on one layer does not prove the path works. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.