NZ Emulator clock running fast?

[chis]

My Tivo's clock is fast. I reset it back to correct, only to find a few days later that it's a few minutes fast again. I seem to remember that the Tivo take's its clock from the emulator, and if that's right and the emulator's clock is a bit fast that would explain everything.

I'm connected to the 210.48.107.133:8000 emulator using the NZ 1.5 software.

Anyone else got the same issue?

[DJC]

You'll need to have a quick check of your logs for ntp issues.

The emulatator is locked on ntp sources. I've had a quick benchmark of its current time against other stratum 1 sources on the internet and it is as right as they come.

I personally don't have time issues with my tivo, the timing has always been spot on.

[Darren King]

As DJC said, check your logs and/or network.

I upgraded to a Billion 7402VGP a while ago and wondered why I was having time drift. Turns out I needed to open port 37 which by default is not with the inbuilt firewall in the Billion. May be a similar issue with you?

Cheers

[Bonzo]

I have noticed that my Tivo's clock has been between 1 and 2 minutes fast (compared to Sky at least) for the last week or so. Its been clipping the ends of programs, where it has something else to record straight after? I'll check the logs for signs of an NTP issue, but does anyone know what I should do if I find one?

Also I haven't had to look at the tivo's firewall before? how do I check / change port 37?

Thanks

[Darren King]

The TiVo does not have a firewall. I was talking about my router and that I had problems with time after I installed it. Sorry if my post was misleading.

[zollymonsta]

I would compare the time on your Sky box to a known reliable time source (ie: a time server). Perhaps Sky's time is out.

[DavidClarke]

whip up a connection to the prompt on the Tivo and type in

[TiVo [p3] ~]# /bin/ntpdate -v -v -v -s 210.48.107.133

should get something like :
/bin/ntpdate: invalid option -- s
Our postcode is 02113. Found matching timezone Pacific/Auckland
Offset 43200 for timezone NZST, daylight saving is 0
Connecting to time server 210.48.107.133
Setting the local time to Wed May 31 20:32:35 2006
gmtime gives 106/4/31 20:32:35 [3]
sending to clock 06/05/31 20:32:35 [3]

this is showing a connection to the time server (i.e. your rooter is setup correctly) and that the time and date zones are right.

IF this fails, you will probably have an idea where the process fails.. post the responce you get.

[Bonzo]

Thanks for that. Problem solved.

The output I got was

/bin/ntpdate: invalid option -- s
Our postcode is 02113. No matching timezone for postcode 02113

This was a pretty clear pointer. I re loaded the postcode files from the web, and retested. Now I get the same output as you.
Cheers. :)

[DavidClarke]

:D

Nice!!!

Cracking this one was the last big bug for my setup back in May. Still get the remote freeze but no-one seems to have a cure for that. As it stands it runs for weeks at a time and a quick re-power fixes it when it freezes.

Time to hack it around a bit more and make it unreliable again:rolleyes:

Love my TiVo

D

[thomson]

Still get the remote freeze but no-one seems to have a cure for that.

You might like to have a look at the EvtSwitchFixer (http://minnie.tuhs.org/twiki/bin/view/Software/EvtSwitchFixer). It resolves a different problem, but could also help out with the remote freeze (event bug) issue. Would be nice for somebody who is experiencing problems to give it a go and see if it does help.

[chis]

You guys are fantastic!

Yes, it was TCP port 37 being blocked by my firewall that was preventing my Tivo sychronising its clock. It's now spot-on.

Many of you have helped me, but special prize to DavidClarke. Being able to test the connection so conclusively was a gem.

Many thanks to you all.

[Darren King]

Yes, it was TCP port 37 being blocked by my firewall

Thougjht it might :)

[DavidClarke]

You might like to have a look at the EvtSwitchFixer (http://minnie.tuhs.org/twiki/bin/view/Software/EvtSwitchFixer). It resolves a different problem, but could also help out with the remote freeze (event bug) issue. Would be nice for somebody who is experiencing problems to give it a go and see if it does help.

Hmmm, the symptoms are not in my log at the moment, will check every couple of days and see if it turns up. Worth a crack so thanks for the suggestion.

It probably senses open unix surgery and is playing it cool :p

Will catch it out at some stage.

As for Chris, thats what its all about, everyone here knows something, and occasionally it comes in handy for someone else. :D