The ,#401 dialing prefix is not working with my new TurboNet for my old standalone Series 1 TiVo. The daily “call” fails with “Service not available”.
The TurboNet is installed and I verified that it’s getting an IP address from the DHCP server. Furthermore, I checked the outgoing log on my Linksys router and it shows that the TiVo is trying to make a connection to 204.176.49.2:80.
I can even access this IP address from my PC (although I can almost swear that earlier in this day, pings were not working):
23:35 Marc@Toshiba-Laptop:~$ nc -v 204.176.49.2 80 204.176.49.2: inverse host lookup failed: : Operation not permitted (UNKNOWN) [204.176.49.2] 80 (http) open : Operation now in progress GET / HTTP/1.0 HTTP/1.1 404 Not Found Date: Wed, 26 Jan 2005 07:35:23 GMT Server: Apache ...
Furthermore, My DirecTiVo is having trouble as well and I can see in its /var/log/tclient file that it’s successfully doing an HTTP POST to 204.176.49.2/tivo-service/mlog.cgi and getting back a 200 HTTP response, but then shortly after, the server seem to drop the connection.
I posted slightly more info at this thread at DealDatabase.com.
Frustrating. I guess the next thing that I will try is to burn a CD of the TurboNet ISO and see if that helps, although then I will have to take the drive out of the TiVo and put it in my PC. Or maybe I’ll just borrow a hub from somebody at work so I can poke around with Ethereal and see what I can find.
I’ve had the same problem. Was messing around with the settings in my Linksys router and noticed that it seems to work when I set the MTU size to 1400. (It is on the Filters tab of the Advanced setup menu). Hope it works for you too.
I think I tried messing with the MTU, but it’s been a while. In any case I solved the problem (I thought I had blogged about the solution, but a quick search just now suggests that I may’ve forgot – oops!) by switching to Sveasoft’s Alchemy firmware. It’s been working well ever since!