TCP/IP

Invader

Hello,

could someone please explain what a "Working Knowledge of TCP/IP" means. I know that TCP/IP is a collection of protocals that define the workings of the Internet, but a working knowledge?????

Looking forward to hearing form you.

Invader

dmaftei

"Working knowledge" means "knowing pretty well", as opposed to being clueless or being an expert. Does this answer your question?

Invader

Would it mean that you a firmiliar with network topologies, what devices and are required for routing/switching , what protocols (RIP/IGRP/ATM/IP) would need to be programmed in order to access Lans or wans?

sprkymrk

I think it means being familiar with using TCP/IP troubleshooting utilities like trace, ping, etc. It might also mean recognizing standard IP ranges (Class A, B, C, Multicast, etc.) and knowing what default subnet masks look like, how to subnet, and how to recognize configuration errors on clients/routers (wrong default gateway, wrong mask, incorrect or missing route statement).

Invader wrote:

Would it mean that you a firmiliar with network topologies, what devices and are required for routing/switching , what protocols (RIP/IGRP/ATM/IP) would need to be programmed in order to access Lans or wans?

These are probably things you need to know for the CCNA exam, but the routing protocols may be catagorized under a different objective than TCP/IP.

Invader

thanks guys, that makes sense.

marlon23

You need to undestand how is data processed from Application to Network Interface layer, what protocols each layer use, what are their features, puspose, and how each particular protocol works.
Don't learn just what is enought for CCNA, becouse you really need this basics to understand more advanced topics which will came later. When you will underestimate this now, you will have problems later.

Danman32

A working knowledge can also mean that when your dad Im's you from your uncle's house saying that he can't get his laptop to go online when he connects it to your uncle's router, you can tell that your uncle has a real IP address from the ISP rather than a NATed IP address, thus you suspect the router is misconfigured. Then when given the "router's" model number, you find it is a 10/100 switch and not a router, which explains why your uncle gets a public IP and can get online while your dad gets no IP and can't get online. While figuring this out, you're able to instruct your dad on how to obtain all the IP information so you can figure out if IP, subnet mask, gateway and DNS is correct for both of them to get out on the internet.