|
| Author |
Message |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Sat Sep 06, 2008 12:28 am Post subject: Tivo doesn't see server / no requests from Tivo |
|
|
This feels so generic, but here:
I just got my Tivo HD (TCD652160) today, got it set up and working, downloaded and effortlessly installed pyTivo on my WinXP box. I used the Windows installer.
My Tivo doesn't see and/or query the pyTivo server (I've watched from the pyTivo console).
I turned off my firewall, which had a clear opening for pyTivo's port in it anyway.
pyTivo server is verifiably running, and I can access it from another computer on my network. I even accessed it via
http://192.168.0.2:9032/TiVoConnect?Command=QueryContainer&Container=%2F
and I get what looks like a reasonable listing (XML-style?) of my media folders. Also, I see the transaction on the pyTivo console.
I tried going into my account at tivo.com and disabling, saving, and reenabling, saving the streaming, or whatever, forcing the Tivo to reconnect to the service after each change.
I've disabled/reenabled Home Network Applications a few times, and I've tried manually adding the server's IP address several times.
I changed the beacon to equal the Tivo's IP address specifically.
I can ping the server (obviously) and the Tivo from my other computer.
The Tivo just doesn't seem to be looking for the server.
I'm out of ideas for now. Any ideas?
Thanks! |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 362
|
Posted: Sat Sep 06, 2008 6:56 am Post subject: |
|
|
So it sounds like your Tivo HD has been officially activated (because it's on your Tivo.com account.) And if you go to the System Info screen on the Tivo, you will probably see your TivoToGo status as "a,a,a".
However, your Tivo HD probably hasn't updated it's software yet. What version of the Tivo software does it have? Some of the older versions don't work and you'll just have to wait a day or two for the mothership to update it. |
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Sat Sep 06, 2008 8:52 am Post subject: |
|
|
Thanks for the reply.
Yeah, the system did update the software version to 9.4-01-2-656, but that didn't change the situation.
TivoToGo does show "a,a,a". |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 362
|
Posted: Sat Sep 06, 2008 8:54 am Post subject: |
|
|
So your pyTivo box has IP 192.168.0.2. Is it wired or wireless?
What is the IP of your Tivo HD unit? Is it wired or wireless? |
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Sat Sep 06, 2008 9:02 am Post subject: |
|
|
They're both wired.
pyTivo: 192.168.0.2
Tivo: 192.168.0.8 |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 362
|
Posted: Sat Sep 06, 2008 9:27 am Post subject: |
|
|
In your pyTivo.conf file, try this for the beacon line in your Server section:
| Code: | beacon = 192.168.0.255 |
pyTivo is supposed to send broadcast packets to your network to inform your Tivo's that it exists and what port to use to query it.
Once the Tivo receives the beacon, it makes HTTP calls to pyTivo on the port (9032 by default) to query the shares.
Since you can reach pyTivo fine, then 9032 is working for the HTTP part, but I'm wondering if something is blocking the beacon broadcast.
What firewall package are you using? Some firewalls don't always turn off completely when you disable them. Try putting an exception in for python.exe so that it can do any networking it wants rather than opening a specific port. |
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Sat Sep 06, 2008 10:45 am Post subject: |
|
|
It's just the Windows firewall. Even though it's off I went ahead and added python.exe.
What's a good simple way for me to see if it's sending out that beacon?
Oh, and I don't see any change with the .255 in there.
This is frustrating...I really do appreciate the suggestions! |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 362
|
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Sat Sep 06, 2008 11:18 am Post subject: |
|
|
I'll get on that today, thanks!
I'll report back on my results. |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 362
|
Posted: Sat Sep 06, 2008 11:26 am Post subject: |
|
|
Also, once you have pyTivo running and can browse to the 9032 port, open up a command prompt and run:
| Code: | netstat -ano > c:\socket.txt |
Then post socket.txt here. I can use that to figure out what TCP/UDP ports your machine is using and whether it's binding the beacon socket. |
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Sat Sep 06, 2008 5:18 pm Post subject: |
|
|
Okay, done. I also removed the chunk of pyTivo.conf that had my audio in it, as I wondered if my giant collection might be choking it or something. Still no dice.
Here's my socket.txt:
| Code: | Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 988
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 908
TCP 0.0.0.0:9032 0.0.0.0:0 LISTENING 3700
TCP 127.0.0.1:1034 0.0.0.0:0 LISTENING 2728
TCP 127.0.0.1:1681 127.0.0.1:27015 ESTABLISHED 3640
TCP 127.0.0.1:1793 127.0.0.1:1794 ESTABLISHED 2248
TCP 127.0.0.1:1794 127.0.0.1:1793 ESTABLISHED 2248
TCP 127.0.0.1:1795 127.0.0.1:1796 ESTABLISHED 2248
TCP 127.0.0.1:1796 127.0.0.1:1795 ESTABLISHED 2248
TCP 127.0.0.1:4242 0.0.0.0:0 LISTENING 864
TCP 127.0.0.1:4664 0.0.0.0:0 LISTENING 1836
TCP 127.0.0.1:27015 0.0.0.0:0 LISTENING 648
TCP 127.0.0.1:27015 127.0.0.1:1681 ESTABLISHED 648
TCP 192.168.0.2:139 0.0.0.0:0 LISTENING 4
TCP 192.168.0.2:139 192.168.0.3:2673 ESTABLISHED 4
TCP 192.168.0.2:1835 74.125.15.37:80 ESTABLISHED 2248
UDP 0.0.0.0:445 *:* 4
UDP 0.0.0.0:500 *:* 752
UDP 0.0.0.0:1025 *:* 1540
UDP 0.0.0.0:1821 *:* 3700
UDP 0.0.0.0:4500 *:* 752
UDP 127.0.0.1:123 *:* 1128
UDP 127.0.0.1:1900 *:* 1320
UDP 192.168.0.2:123 *:* 1128
UDP 192.168.0.2:137 *:* 4
UDP 192.168.0.2:138 *:* 4
UDP 192.168.0.2:1900 *:* 1320 |
Last edited by urge on Sat Sep 06, 2008 9:05 pm; edited 1 time in total |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 362
|
Posted: Sat Sep 06, 2008 5:27 pm Post subject: |
|
|
Couple questions:
1) Was this that sockets.txt with krkeegan's Windows installer version, or did you already switch to wmcbrine's version?
2) What version on Windows do you run? XP or Vista? Home, Pro, Media Center?
3) What service pack level is your Windows?
4) If you open a command prompt window and type "hostname", what's reported? |
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Sat Sep 06, 2008 5:34 pm Post subject: |
|
|
1) This was after switching to wmcbrine.
2 & 3) XP Pro SP2.
4) urgemore
Also, a few minutes ago I tried making an https: connection to my Tivo and got:
Secure Connection Failed
192.168.0.8 uses an invalid security certificate.
The certificate is not trusted because it is self signed.
The certificate is only valid for 652-0011-803A-EF4B
(Error code: sec_error_ca_cert_invalid)
* This could be a problem with the server's configuration, or it could be someone trying to impersonate the server.
* If you have connected to this server successfully in the past, the error may be temporary, and you can try again later.
Or you can add an exception…
I don't know if that's significant, but thought it was a data point.
I was able to add an exception, after which I got a login prompt. |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 362
|
Posted: Sat Sep 06, 2008 7:15 pm Post subject: |
|
|
| You can ignore that certificate warning. Everyone gets it because Tivo uses a self signed certificate for the Tivo's builtin web server. |
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Sat Sep 06, 2008 8:58 pm Post subject: |
|
|
Also, just in case the netstat results are different with the service running vs. the console, here's an example I just now generated:
| Code: | Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 988
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 908
TCP 0.0.0.0:9032 0.0.0.0:0 LISTENING 2464
TCP 127.0.0.1:1034 0.0.0.0:0 LISTENING 2728
TCP 127.0.0.1:2795 127.0.0.1:27015 ESTABLISHED 2660
TCP 127.0.0.1:2892 127.0.0.1:2891 TIME_WAIT 0
TCP 127.0.0.1:2897 127.0.0.1:2898 ESTABLISHED 3476
TCP 127.0.0.1:2898 127.0.0.1:2897 ESTABLISHED 3476
TCP 127.0.0.1:2899 127.0.0.1:2900 ESTABLISHED 3476
TCP 127.0.0.1:2900 127.0.0.1:2899 ESTABLISHED 3476
TCP 127.0.0.1:4242 0.0.0.0:0 LISTENING 864
TCP 127.0.0.1:4664 0.0.0.0:0 LISTENING 1452
TCP 127.0.0.1:9032 127.0.0.1:2903 TIME_WAIT 0
TCP 127.0.0.1:9032 127.0.0.1:2906 TIME_WAIT 0
TCP 127.0.0.1:27015 0.0.0.0:0 LISTENING 648
TCP 127.0.0.1:27015 127.0.0.1:2795 ESTABLISHED 648
TCP 192.168.0.2:139 0.0.0.0:0 LISTENING 4
TCP 192.168.0.2:139 192.168.0.3:3566 ESTABLISHED 4
TCP 192.168.0.2:2895 209.85.171.104:80 TIME_WAIT 0
TCP 192.168.0.2:2896 209.85.171.103:80 TIME_WAIT 0
TCP 192.168.0.2:2901 209.85.171.104:80 ESTABLISHED 3476
TCP 192.168.0.2:2902 209.85.171.103:80 ESTABLISHED 3476
TCP 192.168.0.2:2904 74.125.19.100:80 ESTABLISHED 3476
UDP 0.0.0.0:445 *:* 4
UDP 0.0.0.0:500 *:* 752
UDP 0.0.0.0:1025 *:* 1540
UDP 0.0.0.0:2888 *:* 2464
UDP 0.0.0.0:4500 *:* 752
UDP 127.0.0.1:123 *:* 1128
UDP 127.0.0.1:1900 *:* 1320
UDP 192.168.0.2:123 *:* 1128
UDP 192.168.0.2:137 *:* 4
UDP 192.168.0.2:138 *:* 4
UDP 192.168.0.2:1900 *:* 1320 |
|
|
| Back to top |
|
 |
|