Connect, configure & troubleshoot / TWA · Enugu

Network Engineering & Administration:
understand the path between devices.

When a service cannot be reached, the useful question is where communication stops. Explore addressing, network services, configuration and a diagnosis that another person can follow.

Follow the communication questions

  1. Resolve a name
  2. Reach the network
  3. Route as needed
  4. Reach the service

This simplified path explains roles; actual networks and protocols can add other components.

The network is more than the Wi-Fi signal

A device can be connected to a local wireless network while a service remains unavailable. Local connectivity, name resolution, routing and the destination application are different parts of the question. Naming the part you have actually checked helps avoid blaming the wrong system.

Cisco’s networking explanation distinguishes switches connecting devices within networks and routers connecting networks. DNS is a separate service that helps resolve names to addresses. These roles make a better starting point than memorising a diagram with no explanation of what its arrows mean.

The TWA practice studio / Guided first steps

A website works by number, but not by name.

A workplace guide will not open by its name. The laptop can still reach other parts of the network by their numerical addresses.

Your role: Compare checks at different points, repair the name lookup and test the actual guide.

What you’ll learn: Separate local connectivity, address reachability and name resolution.

Read the full guided story without the interactive controls

You can follow the same lesson here without JavaScript.

  1. Check the first part of the path

    Probe the local gateway, the device that connects this laptop to the wider network.

    What happens and why: The gateway responds in this model. That supports local connectivity; it does not establish that the guide’s application works.

  2. Compare an address with a name

    Test the service address and the guide’s name. Read both results before deciding what to repair.

    What happens and why: The service address responds but name lookup fails. DNS translates names to addresses; this contrast points to the configured resolver. Real networks may block particular probes.

  3. Repair the part the evidence points to

    Use an approved working name resolver rather than replacing an otherwise working cable.

    What happens and why: The resolver change repairs the name-lookup step here. Addresses use documentation-only ranges, and no real network probe is made.

  4. Retest the guide itself

    Resolve the name again and try opening the guide, not just probing a device.

    What happens and why: The name resolves and the fictional guide opens. A successful address probe alone would not prove the web application was healthy.

Takeaway: Check parts of a path separately. Working address reachability with failed name lookup suggests a different problem from a broken local connection.

Where this is useful: Useful when diagnosing “the internet is down” or a service that works by address but not name.

A fictional educational example, not a confirmed TWA assignment, assessment or learner outcome. Simplified to explore one idea; real situations need context and authorised procedures.

Optional deeper exploration: open the original technical workspace

Want to explore the technical model?

The guided story above introduces the idea. This original workspace lets you try actions in different orders. It has its own reset and does not inherit your story choices.

Gateway
A device that forwards traffic beyond the local network.
IP address
A numerical address used to reach a network endpoint.
DNS
The system used to look up addresses for names.
Resolver
A service that answers name-lookup requests.
TWA / The practice studio

An address works. A name does not.

Learning objective: Isolate DNS resolution from network reachability.

Explore · Observe · Explain

A fictional laptop can reach the gateway and service IP, but cannot resolve the service name.

Evidence desk

Gateway
192.0.2.1 responds
Service IP
192.0.2.20 responds in this model
DNS
Configured resolver does not answer
Worked explanation & takeaway — available without JavaScript

Working IP reachability with failed name lookup points toward DNS. Inspect and use an approved working resolver, then retest the hostname. A ping alone cannot establish application health; real networks may block ICMP. Documentation-only IP ranges represent no real target.

Fictional educational model. No live system, personal assessment or confirmed TWA assignment. All actions run locally in your browser.

Explore the idea / network

Follow the communication questions

This simplified path explains roles; actual networks and protocols can add other components.

  1. Resolve a name

    A resolver helps obtain the address for a requested name.

  2. Reach the network

    The device uses its local connection and configuration.

  3. Route as needed

    A gateway/router can forward traffic between networks.

  4. Reach the service

    The destination must accept and respond to the intended request.

Read both scenarios and explanations

Name lookup fails but a permitted connectivity test succeeds

Investigate the resolver and naming observation. Keep the test scope clear; it does not prove every application or route is healthy.

Several devices fail after a network change

Compare the shared scope with the authorised change record. Escalate useful observations instead of changing unrelated devices repeatedly.

An educational illustration using fictional situations. It is not a confirmed TWA assignment, live system, assessment or promise of a particular tool.

Build a vocabulary that supports a diagnosis

Begin with IP addresses, subnetting concepts, gateways and the difference between local and remote destinations. Then connect DNS and DHCP to the questions they answer: finding an address and obtaining network configuration. TWA’s existing direction includes these foundations, routing, switching, VLANs, segmentation, wireless, access controls, VPN concepts and monitoring.

Network engineering can emphasise designing and configuring connectivity. Administration adds maintaining the configuration, documenting change and helping operations remain understandable. Product models, simulator access and hands-on device arrangements need confirmation; an industry reference to a vendor is not a promise of vendor-specific training.

Isolate the failure before changing the configuration

In a fictional office, one service name fails to resolve while an authorised connectivity check still succeeds. That is a reason to investigate name resolution, not proof that every router is working or that replacing a DNS setting will fix the whole application. Compare observations and record what remains untested.

Another scenario affects every device after a planned network change. Review the shared scope and the change record with the authorised owner. Do not make unapproved live changes or assume that a blocked diagnostic packet means every form of traffic is blocked. A diagnosis needs protocol and context, not just a pass/fail icon.

Illustrative project brief

A small-office network explanation

Design a fictional office network and document how to investigate one local-connectivity and one name-resolution problem.

What you could document

  • A device and logical-network diagram
  • An addressing/service plan with no real credentials
  • A check/result troubleshooting log
  • A change and escalation note for a future administrator

What makes the explanation useful?

The explanation should separate local connectivity, name resolution and application behaviour. Every proposed change should have a reason and an authorised owner.

The learning plan determines actual activities and assessment. These deliverables are examples, not contractual curriculum outcomes.

A network design includes its handover

For a small-office example, identify devices, logical networks, intended services and access boundaries. Explain why a segment exists and who can change it. A later administrator should be able to locate the configuration, understand naming/addressing conventions and find the first checks for an outage.

Deeper directions include network support, administration and engineering. Security and cloud work build on related concepts but have different responsibilities. Discuss your foundations with TWA; the approved Nigerian selector covers Network Engineering, while any separate administration-specific plan needs scope confirmation.

TWA learning direction / Confirm your starting point

Discuss a suitable starting point.

Beginners can discuss networking foundations; learners with IT support experience can bring a connectivity problem they understand. Ask about simulator/device access, operating systems, lab permissions and the depth of configuration expected.

Beginners exploring networking and IT learners progressing toward network support, administration or engineering.

Our physical centre is at No. 7 Nkpokiti Road, Ogui, Enugu, opposite Flamingo Mall. Learners elsewhere in Southeast Nigeria, across Nigeria and internationally can discuss suitable arrangements. Delivery, eligibility and availability need confirmation.

Ask about prerequisites and scope →

Existing TWA learning areas to discuss

  • TCP/IP, addressing, subnetting and network fundamentals
  • Routing, switching, VLANs and network segmentation
  • Wireless networking, DNS, DHCP and connectivity services
  • Network security, access controls and VPN concepts
  • Monitoring, troubleshooting and network documentation

These are learning directions rather than a fixed syllabus. Confirm the actual tools, activities, equipment, schedule and assessment before committing.

Industry reading

References inform the explanations above. They do not imply a TWA partnership, accreditation or included software licence.

Questions about Network Engineering & Administration.

Does a Wi-Fi connection mean the internet works?

No. It establishes a local connection state, while other network services or the destination application may still fail.

Will I work on live networks?

Live access is not confirmed here. Discuss authorised labs, simulators, devices and assessment arrangements with TWA.

Are Network Engineering and Administration separate priced programmes?

They share this parent page. Only the approved Network Engineering focus has a fixed Nigerian selector; other scope needs confirmation.

Training options & enquiries

Understand your options.
Plan your next step.

Compare approved Nigerian packages or request a personalised private quotation for international training. Availability is confirmed with TWA.

Choose the training arrangement you want to discuss. TWA will confirm eligibility, learning needs and delivery arrangements with you.

Nigerian learners: approved fees

These rates apply only to Network Engineering. Prices for other programmes are confirmed by enquiry.

Approved Nigerian fees (NGN) for the training subjects listed below
Learning levelGroup TrainingPrivate Exclusive
Beginner₦300,000₦600,000
Intermediate₦700,000₦1,000,000
Advanced₦1,000,000₦1,500,000

Group Training includes

  • Live training sessions
  • Session recordings
  • Learning materials

Private Exclusive includes

  • Live training sessions
  • Session recordings
  • Learning materials
  • Projects
  • Interview preparation
  • CV preparation

Before you enquire

  • Group Training requires more than 20 participants. Group formation, schedules and places need confirmation.
  • Standard training lasts a maximum of 2 months, except Private Exclusive training. Confirm the dates for your selected plan.
  • Private training may involve online and physical sessions in a hybrid format, subject to availability and confirmation. Private Exclusive duration and schedule are agreed with TWA.
  • Enquiry required. A listed programme or price does not confirm an active cohort or an available training slot.
Prepare a WhatsApp enquiry directly — all approved options

Each link includes the programme, level, package and fee. Review the draft in WhatsApp and press Send there.

Network Engineering — choose level & package

Rates apply to Network Engineering. Confirm any administration-specific scope separately.

International learners / Private training

A private learning plan.
A personalised quotation.

Discuss private training around your current experience, learning objectives, desired specialisation, preferred schedule and time zone, duration, delivery arrangements and individual learning needs. TWA will confirm what can be offered before you commit.

International training uses personalised quotations. Nigerian fees are not applied or converted into another currency. Schedules, duration and delivery must be agreed with TWA; a request does not confirm availability.