TCP loses segments ifa link fails in unicast routing.Describe behavior of TCP when old route becomes available
409089
tcp has guearanteed delivery service and error correction so if the packets do not reach their destination you should receive an icmp internet control message protocol such as a ttl expiration or a host unreachable error message a method known as packet switching will break the data down into segments and travel the best path available they may all go a different route or they make take some of the same routes--there may be a problem with the receiving node dude
875892
http://www.rfc-editor.org/rfc/rfc3961.txt\n\n i dont really  know about it but what the hellthats everything i found
193201
I think you'll find any router worth its salt won't let you specify the loopback interface as a destination gateway. If it did I suspect it would just loop around until its TTL expired.
775965
make sure that you are using same IP range in both the router. ( IE. 192.168.1.1 - 192.168.1.254 ) with 255.255.255.0 same subnet. if you are using different range other one it might cause you this problem.\n\nare you able to ping that node ( PC )\n\nhave you installed all services in all PC.\n\nare you using firewall ( third party firewall ) in any PC.\n\nit would be easy for me to give you correct solution if you can provide more details.
98583
the receiver may have disabled the links in their chat client
336219
If you are refering to "traceroute", then yes, it\nis part of the base OS:\n\n$ which traceroute\n/usr/sbin/traceroute\n\n[Just so we're on the same page, this is the utility that\nuses ICMP to discover the route (and latencies) that\na packet would take from one location on the net to\nanother.]
1180473
You're right, your existing access lists won't be able to operate on packets in labelled MPLS VPNs. You should move your access lists as close as possible to the source of traffic, possibly to the distribution/access layer routers. Network core is supposed to be switching data very quickly. In certain situations access lists are processes by the main processor (as opposed to the hardware ASICs) and can be very processor intensive and slow in the core routers. Move your access list closer to the source.
168014
Probably some connection pooling happening somewhere. Don't worry about it, it'll get dropped or reused if required.
351368
It can actually take much longer...it all depends on the route it takes and the reliability of the computers (hops) on that route.  If for example it needs to take a route that includes hops in Brazil for example and as it hits a server in brazil, there is an power outage, it is possible that the email will remain on that hop until a time when power is restored and the route can be finished.  Now in theory routes are self fixing, so if something happens another route is instantly determined and taken, however if something happens where the traffic (email or information be sent/receieved) can not be back tracked it will remain in limbo or be lost.  An example of this is if hits on the 4th or 5th leg of a sprintnetwork.net system and the entire sprintnetwork.net service is interrupted...the information can not go back to the prior hops as they are no longer available, and thus would be lost or delayed.  Most Mail servers require a response from the destination server before accepting the send, however not all do.  If your experiencing a delay in email this may be the case.  I have personally had email both that I've sent and received that have been delayed upto 3 monthes.
890951
http://en.wikipedia.org/wiki/Routing
635515
It might not be a problem with the splitter, ur ISP might just be cutting you off after you use the internet for a long time or something. ping them
519874
could be your browser or the speed at which your connected, sometimes you lost your signal altogether.
1122111
routers breakup broadcast domains, switches breakup collision domains.\n\nsay you have two networks joined by one router netA & netB. All devices in NetA are in the same broadcast domain, all devices in NetB are in their own broadcast domain. \n\nDirectly connected to each port on the router is a switch. Any devices connected to a specified switchport are in their own collision domain.\n\nfrom http://certcities.com/forums/forum_...p?tid=1441&pn=1\nA broadcast domain is simply an area in which broadcasts can be sent. \n\nfrom http://www.webopedia.com/TERM/C/collision_domain.html\nA group of Ethernet or Fast Ethernet devices in a CSMA/CD LAN that are connected by repeaters and compete for access on the network. Only one device in the collision domain may transmit at any one time, and the other devices in the domain listen to the network in order to avoid data collisions. \nA collision domain is sometimes referred to as an Ethernet segment.
202820
The nature of the routing of the internet,
538630
TCP effectively accomplishes error control through a mechanism called positive acknowledgment with retransmission.  Every segment that does not get positively acknowledged is assumed to have arrived in error (or not arrived at all) and will get retransmitted.  So TCP is a "positive acknowledgment protocol" and it does this by sending sequence numbers back in the ACK packets, so it can associate ACKs with packets.  Now here's where flow control comes in... the straight positive ACK system by itself is just a stop and wait protocol, where a new packet cannot be sent until the ACK for the previous packet has come back.  So TCP creates what is called a sliding window, where several unACKed packets can exist at any time.  As the ACKs come back, the window slides forward and more packets are sent.  This allows TCP to make the best use of bandwidth.
150568
untill the termination phase\n\nThe connection termination phase uses a four-way handshake, with each side of the connection terminating independently. When an endpoint wishes to stop its half of the connection, it transmits a FIN packet, which the other end acknowledges with an ACK. Therefore, a typical teardown requires a pair of FIN and ACK segments from each TCP endpoint.\n\nOr\n\nA connection can be "half-open", in which case one side has terminated its end, but the other has not. The side which has terminated can no longer send any data into the connection, but the other side can.
958470
There is probably an IP conflict check your clients' IP settings.  If you have a session open with a certain IP or certain range and all of a sudden another tunnel trys to authenticate with a conflicting IP or range your router doesn't know what to do but close one of the sessions and keep one open.  I had a similar problem with a wired firewall, where it would kick off the user that already authenticated and just open a new session for the person trying to authenticate with the conflicting IP.  See if you can get Static IP from your provider.