TiVo Community
TiVo Community
TiVo Community
Go Back   TiVo Community > Main TiVo Forums > TiVo Help Center
TiVo Community
Reply
Forum Jump
 
Thread Tools
Old 02-04-2009, 09:02 PM   #331
gastrof
Look 32' in reverse
 
gastrof's Avatar
 
Join Date: Oct 2003
Location: We would like tin but for the golden glade. Do not take risks that you cannot return to the encapsulation. Margaret has not the stranding.
Posts: 6,734
I just had the same problem this weekend past.

My Series 1 machines are unsubbed, so the only reason I occasionally have them call in is to fix clock drift.

A short while back I'd gone thru Guided Setup again with one of them, setting it for cable and satellite so I could use the work-around and get the TiVo to record off a digital converter box along with cable. This also updated my cable channel lineup since it'd changed a little over the last few months.

This past weekend I decided to reset the clocks on both but had trouble with the cable-only machine. Took me maybe five attempts to finally get it done. In between there were repeated cases of "Service Not Available" or "Call Interrupted". (In the process, I'd tried a reboot, and then switched from just forcing a call to doing Guided Setup all over again, so's to update the cable lineup on that one too.)

Odd thing was that the machine with the digital box reset its clock fine, first attempt.

It was the cable-only machine I had this problem with, then it suddenly worked.

Glad to see that I'm not the only one having this problem, but I don't like it.

As for the question about this being possibly "sinister", hey, it's business. Not all that out of the realm of possibility.
__________________
Crisp binoculars on a Wednesday.
gastrof is offline   Reply With Quote
Old 02-04-2009, 09:10 PM   #332
joeysmith
Registered User
 
joeysmith's Avatar
 
Join Date: Jan 2002
Posts: 95
Quote:
Originally Posted by mec1991 View Post
Calls 18, 19, + 20 all successful with # 19 downloading the new day's guide data.

I think this really is fixed.

But I hope others will chime in this evening with similar results. Good luck to all.
can you give us the area code or pop you are using? still not working from what i can see...
joeysmith is offline   Reply With Quote
Old 02-04-2009, 09:22 PM   #333
joeysmith
Registered User
 
joeysmith's Avatar
 
Join Date: Jan 2002
Posts: 95
as i suspected, the fix is not at all locations. on a hunch i tried good ole '818' clear across the country and got through to the download. it's importing now...
joeysmith is offline   Reply With Quote
Old 02-04-2009, 09:51 PM   #334
jeffw_00
Registered User
 
Join Date: Sep 2000
Posts: 662
818?
jeffw_00 is offline   Reply With Quote
Old 02-04-2009, 09:58 PM   #335
joeysmith
Registered User
 
joeysmith's Avatar
 
Join Date: Jan 2002
Posts: 95
yes i used the 818 area code (remember i was stuck in guided setup). i figured somewhere on the west coast was probably going to work and an LA areacode first popped into my mind.

i'm gonna let it build the guide database then reboot it to see if that clears up the dhcp issue for my turbonet.

Last edited by joeysmith : 02-04-2009 at 10:10 PM.
joeysmith is offline   Reply With Quote
Old 02-04-2009, 11:15 PM   #336
badcrc
Thread Killer
 
Join Date: Aug 2000
Location: Bremerton WA
Posts: 165
Definitely not fixed. I looked at my 91 hour S1 with the external modem and it hasn't had success since Jan 30. I forced a daily call and after it got to "Connecting..." it sat there for a good 5+ minutes, modem lights were solid and didn't flash until it disconnected with "Failed. Service Unavailable." Looked at my 163 hour S1 and it hasn't had success since Feb 2. I forced a daily call on that with the same results. No point in trying the 93 hour, tivo needs to get this fixed.

I wonder how many of us are using standard phone lines? I forgot I switched to phone service through my cable company about 6 months ago...but all three tivos worked fine until December.
__________________
Three TiVo HDR112 Series 1 with lifetime
163 hours, 93 hours, 91 hours.

Last edited by badcrc : 02-05-2009 at 04:00 PM.
badcrc is offline   Reply With Quote
Old 02-05-2009, 05:09 AM   #337
joeysmith
Registered User
 
joeysmith's Avatar
 
Join Date: Jan 2002
Posts: 95
dialing into an 818 dial in number did the trick for me (818 450 1705 which i think is burbank). maybe some of the others having trouble could try. FWIW i am on FIOS so i'm not on copper anymore but i know that modem dialups work. VOIP is another matter, although if it had been working before, it should work now.

unfortunately my turbonet still isn't acquiring an ip address. don't know if the /var/logs issue has anything to do with that. i still don't have my null modem adapter so can't tty into the box to see what's going on. not ready to pull the drive yet...
joeysmith is offline   Reply With Quote
Old 02-05-2009, 05:09 AM   #338
dbranco
Registered User
 
dbranco's Avatar
 
Join Date: Nov 2003
Posts: 624
nope, not fixed here either. Yesterday took 6 tries (with four "Service unavailable" and two "Call Interrupted") before the 7th finally finished downloading and completing.
dbranco is offline   Reply With Quote
Old 02-05-2009, 05:26 AM   #339
ciper
Registered User
 
Join Date: Nov 2004
Posts: 2,010
Although I believe this issue has nothing to do with the phone connection,,,

IIRC TiVo uses UUNet and QWest for dial up. Perhaps some of you should try numbers from each provider and see if there is any difference?


This page may help some of you
http://www3.tivo.com/tivo-misc/popfinder.do
ciper is offline   Reply With Quote
Old 02-05-2009, 06:41 AM   #340
mec1991
Cranky old coot
 
mec1991's Avatar
 
Join Date: Nov 2004
Location: Back home where I belong
Posts: 659
Quote:
Originally Posted by joeysmith View Post
can you give us the area code or pop you are using? still not working from what i can see...
Area code 602 Phoenix
local number is 605-1880

Still working perfectly this morning.

My only forced call today got a small data update.

Maybe the fix is being tested and or rolled out in different areas of the country?
mec1991 is offline   Reply With Quote
Old 02-05-2009, 06:50 AM   #341
mec1991
Cranky old coot
 
mec1991's Avatar
 
Join Date: Nov 2004
Location: Back home where I belong
Posts: 659
Question for those still having failures

Did you PM Jerry with your TSN when he asked for them last week (or whenever it was)? Not sure if there is any connection, just curious. I did and my machine (or area code) is working perfectly now.
mec1991 is offline   Reply With Quote
Old 02-05-2009, 06:53 AM   #342
data_raider
Registered User
 
Join Date: Feb 2009
Location: Virginia
Posts: 5
Not fixed for me as well. Tried about 9 times last night and got different responses. The test dial worked ok, the dial in to find a different number worked, but not the forced call for program update. I will try a different area code tonight to see if that has any change.
data_raider is offline   Reply With Quote
Old 02-05-2009, 08:01 AM   #343
dbranco
Registered User
 
dbranco's Avatar
 
Join Date: Nov 2003
Posts: 624
I didn't give him my TSN because my machine doesn't fail all the time, and (with babysitting) I am up-to-date on the Guide data.
dbranco is offline   Reply With Quote
Old 02-05-2009, 09:33 AM   #344
joeysmith
Registered User
 
joeysmith's Avatar
 
Join Date: Jan 2002
Posts: 95
Quote:
Originally Posted by ciper View Post
Although I believe this issue has nothing to do with the phone connection,,,

IIRC TiVo uses UUNet and QWest for dial up. Perhaps some of you should try numbers from each provider and see if there is any difference?


This page may help some of you
http://www3.tivo.com/tivo-misc/popfinder.do
i had tried a half dozen calls to various pops in the NY area none of which worked. i tried the one that got through the handshakes last night but it failed again with "interrupted". when i switched to areacode 818, the guided setup call went through without a hitch. it then proceeded to dial in for the data download, again without a hitch. i have guide data to next week now. this is purely empirical deduction that some of the pops are working. i'll try the phoenix number when i have a chance.
joeysmith is offline   Reply With Quote
Old 02-05-2009, 12:17 PM   #345
TiVoJerry
TiVo Field Trials PM
 
TiVoJerry's Avatar
 
Join Date: Jul 2005
Location: Alviso, CA
Posts: 1,511
Please correct me if I'm wrong, but I'm looking at this as a "service unavailable" issue only. If a unit connects but the call is interrupted, I currently am of the opinion that this is another problem. If I'm incorrect, it's going to be a lot harder to separate out those who are having normal connection issues outside of our control.

If I am correct, I'd rather people PM me their S1 TSN even if it connects occasionally. If you are truly experiencing this issue, I could get logs from your unit. If you have sent me your TSN and occasionally connected and believe you have this issue, please ping me with an update so I can have someone focus on your logs.
__________________
Jerry
TiVo Field Trials Program Manager
Grillmeister

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
TiVoJerry is offline   Reply With Quote
Old 02-05-2009, 12:27 PM   #346
dbranco
Registered User
 
dbranco's Avatar
 
Join Date: Nov 2003
Posts: 624
Jerry, there are definitely two separate issues here which started occurring simultaneously (and persistently) back in December. Hopefully, when the Service Unavailable issue is solved, it will also solve the Call Interrupted issue. If not, then I hope you will continue to help us figure out what is going on with that issue.

Once I get home this afternoon I will send you my S1 TSN, which gets Service Unavailable quite a lot.
dbranco is offline   Reply With Quote
Old 02-05-2009, 01:18 PM   #347
bittmann
Registered User
 
Join Date: Apr 2005
Posts: 57
I'm not sure that it's actually two separate issues....in my case, I can get either "service unavailable" OR "call interrupted", depending how far along in the communication I can get before the far end stops talking back to me. (Once I even got an error about "retrieving Account Status", IIRC). Simply re-submitting the call again (and again, and again) has SO FAR led to an eventual ability to download data.

This happens to me on dialup or via TurboNet, with dialup seemingly being more reliable than TurboNet, but I don't know why that would be.

This is a bit of a snyopsis of what I'm noting in my network dumps -- sure looks like it's a problem to me:

First, we connect.. This end is natted at 10.10.10.160. The TiVo server end is 204.176.49.2:
Quote:
19:45:33.731518 IP 10.10.10.160.1308 > 204.176.49.2.80: S 1441494951:1441494951(0) win 512 <mss 1460>
19:45:33.796234 IP 204.176.49.2.80 > 10.10.10.160.1308: S 359220725:359220725(0) ack 1441494952 win 0 <mss 1460>
19:45:33.796978 IP 10.10.10.160.1308 > 204.176.49.2.80: . ack 1 win 1460
19:45:33.861840 IP 204.176.49.2.80 > 10.10.10.160.1308: . ack 1 win 4356
We're all nice and connected . Now, my unit announces that it intends to POST 2694 bytes to mlog.cgi on the TiVo server:

Quote:
19:45:33.862261 IP 10.10.10.160.1308 > 204.176.49.2.80: P 1:63(62) ack 1 win 4380
Followed by the first data packet:

Quote:
19:45:33.862894 IP 10.10.10.160.1308 > 204.176.49.2.80: . 63:1523(1460) ack 1 win 4380
And an acknowledgment back from the TiVo Server:
Quote:
19:45:34.032843 IP 204.176.49.2.80 > 10.10.10.160.1308: . ack 63 win 4418
So my TiVo sends the next data packet:

Quote:
19:45:34.033769 IP 10.10.10.160.1308 > 204.176.49.2.80: P 1523:2757(1234) ack 1 win 4380
And receives an acknowledgment from TiVo. For the first data packet again. (??)

Quote:
19:45:34.127316 IP 204.176.49.2.80 > 10.10.10.160.1308: . ack 63 win 4418
So the central server didn't see the 2nd packet? OK, something bad happened. We'll re-send---the first data packet again?.

Quote:
19:45:34.391541 IP 10.10.10.160.1308 > 204.176.49.2.80: . 63:1523(1460) ack 1 win 4380
Nothing heard from the central server after 1 second delay. Hmm. Try again:
Quote:
19:45:35.111641 IP 10.10.10.160.1308 > 204.176.49.2.80: . 63:1523(1460) ack 1 win 4380
Still nothing. Re-send that message again...

Quote:
19:45:36.552102 IP 10.10.10.160.1308 > 204.176.49.2.80: . 63:1523(1460) ack 1 win 4380
No good. Wait a little longer and then try again.
Quote:
19:45:39.431571 IP 10.10.10.160.1308 > 204.176.49.2.80: . 63:1523(1460) ack 1 win 4380
Still no response from the central server? Back off some more and sent that same packet yet AGAIN...you get the drift. We'll try to re-send that packet 4 more times.
Quote:
19:45:45.191580 IP 10.10.10.160.1308 > 204.176.49.2.80: . 63:1523(1460) ack 1 win 4380
19:45:56.711492 IP 10.10.10.160.1308 > 204.176.49.2.80: . 63:1523(1460) ack 1 win 4380
19:46:19.751443 IP 10.10.10.160.1308 > 204.176.49.2.80: . 63:1523(1460) ack 1 win 4380
19:47:05.831338 IP 10.10.10.160.1308 > 204.176.49.2.80: . 63:1523(1460) ack 1 win 4380
Still no response from the TiVo central server? Well, then. Guess we'll just write this off as "bad" and go update the dialin status with "service unavailable". Just to be neighborly (because, obviously, the central server isn't in communication with us), we'll still be good boys and indicate that we're going to drop the HTTP connection:

Quote:
19:48:30.665619 IP 10.10.10.160.1308 > 204.176.49.2.80: F 2757:2757(0) ack 1 win 4380
Whereupon the TiVo central server says "Ok...I'll acknowledge the first packet again.

What??? I thought you'd disconnected already?

Nope--evidently, the central server still THINKS that it's waiting for the first data packet:

Quote:
19:48:30.731319 IP 204.176.49.2.80 > 10.10.10.160.1308: . ack 63 win 4418
Hmph. And the next few times I had variations of the same thing. Eventually, though, success...with nothing changing except "the dumb user simply forced a call again".

Now, mind you, during this entire exchange I had a slow ping running from my network to the TiVo server, and the network was showing up and available for the duration of the "call", so I don't THINK it's a network transport issue (e.g. a bad connection with my ISP or whatever). It sure looks, to me, like the connection is being made, but then the actual transmission of data falls on its face.

But then again, I don't know if that's the case, either. All I know is -- fighting with this will make a fellow grumpy after a while.

BittMann
bittmann is offline   Reply With Quote
Old 02-05-2009, 01:52 PM   #348
kahuja100
Registered User
 
Join Date: Feb 2009
Posts: 4
mec1991-not sure what your problem is but what does me being a first time post have to do with anything??
no i do not expect a free HD Tivo, but i do expect some sort of compensation for a lifetime subscription if tivo is going to discontinue the series 1, and i do not expect a CSR to tell me that my machine is archaic and i have more than got my monies worth.
i do not know why as i clearly dont spend as much time with my tivo as you do, but if my tivo is unplugged from the power source i DO have to go back thru Guided Setup.

and for future- ignore my post, if you have nothing positive to say,

for the others who are contrbuting valid input-

i sent emails to TIVO investor relations and rec'd an email back instantly apologizing and today received a phone message from TIVO, havent had time to call back yet, wanted to check boards for updates first before i call them but will update later.

my tivo has also made daily calls for the past two nights without fail

Last edited by kahuja100 : 02-05-2009 at 02:03 PM.
kahuja100 is offline   Reply With Quote
Old 02-05-2009, 02:12 PM   #349
joeysmith
Registered User
 
joeysmith's Avatar
 
Join Date: Jan 2002
Posts: 95
wow, really strange seeing the ack - retry sequences. typically run into those with high latency / slow links. 204.176.49.2 - is in California. when i dialed into the California pop, the guided setup and data download went without a hitch. could it be the backend ip got reconfigured so that latency becomes a big problem? dialup itself is managed by the hardware for that connection but the WAN ip traffic relies on data buffers etc to keep the data flowing. that would explain the failures from remote dialups and turbonets...
joeysmith is offline   Reply With Quote
Old 02-05-2009, 02:14 PM   #350
joeysmith
Registered User
 
joeysmith's Avatar
 
Join Date: Jan 2002
Posts: 95
Quote:
Originally Posted by kahuja100 View Post
mec1991-not sure what your problem is but what does me being a first time post have to do with anything??
no i do not expect a free HD Tivo, but i do expect some sort of compensation for a lifetime subscription if tivo is going to discontinue the series 1, and i do not expect a CSR to tell me that my machine is archaic and i have more than got my monies worth.
i do not know why as i clearly dont spend as much time with my tivo as you do, but if my tivo is unplugged from the power source i DO have to go back thru Guided Setup.

and for future- ignore my post, if you have nothing positive to say,

for the others who are contrbuting valid input-

i sent emails to TIVO investor relations and rec'd an email back instantly apologizing and today received a phone message from TIVO, havent had time to call back yet, wanted to check boards for updates first before i call them but will update later.

my tivo has also made daily calls for the past two nights without fail
what part of the country are you in? it might be relevant...
joeysmith is offline   Reply With Quote
Old 02-05-2009, 03:00 PM   #351
kahuja100
Registered User
 
Join Date: Feb 2009
Posts: 4
i am SF bay area, i tried various numbers, although cannot guarantee the successful number was one i had not previously tried,
i also dialed the area code even though it is the same area code as mine, i am also about 15 miles from a TIVO office in Santa Clara.

i also PM Tivo Jerry my TSN number so he can look into mine if he has time and maybe figure out what happened.

His help is really appreciated.

also used 510 area code, for Fremont CA, i think one of the Fremont main numbers
kahuja100 is offline   Reply With Quote
Old 02-05-2009, 03:02 PM   #352
mec1991
Cranky old coot
 
mec1991's Avatar
 
Join Date: Nov 2004
Location: Back home where I belong
Posts: 659
Quote:
Originally Posted by kahuja100 View Post
but if my tivo is unplugged from the power source i DO have to go back thru Guided Setup.

and for future- ignore my post, if you have nothing positive to say,
The first sentence in the quote above makes absolutely no sense whatsoever. You do not have to redo GS if the TiVo is unplugged from the power source. If you honestly do have to do so, you have something seriously wrong with your machine.

As for your last sentence, no problemo.
mec1991 is offline   Reply With Quote
Old 02-05-2009, 03:32 PM   #353
joeysmith
Registered User
 
joeysmith's Avatar
 
Join Date: Jan 2002
Posts: 95
Quote:
Originally Posted by kahuja100 View Post
i am SF bay area, i tried various numbers, although cannot guarantee the successful number was one i had not previously tried,
i also dialed the area code even though it is the same area code as mine, i am also about 15 miles from a TIVO office in Santa Clara.

i also PM Tivo Jerry my TSN number so he can look into mine if he has time and maybe figure out what happened.

His help is really appreciated.

also used 510 area code, for Fremont CA, i think one of the Fremont main numbers
network (WAN) latency is a function of distance. the farther you are to the destination the longer it will take for packets to get there. if you can, how about making your tivo dial into NY (212)? i bet it won't work...
joeysmith is offline   Reply With Quote
Old 02-05-2009, 04:09 PM   #354
kahuja100
Registered User
 
Join Date: Feb 2009
Posts: 4
i went to phone connection and changed the phone to 212 area code and used the first one 212 manhattan, did test phone call first, no problem, now made daily call and it is 50% done with downloading information.....still working,
is that what you wanted me to do ?

worked no problem,

the fremont main number i used that is working -ends in 0040, i think it is 510-404-0040

i have a phillips tivo, normal phone line, original internal modem, never hacked or done anything,
the software version is 3.0-01-1-000

Last edited by kahuja100 : 02-05-2009 at 04:42 PM.
kahuja100 is offline   Reply With Quote
Old 02-05-2009, 04:10 PM   #355
badcrc
Thread Killer
 
Join Date: Aug 2000
Location: Bremerton WA
Posts: 165
Quote:
Originally Posted by TiVoJerry View Post
Please correct me if I'm wrong, but I'm looking at this as a "service unavailable" issue only. If a unit connects but the call is interrupted, I currently am of the opinion that this is another problem. If I'm incorrect, it's going to be a lot harder to separate out those who are having normal connection issues outside of our control.
I think it's all the same issue. I can call 10 times and only connect and successfully download 1-2 times. But one call might be "Failed service unavailable" another might be "call interrupted". There was another message about the line (being in use maybe?) when it wasn't. All of these messages seem to be erroneous. From looking at my external modem it looks like after it connects and sometimes stalls for 5+ minutes is one of the times I get "Failed. Service unavailable".

For anyone keeping track, I just did a daily call on my 93 hour and it connected, downloaded, and hung up successfully on the first attempt, but the call seemed to take quite a long time, probably around 10 mins when the last successful call was just a couple days ago...maybe that's normal, I haven't watched a normal daily call in years.
__________________
Three TiVo HDR112 Series 1 with lifetime
163 hours, 93 hours, 91 hours.
badcrc is offline   Reply With Quote
Old 02-05-2009, 04:33 PM   #356
Illusion
Registered User
 
Join Date: Jun 2008
Posts: 26
Service Unavailable and Call Interrupted appear to be same issue.

I have a Phillips Series 1 on copper POTS and get both failures intermittently since December, same as everyone else.

Neighbor has Phillips Series 1 on Fiber using a different dial in number and gets both failures intermittently since December, same as everyone else.

Both units using original internal modems. Calls are not being interrupted on our end.
Illusion is offline   Reply With Quote
Old 02-05-2009, 05:06 PM   #357
bittmann
Registered User
 
Join Date: Apr 2005
Posts: 57
In case it's of any interest, the following represents a followup transaction to what I posted previously, in which the transaction did eventually complete:

Code:
20:44:59.328332 IP 10.10.10.160.1330 > 204.176.49.2.80: S 834984813:834984813(0) win 512 <mss 1460>
20:44:59.392343 IP 204.176.49.2.80 > 10.10.10.160.1330: S 3209843985:3209843985(0) ack 834984814 win 0 <mss 1460>
20:44:59.392659 IP 10.10.10.160.1330 > 204.176.49.2.80: . ack 1 win 1460
20:44:59.456677 IP 204.176.49.2.80 > 10.10.10.160.1330: . ack 1 win 4356
20:44:59.457092 IP 10.10.10.160.1330 > 204.176.49.2.80: P 1:63(62) ack 1 win 4380
20:44:59.457734 IP 10.10.10.160.1330 > 204.176.49.2.80: . 63:1523(1460) ack 1 win 4380
20:44:59.561157 IP 204.176.49.2.80 > 10.10.10.160.1330: . ack 1523 win 5878
20:44:59.561889 IP 10.10.10.160.1330 > 204.176.49.2.80: P 1523:2219(696) ack 1 win 4380
20:44:59.651953 IP 204.176.49.2.80 > 10.10.10.160.1330: P 1:124(123) ack 2219 win 6574
20:44:59.652031 IP 204.176.49.2.80 > 10.10.10.160.1330: F 124:124(0) ack 2219 win 6574
20:44:59.652642 IP 10.10.10.160.1330 > 204.176.49.2.80: . ack 125 win 4380
20:44:59.663663 IP 10.10.10.160.1330 > 204.176.49.2.80: F 2219:2219(0) ack 125 win 4380
20:44:59.728720 IP 204.176.49.2.80 > 10.10.10.160.1330: . ack 2220 win 6574
20:44:59.767741 IP 10.10.10.160.1331 > 204.176.49.2.80: S 3373314190:3373314190(0) win 512 <mss 1460>
20:44:59.831258 IP 204.176.49.2.80 > 10.10.10.160.1331: S 3881258800:3881258800(0) ack 3373314191 win 4356 <mss 1460>
20:44:59.831570 IP 10.10.10.160.1331 > 204.176.49.2.80: . ack 1 win 1460
20:44:59.836741 IP 10.10.10.160.1331 > 204.176.49.2.80: P 1:394(393) ack 1 win 4380
20:45:00.010769 IP 204.176.49.2.80 > 10.10.10.160.1331: . ack 394 win 4749
20:45:00.036222 IP 204.176.49.2.80 > 10.10.10.160.1331: P 1:147(146) ack 394 win 4749
20:45:00.040146 IP 204.176.49.2.80 > 10.10.10.160.1331: FP 147:196(49) ack 394 win 4749
20:45:00.040598 IP 10.10.10.160.1331 > 204.176.49.2.80: . ack 197 win 4380
20:45:00.045650 IP 10.10.10.160.1331 > 204.176.49.2.80: F 394:394(0) ack 197 win 4380
20:45:00.109157 IP 204.176.49.2.80 > 10.10.10.160.1331: . ack 395 win 4749
20:45:00.128103 IP 10.10.10.160.1332 > 204.176.49.2.80: S 284760962:284760962(0) win 512 <mss 1460>
20:45:00.193904 IP 204.176.49.2.80 > 10.10.10.160.1332: S 3549527618:3549527618(0) ack 284760963 win 4356 <mss 1460>
20:45:00.194343 IP 10.10.10.160.1332 > 204.176.49.2.80: . ack 1 win 1460
20:45:00.231099 IP 10.10.10.160.1332 > 204.176.49.2.80: . 1:1461(1460) ack 1 win 4380
20:45:00.231648 IP 10.10.10.160.1332 > 204.176.49.2.80: . 1461:2921(1460) ack 1 win 4380
20:45:00.329832 IP 204.176.49.2.80 > 10.10.10.160.1332: . ack 1461 win 5816
20:45:00.331193 IP 10.10.10.160.1332 > 204.176.49.2.80: . 2921:4381(1460) ack 1 win 4380
20:45:00.331749 IP 10.10.10.160.1332 > 204.176.49.2.80: . 4381:5841(1460) ack 1 win 4380
20:45:00.430454 IP 204.176.49.2.80 > 10.10.10.160.1332: . ack 4381 win 8736
20:45:00.431891 IP 10.10.10.160.1332 > 204.176.49.2.80: . 5841:7301(1460) ack 1 win 4380
20:45:00.432107 IP 10.10.10.160.1332 > 204.176.49.2.80: P 7301:8096(795) ack 1 win 4380
20:45:00.432724 IP 10.10.10.160.1332 > 204.176.49.2.80: . 8096:9556(1460) ack 1 win 4380
20:45:00.530939 IP 204.176.49.2.80 > 10.10.10.160.1332: . ack 7301 win 11656
20:45:00.531903 IP 10.10.10.160.1332 > 204.176.49.2.80: P 9556:10683(1127) ack 1 win 4380
20:45:00.590077 IP 204.176.49.2.80 > 10.10.10.160.1332: . ack 9556 win 13911
20:45:00.722125 IP 204.176.49.2.80 > 10.10.10.160.1332: . ack 10683 win 15038
20:45:00.947071 IP 204.176.49.2.80 > 10.10.10.160.1332: P 1:127(126) ack 10683 win 15038
20:45:00.950930 IP 10.10.10.160.1332 > 204.176.49.2.80: . ack 127 win 4380
20:45:00.956956 IP 204.176.49.2.80 > 10.10.10.160.1332: . 127:1579(1452) ack 10683 win 15038
20:45:00.968672 IP 204.176.49.2.80 > 10.10.10.160.1332: FP 1579:2400(821) ack 10683 win 15038
20:45:00.969857 IP 10.10.10.160.1332 > 204.176.49.2.80: . ack 2401 win 5840
20:45:00.994877 IP 10.10.10.160.1332 > 204.176.49.2.80: F 10683:10683(0) ack 2401 win 5840
20:45:01.061176 IP 204.176.49.2.80 > 10.10.10.160.1332: . ack 10684 win 15038
20:45:01.651638 IP 10.10.10.160.123 > 204.176.49.10.123: NTPv3, Client, length 48
20:45:01.719470 IP 204.176.49.10.123 > 10.10.10.160.123: NTPv3, Server, length 48
20:45:01.721486 IP 10.10.10.160.123 > 204.176.49.10.123: NTPv3, Client, length 48
20:45:01.786482 IP 204.176.49.10.123 > 10.10.10.160.123: NTPv3, Server, length 48
20:45:01.787675 IP 10.10.10.160.123 > 204.176.49.10.123: NTPv3, Client, length 48
20:45:01.851619 IP 10.10.10.160.123 > 204.176.49.11.123: NTPv3, Client, length 48
20:45:01.853659 IP 204.176.49.10.123 > 10.10.10.160.123: NTPv3, Server, length 48
20:45:01.855061 IP 10.10.10.160.123 > 204.176.49.10.123: NTPv3, Client, length 48
20:45:01.918675 IP 204.176.49.11.123 > 10.10.10.160.123: NTPv3, Server, length 48
20:45:01.919790 IP 10.10.10.160.123 > 204.176.49.11.123: NTPv3, Client, length 48
20:45:01.922509 IP 204.176.49.10.123 > 10.10.10.160.123: NTPv3, Server, length 48
20:45:01.985546 IP 204.176.49.11.123 > 10.10.10.160.123: NTPv3, Server, length 48
20:45:01.986585 IP 10.10.10.160.123 > 204.176.49.11.123: NTPv3, Client, length 48
20:45:02.053070 IP 10.10.10.160.123 > 204.176.49.12.123: NTPv3, Client, length 48
20:45:02.055362 IP 204.176.49.11.123 > 10.10.10.160.123: NTPv3, Server, length 48
20:45:02.056719 IP 10.10.10.160.123 > 204.176.49.11.123: NTPv3, Client, length 48
20:45:02.119854 IP 204.176.49.12.123 > 10.10.10.160.123: NTPv3, Server, length 48
20:45:02.121748 IP 10.10.10.160.123 > 204.176.49.12.123: NTPv3, Client, length 48
20:45:02.123561 IP 204.176.49.11.123 > 10.10.10.160.123: NTPv3, Server, length 48
20:45:02.186746 IP 204.176.49.12.123 > 10.10.10.160.123: NTPv3, Server, length 48
20:45:02.188952 IP 10.10.10.160.123 > 204.176.49.12.123: NTPv3, Client, length 48
20:45:02.255801 IP 204.176.49.12.123 > 10.10.10.160.123: NTPv3, Server, length 48
20:45:02.256698 IP 10.10.10.160.123 > 204.176.49.12.123: NTPv3, Client, length 48
20:45:02.322767 IP 204.176.49.12.123 > 10.10.10.160.123: NTPv3, Server, length 48
20:45:02.584356 IP 10.10.10.160.1333 > 204.176.49.7.80: S 364265320:364265320(0) win 512 <mss 1460>
20:45:02.647803 IP 204.176.49.7.80 > 10.10.10.160.1333: S 3446690337:3446690337(0) ack 364265321 win 4356 <mss 1460>
20:45:02.648333 IP 10.10.10.160.1333 > 204.176.49.7.80: . ack 1 win 1460
20:45:02.658785 IP 10.10.10.160.1333 > 204.176.49.7.80: P 1:109(108) ack 1 win 4380
20:45:02.669594 IP 10.10.10.160.1333 > 204.176.49.7.80: P 109:1012(903) ack 1 win 4380
20:45:02.754237 IP 204.176.49.7.80 > 10.10.10.160.1333: . ack 1012 win 5367
20:45:02.811504 IP 204.176.49.7.80 > 10.10.10.160.1333: P 1:141(140) ack 1012 win 5367
20:45:02.813387 IP 204.176.49.7.80 > 10.10.10.160.1333: F 141:141(0) ack 1012 win 5367
20:45:02.813800 IP 10.10.10.160.1333 > 204.176.49.7.80: . ack 142 win 4380
20:45:02.837473 IP 10.10.10.160.1333 > 204.176.49.7.80: F 1012:1012(0) ack 142 win 4380
20:45:02.904094 IP 204.176.49.7.80 > 10.10.10.160.1333: . ack 1013 win 5367
20:45:02.967861 IP 10.10.10.160.1334 > 204.176.49.35.8080: S 3545318887:3545318887(0) win 512 <mss 1460>
20:45:03.034367 IP 204.176.49.35.8080 > 10.10.10.160.1334: S 496350209:496350209(0) ack 3545318888 win 5840 <mss 1460>
20:45:03.034818 IP 10.10.10.160.1334 > 204.176.49.35.8080: . ack 1 win 1460
20:45:03.038278 IP 10.10.10.160.1334 > 204.176.49.35.8080: P 1:155(154) ack 1 win 4380
20:45:03.109837 IP 204.176.49.35.8080 > 10.10.10.160.1334: . ack 155 win 6432
20:45:03.111123 IP 204.176.49.35.8080 > 10.10.10.160.1334: P 1:237(236) ack 155 win 6432
20:45:03.120939 IP 10.10.10.160.1334 > 204.176.49.35.8080: . ack 237 win 4380
20:45:03.121290 IP 204.176.49.35.8080 > 10.10.10.160.1334: . 237:1689(1452) ack 155 win 6432
20:45:03.188424 IP 204.176.49.35.8080 > 10.10.10.160.1334: FP 3141:3369(228) ack 155 win 6432
20:45:03.189037 IP 10.10.10.160.1334 > 204.176.49.35.8080: . ack 1689 win 4380
20:45:03.198035 IP 204.176.49.35.8080 > 10.10.10.160.1334: P 1689:3141(1452) ack 155 win 6432
20:45:03.199019 IP 10.10.10.160.1334 > 204.176.49.35.8080: . ack 3370 win 5840
20:45:03.200705 IP 10.10.10.160.1334 > 204.176.49.35.8080: F 155:155(0) ack 3370 win 5840
20:45:03.266905 IP 204.176.49.35.8080 > 10.10.10.160.1334: . ack 156 win 6432
20:45:03.292863 IP 10.10.10.160.1335 > 204.176.49.35.8080: S 3228833785:3228833785(0) win 512 <mss 1460>
20:45:03.359621 IP 204.176.49.35.8080 > 10.10.10.160.1335: S 506070431:506070431(0) ack 3228833786 win 5840 <mss 1460>
20:45:03.360115 IP 10.10.10.160.1335 > 204.176.49.35.8080: . ack 1 win 1460
20:45:03.364582 IP 10.10.10.160.1335 > 204.176.49.35.8080: P 1:159(158) ack 1 win 4380
20:45:03.432329 IP 204.176.49.35.8080 > 10.10.10.160.1335: . ack 159 win 6432
20:45:03.434410 IP 204.176.49.35.8080 > 10.10.10.160.1335: P 1:236(235) ack 159 win 6432
20:45:03.436311 IP 204.176.49.35.8080 > 10.10.10.160.1335: P 236:510(274) ack 159 win 6432
20:45:03.436821 IP 10.10.10.160.1335 > 204.176.49.35.8080: . ack 510 win 4380
20:45:03.438460 IP 204.176.49.35.8080 > 10.10.10.160.1335: F 510:510(0) ack 159 win 6432
20:45:03.438825 IP 10.10.10.160.1335 > 204.176.49.35.8080: . ack 511 win 4380
20:45:03.445188 IP 10.10.10.160.1335 > 204.176.49.35.8080: F 159:159(0) ack 511 win 4380
20:45:03.509208 IP 204.176.49.35.8080 > 10.10.10.160.1335: . ack 160 win 6432
20:45:03.530096 IP 10.10.10.160.1336 > 204.176.49.35.8080: S 2649587329:2649587329(0) win 512 <mss 1460>
20:45:03.598117 IP 204.176.49.35.8080 > 10.10.10.160.1336: S 501889219:501889219(0) ack 2649587330 win 5840 <mss 1460>
20:45:03.598919 IP 10.10.10.160.1336 > 204.176.49.35.8080: . ack 1 win 1460
20:45:03.616257 IP 10.10.10.160.1336 > 204.176.49.35.8080: P 1:149(148) ack 1 win 4380
20:45:03.684651 IP 204.176.49.35.8080 > 10.10.10.160.1336: . ack 149 win 6432
20:45:03.688641 IP 204.176.49.35.8080 > 10.10.10.160.1336: P 1:278(277) ack 149 win 6432
20:45:03.688723 IP 204.176.49.35.8080 > 10.10.10.160.1336: F 278:278(0) ack 149 win 6432
20:45:03.689477 IP 10.10.10.160.1336 > 204.176.49.35.8080: . ack 279 win 4380
20:45:03.694954 IP 10.10.10.160.1336 > 204.176.49.35.8080: F 149:149(0) ack 279 win 4380
20:45:03.759479 IP 204.176.49.35.8080 > 10.10.10.160.1336: . ack 150 win 6432
20:45:03.792464 IP 10.10.10.160.1337 > 204.176.49.35.8080: S 4131561977:4131561977(0) win 512 <mss 1460>
20:45:03.858082 IP 204.176.49.35.8080 > 10.10.10.160.1337: S 490770639:490770639(0) ack 4131561978 win 5840 <mss 1460>
20:45:03.858527 IP 10.10.10.160.1337 > 204.176.49.35.8080: . ack 1 win 1460
20:45:03.866604 IP 10.10.10.160.1337 > 204.176.49.35.8080: P 1:153(152) ack 1 win 4380
20:45:03.934972 IP 204.176.49.35.8080 > 10.10.10.160.1337: . ack 153 win 6432
20:45:03.936969 IP 204.176.49.35.8080 > 10.10.10.160.1337: P 1:236(235) ack 153 win 6432
20:45:03.939080 IP 204.176.49.35.8080 > 10.10.10.160.1337: P 236:510(274) ack 153 win 6432
20:45:03.939583 IP 10.10.10.160.1337 > 204.176.49.35.8080: . ack 510 win 4380
20:45:03.941155 IP 204.176.49.35.8080 > 10.10.10.160.1337: F 510:510(0) ack 153 win 6432
20:45:03.941595 IP 10.10.10.160.1337 > 204.176.49.35.8080: . ack 511 win 4380
20:45:03.950906 IP 10.10.10.160.1337 > 204.176.49.35.8080: F 153:153(0) ack 511 win 4380
20:45:04.013727 IP 204.176.49.35.8080 > 10.10.10.160.1337: . ack 154 win 6432
20:45:04.039671 IP 10.10.10.160.1338 > 204.176.49.35.8080: S 840035073:840035073(0) win 512 <mss 1460>
20:45:04.106439 IP 204.176.49.35.8080 > 10.10.10.160.1338: S 505411972:505411972(0) ack 840035074 win 5840 <mss 1460>
20:45:04.106837 IP 10.10.10.160.1338 > 204.176.49.35.8080: . ack 1 win 1460
20:45:04.110203 IP 10.10.10.160.1338 > 204.176.49.35.8080: P 1:157(156) ack 1 win 4380
20:45:04.177386 IP 204.176.49.35.8080 > 10.10.10.160.1338: . ack 157 win 6432
20:45:04.181303 IP 204.176.49.35.8080 > 10.10.10.160.1338: P 1:236(235) ack 157 win 6432
20:45:04.183555 IP 204.176.49.35.8080 > 10.10.10.160.1338: P 236:705(469) ack 157 win 6432
20:45:04.183632 IP 204.176.49.35.8080 > 10.10.10.160.1338: F 705:705(0) ack 157 win 6432
20:45:04.184180 IP 10.10.10.160.1338 > 204.176.49.35.8080: . ack 705 win 4380
20:45:04.184332 IP 10.10.10.160.1338 > 204.176.49.35.8080: . ack 706 win 4380
20:45:04.187582 IP 10.10.10.160.1338 > 204.176.49.35.8080: F 157:157(0) ack 706 win 4380
20:45:04.254261 IP 204.176.49.35.8080 > 10.10.10.160.1338: . ack 158 win 6432
20:45:04.270262 IP 10.10.10.160.1339 > 204.176.49.35.8080: S 1286076821:1286076821(0) win 512 <mss 1460>
20:45:04.337033 IP 204.176.49.35.8080 > 10.10.10.160.1339: S 506871121:506871121(0) ack 1286076822 win 5840 <mss 1460>
20:45:04.337454 IP 10.10.10.160.1339 > 204.176.49.35.8080: . ack 1 win 1460
20:45:04.341051 IP 10.10.10.160.1339 > 204.176.49.35.8080: P 1:161(160) ack 1 win 4380
20:45:04.408042 IP 204.176.49.35.8080 > 10.10.10.160.1339: . ack 161 win 6432
20:45:04.409987 IP 204.176.49.35.8080 > 10.10.10.160.1339: P 1:236(235) ack 161 win 6432
20:45:04.410900 IP 10.10.10.160.1339 > 204.176.49.35.8080: . ack 236 win 4380
20:45:04.412294 IP 204.176.49.35.8080 > 10.10.10.160.1339: P 236:510(274) ack 161 win 6432
20:45:04.414128 IP 204.176.49.35.8080 > 10.10.10.160.1339: F 510:510(0) ack 161 win 6432
20:45:04.414507 IP 10.10.10.160.1339 > 204.176.49.35.8080: . ack 511 win 4380
20:45:04.416342 IP 10.10.10.160.1339 > 204.176.49.35.8080: F 161:161(0) ack 511 win 4380
20:45:04.482999 IP 204.176.49.35.8080 > 10.10.10.160.1339: . ack 162 win 6432
20:45:04.646524 IP 10.10.10.160.1340 > 204.176.49.2.80: S 1914150771:1914150771(0) win 512 <mss 1460>
20:45:04.709626 IP 204.176.49.2.80 > 10.10.10.160.1340: S 2013096674:2013096674(0) ack 1914150772 win 4356 <mss 1460>
20:45:04.710033 IP 10.10.10.160.1340 > 204.176.49.2.80: . ack 1 win 1460
20:45:04.719408 IP 10.10.10.160.1340 > 204.176.49.2.80: P 1:63(62) ack 1 win 4380
20:45:04.726649 IP 10.10.10.160.1340 > 204.176.49.2.80: . 63:1523(1460) ack 1 win 4380
20:45:04.827839 IP 204.176.49.2.80 > 10.10.10.160.1340: . ack 1523 win 5878
20:45:04.828338 IP 10.10.10.160.1340 > 204.176.49.2.80: P 1523:1697(174) ack 1 win 4380
20:45:04.904800 IP 204.176.49.2.80 > 10.10.10.160.1340: P 1:143(142) ack 1697 win 6052
20:45:04.904924 IP 204.176.49.2.80 > 10.10.10.160.1340: F 143:143(0) ack 1697 win 6052
20:45:04.905421 IP 10.10.10.160.1340 > 204.176.49.2.80: . ack 144 win 4380
20:45:04.910154 IP 10.10.10.160.1340 > 204.176.49.2.80: F 1697:1697(0) ack 144 win 4380
20:45:04.975836 IP 204.176.49.2.80 > 10.10.10.160.1340: . ack 1698 win 6052
20:45:16.449488 IP 204.176.49.2.80 > 10.10.10.160.1330: R 125:125(0) ack 2220 win 0
20:45:16.449923 IP 204.176.49.2.80 > 10.10.10.160.1331: R 197:197(0) ack 395 win 0
20:45:18.452466 IP 204.176.49.2.80 > 10.10.10.160.1332: R 2401:2401(0) ack 10684 win 0
20:45:18.453524 IP 204.176.49.7.80 > 10.10.10.160.1333: R 142:142(0) ack 1013 win 0
20:45:20.454681 IP 204.176.49.35.8080 > 10.10.10.160.1337: R 511:511(0) ack 154 win 0
20:45:20.454991 IP 204.176.49.35.8080 > 10.10.10.160.1336: R 279:279(0) ack 150 win 0
20:45:20.456083 IP 204.176.49.35.8080 > 10.10.10.160.1339: R 511:511(0) ack 162 win 0
20:45:20.456401 IP 204.176.49.35.8080 > 10.10.10.160.1338: R 706:706(0) ack 158 win 0
20:45:20.456732 IP 204.176.49.35.8080 > 10.10.10.160.1335: R 511:511(0) ack 160 win 0
20:45:20.457027 IP 204.176.49.35.8080 > 10.10.10.160.1334: R 3370:3370(0) ack 156 win 0
20:45:20.458106 IP 204.176.49.2.80 > 10.10.10.160.1340: R 144:144(0) ack 1698 win 0
Notice how the central server did respond with the expected ACKs in a reasonable amount of time. The data transfer happened acceptably quickly, and we got on down the road without issue. All in all, an unremarkable transaction.

Only difference between this transaction and the one that I posted earlier was about an hour. Nothing had been reset, restarted, or otherwise tweaked.

I did email TivoJerry with a tcpdump of the network traffic in case it was of any help. I hope that it's of some help.

After year and years and years of boring, rock-solid TurboNet daily calls, it cqme as quite a shock that my TiVo will fail enough times in a row to start complaining about running out of guide data.

BittMann
bittmann is offline   Reply With Quote
Old 02-05-2009, 06:01 PM   #358
erniebert
Registered User
 
Join Date: Jan 2009
Posts: 3
I'll send you mine!

TivoJerry -

Here's an idea

I can ship you my unit so you can have everyone there look at it!!!

Sony SVR2000.

Isn't this the best and fastest way to debug it?

It would prove once and for all that there is a issue!

Let me know.

Ernie
erniebert is offline   Reply With Quote
Old 02-05-2009, 06:57 PM   #359
joeysmith
Registered User
 
joeysmith's Avatar
 
Join Date: Jan 2002
Posts: 95
Quote:
Originally Posted by kahuja100 View Post
i went to phone connection and changed the phone to 212 area code and used the first one 212 manhattan, did test phone call first, no problem, now made daily call and it is 50% done with downloading information.....still working,
is that what you wanted me to do ?

worked no problem,

the fremont main number i used that is working -ends in 0040, i think it is 510-404-0040

i have a phillips tivo, normal phone line, original internal modem, never hacked or done anything,
the software version is 3.0-01-1-000
duh, it worked for me too and so does another local area code. something seems to be going right and OMG my turbonet card had simply come loose and is working now (i had jimmied it a bit last time which probably unseated it instead of seating it). it's all good from my end!

Last edited by joeysmith : 02-05-2009 at 07:24 PM.
joeysmith is offline   Reply With Quote
Old 02-05-2009, 07:44 PM   #360
bittmann
Registered User
 
Join Date: Apr 2005
Posts: 57
I don't know if it's going right, or if it's just chance right now. I can have 5 good calls in a row, then 10 bad calls in a row, with seemingly no way to anticipate what is going to happen.

After seeing your post, I decided to kick off another dial, and while it looked good at first (went through connecting, to setting clock, to downloading), I was actually able to do what APPEARS to be a complete transfer with "whatever it is that my TiVo talks to" on port 8080, but at the end of the transmission there is additional traffic on port 80 (the logs of this traffic looks like the traffic from the first port 80 transfers--uploads from my machine to the Mothership?), and that last transmission failed. "interrupted" it says.

Next try won't get past "connecting".

I'm going to bang on this until it finishes...which I'll *bet* it will soon. And then there is a good chance that the next half-dozen downloads will complete normally.

BittMann
bittmann is offline   Reply With Quote
Reply
Forum Jump




Thread Tools


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Advertisements

TiVo Community
Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
vBulletin Skins by: Relivo Media

(C) 2013 Magenium Solutions - All Rights Reserved. No information may be posted elsewhere without written permission.
TiVoŽ is a registered trademark of TiVo Inc. This site is not owned or operated by TiVo Inc.
All times are GMT -5. The time now is 12:43 AM.
OUR NETWORK: MyOpenRouter | TechLore | SansaCommunity | RoboCommunity | MediaSmart Home | Explore3DTV | Dijit Community | DVR Playground |