How does a host know a data packet was not recieved?

How does a host know a data packet was not received?

When the TCP/IP protocol is used they use what is called a 3 way handshake. If UDP protocol is used it is connectionless which means there is no guarantee of packet arrival. For more information, see the Related Link.

Why is data uploaded as you download?

Data is transmitted in packets. TCP/IP has to respond to each packet. TCP allows for the sending side to know that the packet was received. If there is a malfunction, it can retransmit the packet.

When more than one application is running on a server how does IP know which service should be presented a data packet?

The port number lets IP know which service should be presented a data packet.

How does the access point know if a wireless data packet is intended for its network?

Usually IP addressing is used.

How does IP know which service should be presented a data packet when more than one application is running on a server?

By the Port Number

Why was it good that annemarie did not know what was in the packet?

Becaus she did not want to know

How does the orginatiing system know whether or not a packet was received?

The originating system knows whether or not a packet was received through acknowledgment (ACK) mechanisms used in communication protocols. When a packet is sent, the receiving system is expected to send back an acknowledgment to confirm receipt. If the originating system does not receive this acknowledgment within a specified time frame, it assumes that the packet was lost or not received and may retransmit it. This process is fundamental in protocols like TCP, which ensures reliable data transmission.

What is an arp request packet for?

ARP stands for Address Resolution Protocol. This is IP's way of requesting a MAC address (or hardware address) from a host located at a certain IP address. In order for a host on a network to send a unicast packet across the network, it must know both the source and destination MAC addresses. ARP is used to obtain a MAC address similar to the way DNS is used to obtain an IP address from a domain name (www.anydomain.com).

How does data know which way they are supposed travel in a cable?

From the source. Wherever the data leaves from. For example, when I click "Post This Answer", the packets that include this answer leave my laptop and go to my router. They then go to my ISP, which looks at them and then sends them to wiki.answers.com. Wiki.answers.com then reads the packet and automatically edits this page to include the answer.

Why are port numbers included in the tcp header of segments?

So the destination host knows what port to send it to. If the destination just takes a guess as to what port to send it to and sends an RDP packet to port 80 what do you think is going to happen?

Where to download winsock packet editor?

One Place I Know Of That You Can Get It From Is Wpepro.com

How different rages of ip send data to each other?

Short and simple answer is: routers A little more detail. A router has a routing table. That table tells it about the networks that are connected to it, and where to send IP packets based on their addresses. So for example, lets make a simple network: Subnet A: 10.0.0.0/24 Host A: 10.0.0.2 Subnet B: 10.0.1.0/24 Host B: 10.0.1.2 Router Interface A: 10.0.0.1 Interface B: 10.0.1.1 Interface C: 10.0.2.1 * default route So, if you are host A, and you want to send data to host B (on a different subnet) you would have to send your data to Interface A on the router. It would see that you are trying to send data to a different subnet then the one you are on, and it would look in its routing table to see if it knows anything about the subnet 10.0.1.0/24. Since the router is connected to 10.0.1.0/24 on interface B, the router would send the packet out interface B, and it would end up at host B through the magic of switching. Now, if we needed to send data to say... google.com (66.102.7.99) the router would see that address, and not know where to send it, since none of its interfaces are connected to that subnet. The router would then send this packet out its default route, which would lead to a router that had more information on other networks it is connected to. This would continue until eventually it would reach a router that had some idea where the 66.102.7 network is, and the packet would eventually end up at google. I say eventually, and it may take several hops to get to google, but the whole process (from your computer to google -- or wherever) normally is done in under 250 milliseconds. (My packets get to google in about 65 milliseconds).