1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Series 1 not downloading data

Discussion in 'TiVo Help Center' started by shototsu, Nov 11, 2008.

  1. bm5

    bm5 New Member

    3
    0
    Dec 16, 2008
    guys just bringing this up again. I followed cgf's method way back in early January and it is still working. I am able to get successful calls over turbonet daily.

    by the way, I came here to look up something else but was surprised to find this problem is still happening. VERY disappointing response from Tivo :(
     
  2. bittmann

    bittmann Member

    68
    0
    Apr 19, 2005
    South...
    Makes sense to me.

    Although I do wonder what any potential downsides might be (both to us AND to TiVo).
     
  3. nmiller855

    nmiller855 New Member

    5,400
    0
    Sep 26, 2000
    East of...
    I haven't made any modifications to my series 1 TiVo since any of this started & it is working fine now. Every once in a while a call fails & I just restart the call & it goes through quickly.
     
  4. joeysmith

    joeysmith New Member

    95
    0
    Jan 9, 2002
    i saw a trace of a newer TIVO elsewhere showing http 1.1 to that cgi.
     
  5. vjquan

    vjquan New Member

    18
    0
    Feb 14, 2009
    I joined this forum for the sole purpose of sending TivoJerry my TSN. I too experience the same problems most are having - call failed, call interrupted, etc. While the recent discussions have been about clearing logs, I only have the dial-up option and do not have access to the file system. This is frustrating to say the least as I constantly, on a daily basis, babysit to see what it did. Does anyone know if this affects series 2 boxes? If not, what's the difference? I would like to upgrade to HD, but their boxes only support cable while I'm on DirecTV. I would hate to waste my lifetime subscription transfer on a non-HD machine, but am tempted to do so. This has been going on too long! I am hopeful that a resolution is in the works, but I don't see any indication of that happening. Is this going to be one of those problems where it just gets brushed off? There's got to be many more out there that just aren't posting.
     
  6. dbranco

    dbranco Member

    682
    1
    Nov 20, 2003
    I have a Series 2 box connected to the same phone line as my (often-failing) Series 1. It has never experienced any "Service Unavailable" or bogus "Call Interrupted" errors.

    I sent TiVoJerry my S1 TSN, and at his request, later sent him the S2 TSN. I suspect he is looking at at the logs for each box, trying to determine what the difference is.
     
  7. tzone

    tzone New Member

    16
    0
    Feb 28, 2002
    I've also been having problems on a recently repurposed Series 1 unit with Lifetime service and turbonet. I initially thought that my old turbonet card (ISA riser with Kingston NIC) was going bad so I opened another Series 1 of mine that is retired and took out the newer (much smaller) NIC and put that in the unit. It made no difference. I even went so far as to reimage the drive in the unit and repeat guided setup but that seemed to take on the order of 15-20 tries for it to complete (but it eventually did amongst a bunch of service unavailable and call interrupted messages).

    My question for TiVoJerry is: Do you still need captures of the failed events? If so I can get out my old 10baseT hub and use wireshark to capture a failed call if you would like. I see that several others have already provided you with TCP captures so I just want to see if you would like to have more data or not before I go to all the work to set this up.

    /troy
     
  8. dlee0708

    dlee0708 New Member

    115
    0
    Sep 20, 2002
    Lewisville, TX
    Well, I think my mother has pretty much had it with this situation. She has not had a successful connection since Dec 3, no program guide data since Dec 17.

    I took the data from my Tcp capture and wrote a simple little test program to send the same connetion to Tivo and it works fine (acks the 2nd packet). The difference is the 2nd packet sent by my test program is 536 bytes instead of 1460 like the Tivo is sending. For some stinking reason Vista is setting the MTU down to 576 when I run my program and just sending 536 bytes at a time. But if I run Outlook Express and send a large file it sends much larger packets (still not 1460, but at least larger than 536). I don't know where this problem is, but I am giving up on this. I wish Tivo would at least tell us what is going on. Just even knowing if the packets are getting to TivoInc would be something. But as far as telling us what they have determined what is wrong, nothing has come back.
     
  9. dlee0708

    dlee0708 New Member

    115
    0
    Sep 20, 2002
    Lewisville, TX

    Troy,

    If you ever connect up the Hub, I am curious does yours fail the same way my mothers does (see post on 02/07/2009 for full data if you want to see it). My mothers makes a connection, sends a Http POST packet of 63 bytes, then sends 1460 bytes, gets the ack from TivoInc of the first 63 bytes (ack 64) but never gets an ack from TivoInc for the 2nd 1460 byte packet. Then all you see is the Tivo resend the 2nd packet about 10 times and then a Server error from TivoInc (still just acking the first 63 bytes) and the connection ends.
     
  10. mec1991

    mec1991 Cranky old coot

    659
    0
    Nov 5, 2004
    Back home...
    Haven't posted for awhile, but the past few days I have been getting about 30% failures, either service unavailable during connecting or call interrupted during downloading. Much better than in Dec and Jan but obviously still not fixed as I had earlier thought. Oh well, at least I have up to date guide data with a little babysitting.

    One thing, though, I have really learned to appreciate the UI of the S1; it is blazing fast and I am not blindsided by ads like I am on my S2 :up: :)

    I'd really like to keep the old Sony purring along as long as possible. I plan on getting a HD model if they ever support clear QAM with guide data. I personally have no use for a STB with 900 channels and really only want my locals in HD. The SciFi channel crap is still going to be crap regardless of whether it is in HD or not.

    OTA is a non starter for me as I cannot use an outdoor antenna and the two indoor ones I tried worked as well as hooking up a banana instead.
     
  11. bittmann

    bittmann Member

    68
    0
    Apr 19, 2005
    South...
    [offtopic]

    With respect to DirecTV and TiVo: Have you seen this?

    [/offtopic]
     
  12. bittmann

    bittmann Member

    68
    0
    Apr 19, 2005
    South...
    FWIW: I messed around with my TiVo a bit, setting the MTU on the NIC way down. Tried 1460, 1400, 800, and 128 (!!) byte MTUs with the same result -- regardless of MTU, sometimes it'd hang on the POST, sometimes it wouldn't. For what little THAT's worth.

    BittMann
     
  13. pip55

    pip55 New Member

    42
    0
    Dec 29, 2005
    I have a SA series2 that's joining in on the data guide loss. Haven't been able to successfully download & install since December. When I do a search for local numbers they are found and downloaded no problem but if i try any in- state numbers with test phone connection or make daily call, they all fail. Tried 818 450 1705 & 602 605-1880 & other states as well. Burbank and Arizona came the closest to completion but failed on download or install. I was going to try a new image install as well, thinking perhaps an older software version might work but apparently doesn't look well. If an older image doesn't remedy the problem does that point to a integral motherboard situation for the series 1 & 2 that conflicts with new scripts from Tivo Central? I have a hughes sddvr40 that downloads data as always. Not ready to do a Cl&Del yet, although I believe that has been tried already. Can you serial connect to unmodded series2?
     
  14. bittmann

    bittmann Member

    68
    0
    Apr 19, 2005
    South...
    You'd be the 1st Series2 that's experiencing this issue, if that's the case.

    How confident are you in your phoneline/your modem? (That'd be my first suspicion...It's the least complicated explanation, anyhow)
     
  15. vjquan

    vjquan New Member

    18
    0
    Feb 14, 2009
    Thanks, but this is just another DTV receiver where they charge monthly fees. I'm interested in a stand alone Tivo where I can transfer my lifetime service.
     
  16. dlee0708

    dlee0708 New Member

    115
    0
    Sep 20, 2002
    Lewisville, TX

    BittMann,

    That is real interesting information. Could you set the MTU down to 576, do a Daily Call and post the the Tcp capture like you did on 02/09, except also post the HTTP POST /tivo-service..., the next packet the Tivo sends (seq 64) and then the next 2 packets received by TivoInc (or the whole thing if you want). I would do this myself, but its my Mom's Tivo that is having the problem and it doesn't have telnet access (still kicking myself for not adding that). I mainly want to see the size of the packets sent to TivoInc and what ack packets coming back from TivoInc telling me what packets it has received.

    I just don't understand why my test program running on my mom's computer gets responses from TivoInc, but the Tivo doesn't. I thought it was because of the MTU difference, but your little test shows different and I just want to see what the difference is when you set the MTU down to what her computer has it set at. I can change my program to look like your test and see what happens on my mom's Tivo. Maybe we can figure out what is making it fail, because it appears Tivo isn't making any effort to tell us. This is the first time I haven't defended Tivo, but I have not heard Jack Squat from them, so I have changed my tune.:mad:. I'm not expecting a fix from Tivo necessarily, but at least info on what they know. I have spent a ton of time and my mothers time trying to help find the problem instructing my 82 year old mother on how to set up the network and then me getting the trace and sending to it Tivo with all the info and I don't think they have done anything (or if they have done anything they haven't said anything).

    The one thing that for sure Tivo should know is whether the packets sent from my mom's Tivo are making it to TivoInc. If they aren't getting there, then I can tell her ISP they need to fix whatever it is that is blocking the packets to TivoInc, but I don't feel I should do that unless I know for sure that TivoInc is not getting the packets.
     
  17. bittmann

    bittmann Member

    68
    0
    Apr 19, 2005
    South...
    I can give it a shot, but it'll be a bit.

    And don't give up on TiVo just yet. If this was "easy", it would've been fixed earlier. And if it wasn't something that they are going to try to fix, TivoJerry wouldn't be involved.

    BittMann
     
  18. dlee0708

    dlee0708 New Member

    115
    0
    Sep 20, 2002
    Lewisville, TX
    I can certainly wait for you to have a chance. Glad you are able to this.

    I probably shouldn't have gotten harsh, but it's starting to get frustrating. To be honest, I really don't think my my mothers problem is really a Tivo problem (Tivo DVR or Server at TivoInc), but a network issue that is not handling this old HTTP HTML1.0 format (or something like that), but TivoInc should be able to look at our logs, compare them to what there Ethereal/WireCapture are seeing on their end and tell us where the problem is. It happens on my mothers Tivo 100% of the time. It would be very simple to figure this out, look at my mothers capture, look on their side and see if they are getting the packets. Dang, I tried to keep from going negative, but I did it again. Please Tivo, restore my faith.
     
  19. tzone

    tzone New Member

    16
    0
    Feb 28, 2002
    I connected everything up this morning (old Netgear 10baseT hub and Wireshark). My capture does look very similar to yours with several retransmissions on both ends and eventually ends with:

    HTTP/1.1 500 Internal Server Error

    Note that this is in a house with two TiVoHD units that connect just fine to the tivo service via broadband everyday.

    Now to see if I can get a download interrupted capture next.

    /troy
     
  20. dlee0708

    dlee0708 New Member

    115
    0
    Sep 20, 2002
    Lewisville, TX
    Could you post your capture. If you are seeing several retranmissions by the Tivo Server that is different than what my mom is getting. I would be curious to see exactly what you are getting.

    Here is what I have:
    Code:
    No.     Time        Source                Destination           Protocol Info
         25 197.419017  192.168.1.4           204.176.49.2          TCP      1157 > http [SYN] Seq=0 Ack=0 Win=512 Len=0 MSS=1460
    
    Frame 25 (60 bytes on wire, 60 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 0, Ack: 0, Len: 0
    
    No.     Time        Source                Destination           Protocol Info
         26 197.502033  204.176.49.2          192.168.1.4           TCP      [TCP ZeroWindow] http > 1157 [SYN, ACK] Seq=0 Ack=1 Win=0 Len=0
    
    Frame 26 (60 bytes on wire, 60 bytes captured)
    Ethernet II, Src: 00:1e:2a:08:cd:98, Dst: 00:0b:ad:32:12:1f
    Internet Protocol, Src Addr: 204.176.49.2 (204.176.49.2), Dst Addr: 192.168.1.4 (192.168.1.4)
    Transmission Control Protocol, Src Port: http (80), Dst Port: 1157 (1157), Seq: 0, Ack: 1, Len: 0
    
    No.     Time        Source                Destination           Protocol Info
         27 197.502453  192.168.1.4           204.176.49.2          TCP      1157 > http [ACK] Seq=1 Ack=1 Win=1460 Len=0
    
    Frame 27 (60 bytes on wire, 60 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 1, Ack: 1, Len: 0
    
    No.     Time        Source                Destination           Protocol Info
         28 197.584177  204.176.49.2          192.168.1.4           TCP      [TCP Window Update] http > 1157 [ACK] Seq=1 Ack=1 Win=4236 Len=0
    
    Frame 28 (60 bytes on wire, 60 bytes captured)
    Ethernet II, Src: 00:1e:2a:08:cd:98, Dst: 00:0b:ad:32:12:1f
    Internet Protocol, Src Addr: 204.176.49.2 (204.176.49.2), Dst Addr: 192.168.1.4 (192.168.1.4)
    Transmission Control Protocol, Src Port: http (80), Dst Port: 1157 (1157), Seq: 1, Ack: 1, Len: 0
    
    No.     Time        Source                Destination           Protocol Info
         29 197.641810  192.168.1.4           204.176.49.2          HTTP     POST /tivo-service/mlog.cgi HTTP/1.0
    
    Frame 29 (117 bytes on wire, 117 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 1, Ack: 1, Len: 63
    Hypertext Transfer Protocol
    
    No.     Time        Source                Destination           Protocol Info
         30 197.698146  192.168.1.4           204.176.49.2          HTTP     Continuation
    
    Frame 30 (1514 bytes on wire, 1514 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 64, Ack: 1, Len: 1460
    Hypertext Transfer Protocol
    
    No.     Time        Source                Destination           Protocol Info
         31 197.825455  204.176.49.2          192.168.1.4           TCP      http > 1157 [ACK] Seq=1 Ack=64 Win=4299 Len=0
    
    Frame 31 (60 bytes on wire, 60 bytes captured)
    Ethernet II, Src: 00:1e:2a:08:cd:98, Dst: 00:0b:ad:32:12:1f
    Internet Protocol, Src Addr: 204.176.49.2 (204.176.49.2), Dst Addr: 192.168.1.4 (192.168.1.4)
    Transmission Control Protocol, Src Port: http (80), Dst Port: 1157 (1157), Seq: 1, Ack: 64, Len: 0
    
    No.     Time        Source                Destination           Protocol Info
         32 197.827593  192.168.1.4           204.176.49.2          HTTP     Continuation
    
    Frame 32 (1514 bytes on wire, 1514 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 1524, Ack: 1, Len: 1460
    Hypertext Transfer Protocol
    
    No.     Time        Source                Destination           Protocol Info
         33 198.280470  192.168.1.4           204.176.49.2          HTTP     Continuation
    
    Frame 33 (1514 bytes on wire, 1514 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 64, Ack: 1, Len: 1460
    Hypertext Transfer Protocol
    
    No.     Time        Source                Destination           Protocol Info
         34 199.199982  192.168.1.4           204.176.49.2          HTTP     Continuation
    
    Frame 34 (1514 bytes on wire, 1514 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 64, Ack: 1, Len: 1460
    Hypertext Transfer Protocol
    
    No.     Time        Source                Destination           Protocol Info
         35 201.040309  192.168.1.4           204.176.49.2          HTTP     Continuation
    
    Frame 35 (1514 bytes on wire, 1514 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 64, Ack: 1, Len: 1460
    Hypertext Transfer Protocol
    
    No.     Time        Source                Destination           Protocol Info
         36 203.244885  192.168.1.1           192.168.1.4           UDP      Source port: 4457  Destination port: 40116
    
    Frame 36 (174 bytes on wire, 174 bytes captured)
    Ethernet II, Src: 00:1e:2a:08:cd:98, Dst: 00:0b:ad:32:12:1f
    Internet Protocol, Src Addr: 192.168.1.1 (192.168.1.1), Dst Addr: 192.168.1.4 (192.168.1.4)
    User Datagram Protocol, Src Port: 4457 (4457), Dst Port: 40116 (40116)
    Data (132 bytes)
    
    0000  54 4d 44 50 01 00 00 11 00 78 00 00 00 02 00 74   TMDP.....x.....t
    0010  54 4d 53 53 5f 54 45 53 54 5f 4e 4f 44 45 00 00   TMSS_TEST_NODE..
    0020  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
    0030  30 30 31 45 32 41 30 38 43 44 39 38 38 38 45 45   001E2A08CD9888EE
    0040  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
    0050  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
    0060  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
    0070  ff ff ff ff 00 00 00 00 00 00 00 01 ff ff ff ff   ................
    0080  ff ff ff ff                                       ....
    
    No.     Time        Source                Destination           Protocol Info
         37 203.245308  192.168.1.4           192.168.1.1           ICMP     Destination unreachable
    
    Frame 37 (202 bytes on wire, 202 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 192.168.1.1 (192.168.1.1)
    Internet Control Message Protocol
    
    No.     Time        Source                Destination           Protocol Info
         38 204.720520  192.168.1.4           204.176.49.2          HTTP     Continuation
    
    Frame 38 (1514 bytes on wire, 1514 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 64, Ack: 1, Len: 1460
    Hypertext Transfer Protocol
    
    No.     Time        Source                Destination           Protocol Info
         39 212.080887  192.168.1.4           204.176.49.2          HTTP     Continuation
    
    Frame 39 (1514 bytes on wire, 1514 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 64, Ack: 1, Len: 1460
    Hypertext Transfer Protocol
    
    No.     Time        Source                Destination           Protocol Info
         40 226.802100  192.168.1.4           204.176.49.2          HTTP     Continuation
    
    Frame 40 (1514 bytes on wire, 1514 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 64, Ack: 1, Len: 1460
    Hypertext Transfer Protocol
    
    No.     Time        Source                Destination           Protocol Info
         41 256.243644  192.168.1.4           204.176.49.2          HTTP     Continuation
    
    Frame 41 (1514 bytes on wire, 1514 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 64, Ack: 1, Len: 1460
    Hypertext Transfer Protocol
    
    No.     Time        Source                Destination           Protocol Info
         42 315.127624  192.168.1.4           204.176.49.2          HTTP     Continuation
    
    Frame 42 (1514 bytes on wire, 1514 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 64, Ack: 1, Len: 1460
    Hypertext Transfer Protocol
    
    No.     Time        Source                Destination           Protocol Info
         43 432.895135  192.168.1.4           204.176.49.2          HTTP     Continuation
    
    Frame 43 (1514 bytes on wire, 1514 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 64, Ack: 1, Len: 1460
    Hypertext Transfer Protocol
    
    No.     Time        Source                Destination           Protocol Info
         44 497.652716  204.176.49.2          192.168.1.4           HTTP     HTTP/1.1 500 Internal Server Error (text/html)
    
    Frame 44 (767 bytes on wire, 767 bytes captured)
    Ethernet II, Src: 00:1e:2a:08:cd:98, Dst: 00:0b:ad:32:12:1f
    Internet Protocol, Src Addr: 204.176.49.2 (204.176.49.2), Dst Addr: 192.168.1.4 (192.168.1.4)
    Transmission Control Protocol, Src Port: http (80), Dst Port: 1157 (1157), Seq: 1, Ack: 64, Len: 713
    Hypertext Transfer Protocol
    Line-based text data: text/html
    
    No.     Time        Source                Destination           Protocol Info
         45 497.653135  204.176.49.2          192.168.1.4           TCP      http > 1157 [FIN, ACK] Seq=714 Ack=64 Win=4299 Len=0
    
    Frame 45 (60 bytes on wire, 60 bytes captured)
    Ethernet II, Src: 00:1e:2a:08:cd:98, Dst: 00:0b:ad:32:12:1f
    Internet Protocol, Src Addr: 204.176.49.2 (204.176.49.2), Dst Addr: 192.168.1.4 (192.168.1.4)
    Transmission Control Protocol, Src Port: http (80), Dst Port: 1157 (1157), Seq: 714, Ack: 64, Len: 0
    
    No.     Time        Source                Destination           Protocol Info
         46 497.653565  192.168.1.4           204.176.49.2          TCP      1157 > http [ACK] Seq=2984 Ack=715 Win=4380 Len=0
    
    Frame 46 (60 bytes on wire, 60 bytes captured)
    Ethernet II, Src: 00:0b:ad:32:12:1f, Dst: 00:1e:2a:08:cd:98
    Internet Protocol, Src Addr: 192.168.1.4 (192.168.1.4), Dst Addr: 204.176.49.2 (204.176.49.2)
    Transmission Control Protocol, Src Port: 1157 (1157), Dst Port: http (80), Seq: 2984, Ack: 715, Len: 0
    
    No.     Time        Source                Destination           Protocol Info
         47 503.004188  204.176.49.2          192.168.1.4           TCP      http > 1157 [RST, ACK] Seq=715 Ack=64 Win=4299 Len=0
    
    Frame 47 (60 bytes on wire, 60 bytes captured)
    Ethernet II, Src: 00:1e:2a:08:cd:98, Dst: 00:0b:ad:32:12:1f
    Internet Protocol, Src Addr: 204.176.49.2 (204.176.49.2), Dst Addr: 192.168.1.4 (192.168.1.4)
    Transmission Control Protocol, Src Port: http (80), Dst Port: 1157 (1157), Seq: 715, Ack: 64, Len: 0
    
     

Share This Page