Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[rowens]

I've tried, unsuccessfully, for the last few days to get TIVO to recognize Media Server.  I see from searching through other posts that others have had difficulty as well, but unfortunately, their solutions either haven't worked or don't apply.

I'm running Win2K on a wired network.  TIVO Publisher works fine.  Media Center doesn't.  There's a built in firewall on the router that i've opened port 8079 - i've set the Media Server to automatically detect the port, and set TIVO to run on 8079/2190.

I'm running a program called Active Ports which indicates that Media Server is listening on local ports 80, 5556 and 8079.  TivoBeacon.exe is listening on 2190 and 8100, with TivoServer.exe listening on 8080.

One interesting phenomena - when i try to open Media Center after Media Server is running on my PC, i get an error message "Couldn't create WebRemote listener', followed by another error "Failed to start Remote Server'.  After clicking OK, Media Center opens and appears to run normally.

I'm at a loss in trying to figure out what to do next.  Anyone have any ideas?? Any help would be much appreciated... hopefully i can get it up and running before my 30 day trial expires, as i'd really like to use MC on my TIVO!

Thanks
Rick

And here's the output in the Status window on MediaServer:
10/26/04 21:56:32 - Server initialized
10/26/04 21:56:32 - sharer ready to accept connections
10/26/04 21:56:32 - Started auto response thread on port 5556.
10/26/04 21:56:32 - TiVo HTTP ready for connections
10/26/04 21:57:07 - TiVo HTTP: received a connection
10/26/04 21:57:07 - TiVo HTTP: ready for another connection

[John Gateley]

Which version of Media Center are you running?

Try shutting down the TiVo Beacon (through services, don't kill the process).

j

[rowens]

Thanks for the reply, John.

I'm running Media Center 10.0.

I shut down the Tivo Beacon (through services), and reloaded Media Server and got an error "Tivo connect Beacon is not available".

I then changed the MediaServer options to NOT support TIVO HMO and to use port 80 for Media Server.

Nothing worked.

Any other ideas or methods to debug?

TIA,
Rick

[John Gateley]

Yes: get the latest version of 10. There were several problems of this kind fixed a while ago.

j

[rowens]

i have version 10.0.173... sorry, i omitted the last 3 digits as i didn't see them initially.  

I looked for something more recent in Version 10, but couldn't find anything...

I suspect we're back to square 1?  Or am i missing something?  

TIA,
Rick

[John Gateley]

Your error message (TiVo beacon not available) and the missing digits led me to think it was an earlier version. I'll have to search the source tomorrow. If you could post the exact text of the message that would help.

In the meantime, it really should work. Start the original TiVo beacon in services, do a netstat -an to make sure the beacon is listening on 8100 (you can test it with a browser too). Then start Media Server.

Is there a firewall on the local machine? Media Server has to connect to the beacon on 8100.

j

[rowens]

If you could post the exact text of the message that would help.
hmm... not sure what message you are referring to... sorry.  I previously posted any error messages that i was receiving...

Yes, there's a firewall on the router.  I've opened ports 8079, 5556 and 2190 (maybe theres a way to test this to make certain these ports are properly opened?)

Netstat -an doesn't seem to work from DOS prompt.  Here's an output file from ActivePorts utility that shows open ports.  It does show 8100 is listening..

PROCESS      PID   LOCAL IP    LOCAL PORT   REMOTE IP   REMOTE   STATE   PROTOCOL   PATH
                        PORT
Media Server.exe1628   0.0.0.0      80            LISTEN   TCP   C:\Program Files\J River\Media Center\Media Server.exe
svchost.exe   508   0.0.0.0      135            LISTEN   TCP   C:\WINNT\system32\svchost.exe
System      8   192.168.0.100   137            LISTEN   UDP   
System      8   192.168.0.100   138            LISTEN   UDP   
System      8   192.168.0.100   139            LISTEN   TCP   
System      8   0.0.0.0      445            LISTEN   UDP   
System      8   0.0.0.0      445            LISTEN   TCP   
lsass.exe   244   192.168.0.100   500            LISTEN   UDP   C:\WINNT\system32\lsass.exe
MSTask.exe   828   0.0.0.0      1025            LISTEN   TCP   C:\WINNT\system32\MSTask.exe
System      8   0.0.0.0      1036            LISTEN   TCP   
IEXPLORE.EXE   1084   127.0.0.1   1045            LISTEN   UDP   C:\Program Files\Internet Explorer\IEXPLORE.EXE
IEXPLORE.EXE   1700   127.0.0.1   1495            LISTEN   UDP   C:\Program Files\Internet Explorer\IEXPLORE.EXE
ANT.exe      1584   192.168.0.100   1589   64.90.180.93   80   CLOSE_WAIT   TCP   C:\Program Files\DreamSysSoft\ANT\ANT.exe
ANT.exe      1584   192.168.0.100   1590   64.90.180.93   80   CLOSE_WAIT   TCP   C:\Program Files\DreamSysSoft\ANT\ANT.exe
IEXPLORE.EXE   1744   127.0.0.1   1723            LISTEN   UDP   C:\Program Files\Internet Explorer\IEXPLORE.EXE
IEXPLORE.EXE   308   127.0.0.1   2020            LISTEN   UDP   C:\Program Files\Internet Explorer\IEXPLORE.EXE
TivoBeacon.exe   692   0.0.0.0      2190            LISTEN   UDP   C:\Program Files\Common Files\TiVo Shared\Beacon\TivoBeacon.exe
TivoBeacon.exe   692   0.0.0.0      2190            LISTEN   TCP   C:\Program Files\Common Files\TiVo Shared\Beacon\TivoBeacon.exe
Media Server.exe1628   0.0.0.0      5556            LISTEN   UDP   C:\Program Files\J River\Media Center\Media Server.exe
Media Server.exe1628   0.0.0.0      8079            LISTEN   TCP   C:\Program Files\J River\Media Center\Media Server.exe
TivoBeacon.exe   692   0.0.0.0      8100            LISTEN   TCP   C:\Program Files\Common Files\TiVo Shared\Beacon\TivoBeacon.exe

[rowens]

any thoughts?

[rowens]

Over the wekeend, put PC in DMZ and Media Server worked perfectly...

Looks like the problem is on my end with my firewall configuration.  

sorry for the trouble...

[John Gateley]

Firewalls are often an issue. Port 8080 is often one of the allowed ports (commonly used for proxy servers I think), and 8079 is not, so check your firewall conf.

j