basic working of TCP/IP

Hi experts ,
i like to know the working of TCP/IP .
i have studied the theory of it but i didnt get well the working .
what is the layer (5 layer )
how the layer working ?
How the modem response it ?
please help me ,is there any example to understand

The session layer coordinates applications as they interact on two communicating hosts. In networking, data communications travel on packet-switched not circuit-switched networks, unlike telephone calls. Communication between two computers involves many mini-conversations, thus ensuring that the two computers can communicate effectively. One requirement of these mini-conversations is that each host plays dual roles: requesting service, like a client; and, replying with service, like a server. Determining which role they are playing at any given moment is called dialogue control. The session layer establishes, manages, and terminates sessions between applications. This includes starting, stopping, and resynchronizing two computers who are having a "session."

The session layer decides whether to use two-way simultaneous conversation or two-way alternate communication. This decision is referred to as dialog control. If two-way simultaneous communication is allowed, then the session layer does little in the way of managing the conversation, and allows the other layers of the communicating computers to manage the conversation.

Here's an example from **broken link removed**

The Session Layer
If you are an ardent user of the Yahoo Messenger or any messenger for that matter and if you are popular among you friends, I am sure you would have faced the crisis of replying to several message windows popping up on your screen. Imagine the complexity of the software (yahoo messenger for ex), it has to cater to serveral connections at the same time. Each window is a connection, the front end (the blank space where you type your message) is the application layer, the smiley's and italics that you conjure up are displayed on the window at the receiving end through the presentation layer and each session is maintained by the session layer.

Every time you open a new chat window the session layer sets up the connection to the yahoo server and any message received for the window is forwarded to the appropriate window or in other words session layer manages the connections and when the window is closed it tears down the connection. If the messenger has a buggy session layer application I shudder to think about the plight of the messenger user, messages meant for one person might end up in the window of another( I hope you got the picture).

Click to expand...

Hope the above example clears things up for you. Actually the entire document has very good examples of each of the 7 layers of the OSI Model.

TCP/IP is arguably the single most important computer networking technology. The Internet and most home networks support TCP/IP as the "language" computers use to find and connect with each other

the biggdoggru i am the beginner in that filed i don't know well OSI ?
why you are refereeing OSI ? any simulation software for it ?

one can think of 'layers ' from practical application as:

1)application(the sw which is communicating outside--user pgm)
2)just below the application layer is 'tcp'
3)below that 'ip'
4)below that 'datalink layer(mac)

assume that the application has a data to be communicated(i.e) data packets)
'tcp' layer adds 'tcp header' to the packet and pass below.
'ip' layer ' adds ip header to it and pass.
mac layer adds 'ethernet header ' and send out thro net.

so each layer adds its own header to the packet of data.

on the reverse , the first layer that receive the incoming is 'mac layer '
it strips of the header and pass above .
likewise each layer checks its own layer header and strips it.
finally you get the received 'packets ' in the application.

in short , data packets are added with each layer header when transmission.
on reception , each layer strips that layer haeadr and finally yo get the data.
the tcp layer header contains 'port no' also,

There are two models used to describe TCP/IP, OSI Model and the TCP/IP Model. The OSI Model was developed by of course the OSI Standard Group, while the TCP/IP Model was developed by DARPA DoD.



Depending on who you reference in regards to the TCP/IP Model it has either four or five levels and there is some correlation between the two models as shown by the above photo.

Here is a good comparison of the two models:

The TCP/IP and OSI Network Models

TCP/IP versus OSI

The model you were referring to in your original post is the OSI Model.

Here is one website...i hope this will help full to you
- The World's First Free Cisco Lab - Firewall.cx

can we connect two computer through wire (like lan) ?
has here using IP or any protocol ?

Sure, you can connect two computers without the use of a hub or switch by using a ethernet crossover cable:

Ethernet Crossover Cable

Assign a distinct static IP with the same subnet to each computer and you can ping, access services (EX. webserver) and share files between each computer.

Step by Step Instructions:



Hope the info helps.

yes,we can connect two computers that are in LAN i.e possible by IP address...

that is possible by ip .how can you explain ?

thannara123 said:

that is possible by ip .how can you explain ?

Click to expand...

please follow the below link
How to Link Two Computers Using IP Addresses | eHow.com

what is the difference between OSI and TCP/IP layer ?

check this

TCP/IP versus OSI

and tell your doubt properly..... there are many good post already that explain your doubts/......

I think a good simple demo environment to learn a lot of TCP/IP programming basics is by looking at sockets on Windows (or whatever). It is particularly easy on windows with Visual Studio Express and its free. You'll see '.BeginConnect' and '.BeginAccept' once you're in the right area. When you make your first "listening socket", make it use address IPAddress.Any (0.0.0.0) and port 80. Make your browser goto 127.0.0.1 (or any). The 'accept' handler will normally have a BeginRead() somewhere. Breakpoint BeginRead()'s handler. When it stops, step through and watch where the data floods in. (look for .EndRead) To display the data in a textbox is more work than you'd think but there's simple ways round that to start.
You write everything layer 4 (of 5) and above (5 and above for OSI) but can go deeper if you want raw IP sockets to make your own protocol to rival TCP or UDP. I dont think ethernet level access is possible so no layer 2of5 programming fun. Everything is in the System.Net.Sockets library and TechNet

Things may look a nightmare if you're starting from scratch, especially if you've got to learn the c#/vb too, but you'll find you can make a working PC to PC simple chat program in about 30 lines of code. (some of them lines are for threadsafeness too). Extend it to whatever once you've got it sussed. For easyness, each connection is passed on to a worker object that runs itself.

If you do look at this stuff, ask me for code anytime. In days of compuserve and home 56k and when things didn't exist off-the-shelf, and for fun, I wrote a (not https) filtering scheduled proxy for 300student/staff PC at the place gone to work to set them up IP. We had 10mbit FDX which was alot in 97 (we got 700kByte/s from microsoft even then), but written in VB3 using 'Catalyst's SocketWrench.ocx' and running on an NT4 twin p2, it handled everything simply and quietly. (up to the time upto the point of getting MS proxy2). All tributes to the reliability of IP and sockets.

Neal

I came across these interesting TCP/IP tutorials and thought I would share the links:

Thank you for visiting the dNet tutorials section! Whenever we get a burst of inspiration, we will add an article explaining how something works. Keep an eye out for articles on internet protocols, Windows programming, WinSock programming, and more. We hope you can learn something interesting from us!

Click to expand...

TCP/IP is one of the oldest sets of internet protocols still being used. If you are interested in learning about what makes the Internet work, check out this tutorial. Written by Erik Iverson.



This installment looks at how to use tools provided with your operating system to see TCP and related protocols in action. It also describes the flow of data between machines at multiple levels during simple network operations. Written by Erik Iverson.



Interesting real life examples.