Member Avatar for chawk

i am student, that following a course in ICT and i have to do a project using that knowledge. i would like to do that in the computer networking field, because i planning to go ahead in computer network field and that is my expertise area.

so, i want to know from you, "what are the common problems, that facing clients (and admins), in the computer network field"?

  • 3 Contributors
  • 2 Replies
  • 374 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by goatnetworking

Dani AI

Generated

A concise, practical add‑on for ’s project request. Earlier replies by and touched on high‑level strategy and product choices; the points below focus on recurring, concrete problems admins and clients actually face, simple diagnostics, and project ideas that remain useful years later.

  • Poor documentation and inventory — missing diagrams, unlabeled ports, unknown firmware levels. Mitigation: build an inventory (device, role, config backup, last update).
  • Configuration drift and human error — mismatched VLANs, wrong ACLs, STP loops. Mitigation: keep config backups and use change review + versioning.
  • Visibility gaps — no baseline, no alerts, ad‑hoc troubleshooting. Mitigation: deploy basic monitoring (interface, CPU, latency) and collect short baselines.
  • Name resolution and DNS issues — hard to spot, breaks many services. Mitigation: replicate DNS checks in any troubleshooting runbook.
  • Performance and saturation — bursts, asymmetry, or wrong QoS settings. Mitigation: capture flows, compare to baseline, and test QoS in a controlled window.
  • Wireless/interference and physical faults — bad cables, SFP/port problems, RF overlap. Mitigation: physical checks, replace suspect links, spectrum scan for Wi‑Fi.
  • Security hygiene — expired certs, weak admin access, unmanaged remote access. Mitigation: periodic credential audit and automated patching policy.

A simple, repeatable troubleshooting workflow suitable for a project:

1) Define scope: affected hosts, time, services.
2) Verify physical/link: LEDs, cables, SFPs.
3) Verify addressing/routing: ping/traceroute; check ARP/route tables.
4) Check name resolution and policies: nslookup/dig; inspect ACLs/firewall logs.
5) Capture traffic if needed: tcpdump/wireshark; identify protocol-level failures.
6) Apply targeted fix, verify, document, and backup config.

Project suggestions: pick one problem class (visibility, config drift, DNS, wireless), produce baseline metrics, implement a monitoring or automation fix, and deliver a short runbook plus before/after evidence. Caution: always backup configs and schedule live changes during a maintenance window.

Recommended Answers

All 2 Replies

Member Avatar for JorgeM

The real answer is how to manage the network in the most cost effective manner, doing more with less. Finding IT solutions that save the business money while empowering users to do more.

Member Avatar for goatnetworking

What vendor to use for what purpose. Everybody knows Cisco, but did you know that F5 has a different feature set then the ACE or CSS load balancers? My point is, what is the best product to fit the need of the business.

The other is the wide variety of technologies all bundled up in "Networking". For example, I support Routers, Switches, Load Balancers, Firewalls, VPN Concentrator, WAN Accelerators, IP PHones, Cisco Call Manager, Voice Gateways, Wireless (Controllers with over 1000 AP's). I manage products from Cisco, Brocade, F5, Riverbed. It sounds like a lot, but it's a lot of fun and it's never dull.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.