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 II

Overview:

This is a continuation of Internetworking with TCP/IP Level I. The upper levels of the TCP/IP protocol suite will be investigated thoroughly. TCP mechanisms to ensure reliable transfer of data will be studied. This includes session set-up, sequencing, flow control and session termination. TCP timers and assessment of application performance will be discussed. The second part of the class includes a study of routers and routing protocols, including RIP, OSPF, and multicasting. A comparison will also be made to Cisco’s IGRP and EIGRP. The third section of the class involves a study of application program interfaces such as DNS, TELNET, SNMP, FTP, HTTP, and related topics such as voice over IP, security, and proxy servers. Finally, troubleshooting techniques and IP Version 6 will be covered. The final exercise the class will complete will require the knowledge of much of the material covered in the four-day sequence.

This seminar will enable you to:

  • Understand the overall operation of TCP.
  • Grasp the relationship between network performance and application performance.
  • Understand how a TCP client and server coordinate a TCP flow.
  • Immediately recognize when TCP establishes or terminates a session.
  • Calculate TCP throughput.
  • Recognize retransmissions.
  • Recognize processors that drag behind network delivery.
  • Understand the role of TCP error detection.
  • Compare the purpose of TCP with UDP.
  • Analyze in some detail how FTP works.
  • Understand the role many well-known application interfaces.
  • Investigate how voice and video can be transported over TCP/IP.
  • Gain an understanding of the trouble shooting tools available.
  • Attempt troubleshooting simple and difficult problems in the network.
  • Learn about the design of the next version of IP.
  • Use knowledge gained in this class to systematically follow the creation and flow of a data packet.

What students say about this course:

" This class was an excellent technical overview. I especially like the focus on TCP performance."

    • M. Altland, Verizon

" This class was challenging but very well presented. The hands-on with the test equipment was particularly beneficial."

    • G. Burkholder, Sprint

" The TCP/IP class was technically very solid. Dr. Hippensteel did a great job of presenting it. Our group found it to be very worthwhile."

    • G. Downey, Hershey Foods

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.