OK, I changed it all at the bottom of rc.sysinit, moving the rc.sysinit.author IF statement to the bottom, this caused my Tivo to hang on 'almost there'. I had to pull the drive and undo what i did using a bootcd as didnt have telnet access.

I have deleted the gotomydvr comments from .author, and have put right at the bottom of rc.sysinit .

It now works.

Cheers

The IF-THEN should never cause a problem, unless you had a syntax error or managed to get some ^M characters in there; you might want to double check that (carefully) as there is nothing inherently wrong with using a conditional anywhere in the startup files.

Good that you ultimately got it working. Have fun!

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

1) the bandwidth of your connection won't (shouldn't) make a difference unless there is a problem or bottleneck on our server. latency is the issue and i'd suggest that its not related to the latency of your network connection, but the speed at which your client returns the information; ie - unfortunately, TiVoWebPlus runs slowly in some implementations and that is a problem - would be great to have a lighter weight / faster version of TiVoWebPlus or an alternative http-based interface that was a little less clunky in this scenario

2) 'simply' using different ports is exactly what we were trying to eliminate with gotomydvr. the idea was to design and deploy a solution which required ZERO knowledge of ones home network to utilize. this is now beyond the concept stage as we've begun to embed the gotomydvr client in select kits and products, which means installation of the client (ie knowledge of your TiVo IP address is not necessary) no longer requires any technical ability, nor does one ever need to touch their router

3) as fofer said, its inherently more secure. to add to that, even if you argue that one can securely configure multiple TiVo units (albeit a more technical process) using a port forwarding scheme, it means you need to have administrative access to the router, and that leads to other security issues.

I do understand what you are saying, though -- personally, I think the *issue* is performance. With the newer version of TiVoWebPlus, I think there is some promise there. 6.2 and 6.3 are definitely better than older versions of the software. Series1 units with CacheCards are definitely peppy But still, TiVoWebPlus is a monster of an app to run on these units, either remotely or non-remotely - its a great app though. I do think there is room for something lighter-weight, and more conducive to say, a true mobile device and that would play well with gotomydvr.

So, to point out, we are well beyond the concept phase wrt to the TiVo platform here. There are over 1000 users registered and about 700 TiVo units registered with the site now and we are seeing decent activity. Thats good. The real concept here is to extend beyond the TiVoWebPlus world, though -- either to another http-based management interface (anyone game for that?) or even a new platform altogether; I think *that* would be cool.

Happy New Year!

Thanks for taking the time to address my comments. You're absolutely right in that it is a much more transparent and easier approach for most users; I realize TivoWebPlus is mostly the cause of the latency many of us seem to experience, which is why I look forward to testing it again on my Tivos once TivoWebPlus 1.4 leaves beta stage (I hear it is a lot faster than the present releases); from what I have been reading, 1.4 will mark the beginning of this transition towards the more mobile, less bloated approach you mention.

I am running an HDVR2. 6.2, Zippered and enhanced with rbautch's script. I am able to access my boxes via the internet through XP remote desktop and via orenosp. My ISP is Hughesnet and my router is a Linksys WRT54GS.

I got the error "Bad H*TTP response: H*TTP/1.0 400 Bad Request" when tring to run the b_install.sh script. So, I modified the script to use wget and everything installed correctly. When trying to run rc.gotomydvr I get:

I will be there all week, and if there are any users of the site that will be around during the week and want to meet for a brief discussion, please PM me and we'll coordinate a meeting place and time. My thought is just to have an open discussion about the usefullness / uselessness of what you've been exposed to so far, and talk a bit about the direction of things.

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

Just thought I should jump in here quick and let everyone know that for whatever reason, wget (the service used to download te remote access tool) does not work over HughesNet satellite service. I tried for a couple of weeks to get it to work. Then a few weeks ago I switched to DSL when it finally became available and without touching anything else, it worked instantly.

__________________
--Adam--

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

"The trouble with quotes on the Internet is that you can never know if they are genuine." - Mark Twain

Anyone know why in order for gotomydvr to work I have to open telent and run /gotomydvr/etc/rc.gotomydvr & also have to leave telnet open or gotomydvr says tivo disconected? this is in my /etc/rc.d/rc.sysinit.author file

Just thought I should jump in here quick and let everyone know that for whatever reason, wget (the service used to download te remote access tool) does not work over HughesNet satellite service. I tried for a couple of weeks to get it to work. Then a few weeks ago I switched to DSL when it finally became available and without touching anything else, it worked instantly.

Actually, wget works fine over Hughesnet. It is h*ttp_get that has a problem. I have been researching it and have been led to believe that it has something to do with the latency of satellite transmissions.

I don't know if that is accurate, as I have seen latency values with my Cox service in the city that far exceed those I see in the country with Hughesnet.

Actually, wget works fine over Hughesnet. It is h*ttp_get that has a problem. I have been researching it and have been led to believe that it has something to do with the latency of satellite transmissions.

I don't know if that is accurate, as I have seen latency values with my Cox service in the city that far exceed those I see in the country with Hughesnet.

I have read that port 80 is blocked by verizon and its pretty much impossable to do any port forwarding via the router due to its lack of user friendly menus.

If ANYONE has this problem or uses verizon or even the westell 327w router PLEASE respond. I found that calling verizon OR westell is a TOTAL waste of time and energy.

Thanks! Dave

I have Verizon DSL along with the excellent Westell 327W DSL Gateway and have had no problems accessing my Tivo's remotely thru www.gotomydvr.com. I didn't change the Westell 327W configuration and I'm running TWP 1.2.1 on both of my zippered Tivo's (1 wired and 1 connected wirlessly thru a Zyxel 802.11g bridge).

Yes, Rebooted EVERYTHING. Also checked the rc.sysinit.author file. The only thing that changed was the addition of the client commands at the end of the file.

It's probably something simple or stupid but its really becomming a headache as I can still FTP into the tivo but TWP fails as does the gotomydvr.

This is the responce I now get when I try to start TWP:

IP44:/var/hack/TivoWebPlus$ tivoweb
Warning: An http server was already running
Warning: The last few sessions did not complete successfully
We may be in a reboot loop... aborting
[1]+ Done tivoweb
IP44:/var/hack/TivoWebPlus$

1Dave1 --- the problem you are experiencing is with TiVoWebPlus (not gotomydvr); try removing the log files (rm -rf /var/log/*tivoweb.log) on your system and then restart TiVoWebPlus

bradnic --- remember, we (DVRupgrade) have no direct control to your TiVoWebPlus configuration; take a look in tivoweb.cfg file and you'll see that you probably have a username/password setup in there for accesses to TiVoWebPlus from OUTSIDE your LAn...

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

Glad it all worked for you. When you exited your telnet session on the 2nd unit, did the process continue to run?

FYI - PTVnet kits and software tools now contain the client, so if you've recently upgraded your system using either of them, all you have to do is register with the site, restart your unit and you'll have access to the service.

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

In fact, as I realized later, the process did not continue on the 2nd unit after ending telnet. I reinstalled w/ "sync; reboot &" and was good to go.

My third tivo is a Series 2 Standalone (TCD24A) running 8.1 tivo software. Your http get download worked as far getting rid of the segement fault and getting the client onto the unit. But beyond that .... no dice.

Should I conclude that the 8.x software is not compatible? I would be happy to let you telnet in to see what's going on.

In fact, as I realized later, the process did not continue on the 2nd unit after ending telnet. I reinstalled w/ "sync; reboot &" and was good to go.

My third tivo is a Series 2 Standalone (TCD24A) running 8.1 tivo software. Your http get download worked as far getting rid of the segement fault and getting the client onto the unit. But beyond that .... no dice.

Should I conclude that the 8.x software is not compatible? I would be happy to let you telnet in to see what's going on.

I wouldn't draw a conclusion like that unless you've got a bit more data to support it. I'd be happy to poke around if you can provide the access (PM me with the details and I'll try to take a look today)... Thx

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

Apparently the error occurred between my keyboard and my chair.
Works great!

Not exactly sure *what* the problem was. For those interested in a little more detail, it looked like the client, or components of it, had been started multiple times. In retrospect, a reboot of the unit probably would have solve the problem, but contrary to popular belief, that is rarely the solution... In any case, I did poke around, and things looked good after killing/restarting things.