Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

Internetworking with TCP/IP Level I

Course Outline: DAY ONE / DAY TWO

 

DAY ONE

9:00-9:50 a.m.

  • Introductions, overview of course and administrative matters.
  • Seven layer model and encapsulation
    • How the theory relates to actual implementation.
    • How pointers in the header facilitate processing the packet.
  • How data packets are processed: the role of hardware and software address, names and port numbers.

10:00-10:50 a.m.

  • Protocol header structure.
  • Internetworking devices such as switches, routers and gateways.
    • Using hardware and IP addresses.
    • Deciding whether to implement cut-through switching.
  • Labs 1: Equipment Utilization

11:00-12:00 p.m.

  • Segmenting the network at the hardware level and at the software level.
  • The logical and physical architecture of the network and the role of the devices in defining that architecture.

12:00-1:00 p.m. LUNCH

1:00-1:50 p.m.

  • Lab 2: Encapsulation
  • Ethernet communications and technology
    • Frame structure
    • 10BASE-X nomenclature
    • Repeater rules

2:00-2:50 p.m.

  • Overview: Fast and Gigabit Ethernet
    • Cabling
    • Hubs and Switches
    • Full duplex and L2 switching

3:00-3:50 p.m.

  • Bridges and layer two switches; spanning tree

4:00-4:30 p.m

  • Review and discussion

(back to top)

DAY TWO

9:00-9:50 a.m.

  • The architecture of the Internet
  • IP and IP addressing

10:00-10:50 a.m.

  • Subnets and masks
    • Partitions and address spaces
    • 8-bit bound
    • Variable length and CIDR
    • Examples and exercises
  • Lab 3: Addressing

11:00-12:00 p.m.

  • Lab 4: Assigning IP addresses
  • Broadcasts and multicasts

12:00-1:00 p.m. LUNCH

1:00-1:50 p.m.

  • Address and name resolution
  • ARP
  • ICMP
    • PING
    • Destination unreachable types

2:00-2:50 p.m.

  • Lab: ICMP
  • BOOTP and DHCP

3:00-3:50 p.m.

  • Configuring IP in the client
  • Introduction to TCP and UDP

4:00-4:30 p.m.

  • Review and discussion

(back to top)

To bring this course on-site, please call Michele Zarella at 508.490.6620 or email at mzarella@nww.com
Error 404--Not Found

Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

Error 404--Not Found

Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.