PPP Serial Trouble

Discussion in 'TiVo Underground' started by Mephistopheles, Aug 25, 2004.

  1. cactus46

    cactus46 New Member

    770
    0
    Nov 17, 2001
    Phoenix AZ USA
    Hi Peter,

    I count 5 tests in your latest log. Can you disable your ICS and test? Have you made any other changes such as hardware changes? What kind of an Internet connection are you using--such as cable or DSL?

    John
     
  2. cactus46

    cactus46 New Member

    770
    0
    Nov 17, 2001
    Phoenix AZ USA
    Hi strange,

    How many com ports does your computer have? If you have two, can you try the setup on the other port? If you have only com1, can you try changing the IRQ for that port?

    Let us know.

    John
     
  3. strange_69

    strange_69 New Member

    68
    0
    Mar 3, 2004
    I only have COM 1 and 2. Right now I have the serial cable from my TIVO plugged into COM 1. I don't know where COM 2 is. LOL I am able to get the "garbage" using HT on COM 1 so I know that my connection is good. I just cannot set up an Incoming Connection while I am using C to C. As soon as I uninstall C to C the Incoming Connection Icon appears preconfigured just as I left if. I have checked in my Device Manager for conflicts and there are non that I can see. I just tried a selective startup unchecking all of my startup programs but it made no differance. Is it possible to use my computer's USB connection instead of serial connection? USB stands for Universal Serial Bus right?
     
  4. cactus46

    cactus46 New Member

    770
    0
    Nov 17, 2001
    Phoenix AZ USA
    >>USB stands for Universal Serial Bus right?<< In the current context, yes. Ok, if you find it hard to change your com1 port to a different IRQ, then the only other suggestion I have is to get a USB-to-serial cable to give yourself another com port to set up for serial to PPP. Here is an example: http://www.newegg.com/app/ViewProductDesc.asp?description=12-101-112&depa=0 I'm not saying that this will work for you but it is another approach to your serial to PPP situation. Of course there are many more adapters, too.

    And maybe your friend can find some time for some better approach to the solution?

    John
     
  5. strange_69

    strange_69 New Member

    68
    0
    Mar 3, 2004
    I'm just confused. COM 1 is using IRQ 4 which is not being used by anything else. I still have nightmares of Win 95/IRQ conflict days. I could try to swap IRQs with COM 2 if you think that would work.
     
  6. Peter Miller

    Peter Miller 6th member of SG-1

    98
    2
    Nov 28, 2001
    San Jose,...
    That's strange, I disabled ICS and the connection worked with IP addresses outside the range of IPs the router hands out. When I turned ICS back on the tivo would fail at the negotiation stage. Guess I'll just have to remember to turn off ICS when I need my tivo to dial out. Thanks for the help!
     
  7. cactus46

    cactus46 New Member

    770
    0
    Nov 17, 2001
    Phoenix AZ USA
    stange,

    I wish you luck on whatever you try to do to improve the chances of your serial to PPP working. I always hope my suggestions will improve the situation but I am skeptical that they will. Not having up close and personal contact with the problem puts me at a disadvantage.

    Usually my ideas are formed by the symptoms I see via the person who has the problem relating them here. So if you think it might work, then try it but do so at your own risk. YMMV. :)

    John

     
  8. Feb 1, 2005 #108 of 823
    strange_69

    strange_69 New Member

    68
    0
    Mar 3, 2004
    John, Thanks for your help and time. I think that I am just going to have to put this on the back burner until I can come across something else to help me. Once again, thanks for your help. If and when I lick this problem you will probily be the first person I tell what I found. I bet that it is going to be a head thumper. LOL Take care, Steve
     
  9. Feb 1, 2005 #109 of 823
    KEVIN7822

    KEVIN7822 New Member

    5
    0
    Jan 17, 2005
    This thread was a huge help to me thanks to all those who contributed.

    One tip to everyone, if your unit hasn't called in for a while it can take a long time before it completes negotiating, it took mine 45 min. Now it connects without a problem, so don't get worried if it seems to be stuck negotiating for a while.
     
  10. Feb 2, 2005 #110 of 823
    cmccallion

    cmccallion New Member

    3
    0
    Jan 5, 2005
    Bergen...
    After taking a week off on trying to get my connection to work, I returned to this forum and found a few more hints and...

    SUCCESS!!!

    Here's what did it for me:
    1) Since I don't have a router, I changed my IP addresses to be in line with my modem's IP address (67.81.9.###) instead of a router range (192.68.1.###)

    2) I looked back at my edited mdmhayes.inf and found that I had the extra spaces after "CLIENT", and "<h00>CLIENT", so I deleted those.

    3) I disabled my blackice firewall and windows firewall.

    I had a successful test call and daily call and downloaded the program data. My equipment is a Phillips Series 1 HDR312-12 with a long serial extention cable between two floors. I had been out for almost two months!

    Thank you to this forum! Good luck everyone else.
     
  11. Feb 2, 2005 #111 of 823
    cactus46

    cactus46 New Member

    770
    0
    Nov 17, 2001
    Phoenix AZ USA
    Hi cmccallion,

    Congratulations on your progress! Your item #2 would be the key to your calls not going through, I believe. It is very important not to have any extraneous characters and spaces edited into the mdmhayes.inf file. I simply cut'n'paste Otto's changes into the mdmhayes.inf without any extra spaces.

    I would try putting the firewalls back into the picture, one at a time with a Test Call test.

    Thanks for the update.

    John
     
  12. KBrack

    KBrack Member

    44
    5
    Feb 15, 2002
    Twin Cities, MN
    Thanks to all of you who offered suggestions and troubleshooting advice. After hours of effort, I never was able to get XP to work - I'm guessing it was something with the special configuration of the machines on our standard office baseload.

    It was a much different story after giving it a try on one of my Mac laptops. I think that the Unix based OS makes for a much cleaner process and would suggest that anyone who has access to a machine running OS X give it a try.

    Here's a more detailed post about my experience with the process and the how-to is a few posts up:

    http://www.tivocommunity.com/tivo-vb/showthread.php?p=2628191#post2628191
     
  13. cburns14

    cburns14 New Member

    14
    0
    Dec 21, 2003
    Virginia
    This is a bit off-topic for this tread....

    After getting my ppp connection to work, I started wondering more about how this
    setup works (as it applies to the directv and tivo calls which are separate things). I thought that Directv did not support updates via the internet, but this technique is doing just that. I have not verified that I am successfully billed for pay-per-views after an update (haven't ordered any yet), but I know I read somewhere in one of these threads that ppvs are working (i.e. the directv call). Or am I confused, and I am only updating my tivo software (i.e. the tivo phone call)?

    What I understand is that my tivo is able to access the internet via my pc. Then what happens?

    Chris
     
  14. etsolow

    etsolow Don't Try

    1,625
    11
    Feb 8, 2001
    Wisconsin
    As I understand it the Tivo call and the DirecTV call are completely separate. The Tivo call dials up an ISP (UUNET?) and does its business over the internet, whereas the DirecTV call dials directly into DirecTV. This is how DirecTV can (but doesn't?) verify that all your units are dialing in from the same land-line, as the number dialed is an 800 number with Automatic Number Identification.

    I read this somewhere on the internet, so it's gotta be right. :D

    E
     
  15. schiavonir

    schiavonir New Member

    39
    0
    Jul 17, 2000
    West...
    First off, let me say how much I appreciate all the work that has gone into this thread. Several times, as I read through it, I thought all my problems were solved. Alas, they are not. I have a Series 1 and I'm connecting to Win2k. Going by the log, it appears that I'm getting a connection, but my TiVo never says "Negotiating...", just "Connecting..." then "Failure." Comparing my log to others, it would appear to be related to the fact that no data is being written.

    I have edited the logfile to show the initialization and the latest result. I'm trying at 9600, so I've used ,#296 as the prefix. It connected fine through HyperTerminal.

    Please help, Vonage stopped working after a year of no problems, and I'm out of guide data.

    02-20-2005 21:56:11.493 - File: C:\WINNT\System32\unimdm.tsp, Version 5.0.2195 - Retail
    02-20-2005 21:56:11.573 - File: C:\WINNT\System32\unimdmat.dll, Version 5.0.2195 - Retail
    02-20-2005 21:56:11.624 - File: C:\WINNT\System32\uniplat.dll, Version 5.0.2195 - Retail
    02-20-2005 21:56:11.804 - File: C:\WINNT\System32\drivers\modem.sys, Version 5.0.2195 - Retail
    02-20-2005 21:56:11.894 - File: C:\WINNT\System32\modemui.dll, Version 5.0.2195 - Retail
    02-20-2005 21:56:11.894 - Modem type: Communications cable between two computers
    02-20-2005 21:56:11.894 - Modem inf path: mdmhayes.inf
    02-20-2005 21:56:11.894 - Modem inf section: M2700
    ...
    02-20-2005 22:28:37.308 - 9600,8,N,1, ctsfl=1, rtsctl=2
    02-20-2005 22:28:37.318 - Initializing modem.
    02-20-2005 22:28:37.328 - Waiting for a call.
    02-20-2005 22:29:12.779 - Recv: ~
    02-20-2005 22:29:12.779 - Interpreted response: Ring
    02-20-2005 22:29:12.779 - Recv: <ff>}#<c0>!}!
    02-20-2005 22:29:12.779 - Unknown Response
    02-20-2005 22:29:12.779 - Recv: }
    02-20-2005 22:29:12.789 - Unknown Response
    02-20-2005 22:29:12.789 - Recv: !} }4}"
    02-20-2005 22:29:12.789 - Unknown Response
    02-20-2005 22:29:12.789 - Recv: }
    02-20-2005 22:29:12.789 - Unknown Response
    02-20-2005 22:29:12.789 - Recv: &} } }
    02-20-2005 22:29:12.789 - Unknown Response
    02-20-2005 22:29:12.799 - Recv: }
    02-20-2005 22:29:12.799 - Unknown Response
    02-20-2005 22:29:12.799 - Recv: }%}&}
    02-20-2005 22:29:12.799 - Unknown Response
    02-20-2005 22:29:12.809 - Recv: }
    02-20-2005 22:29:12.809 - Unknown Response
    02-20-2005 22:29:12.809 - Recv: i<f7>}'}"
    02-20-2005 22:29:12.809 - Unknown Response
    02-20-2005 22:29:12.819 - Recv: }
    02-20-2005 22:29:12.819 - Unknown Response
    02-20-2005 22:29:12.819 - Recv: (}"<97>}<~
    02-20-2005 22:29:12.819 - Unknown Response
    02-20-2005 22:29:15.783 - Recv: ~
    02-20-2005 22:29:15.783 - Interpreted response: Ring
    02-20-2005 22:29:15.783 - Recv: <ff>}#<c0>!}!
    02-20-2005 22:29:15.783 - Unknown Response
    02-20-2005 22:29:15.783 - Answering the call.
    02-20-2005 22:29:16.134 - Recv: }
    02-20-2005 22:29:16.134 - Unknown Response
    02-20-2005 22:29:16.134 - Recv: !} }4}"}&} } } } }%}&} } i<f7>}'}"}(}"<97>}<~
    02-20-2005 22:29:16.134 - Unknown Response
    02-20-2005 22:29:16.144 - Send: CLIENTSERVER
    02-20-2005 22:29:16.144 - Connection established at 9600bps.
    02-20-2005 22:29:16.144 - Error-control off or unknown.
    02-20-2005 22:29:16.144 - Data compression off or unknown.
    02-20-2005 22:29:46.147 - Read: Total: 538, Per/Sec: 14, Written: Total: 0, Per/Sec: 0
    02-20-2005 22:29:48.871 - Hanging up the modem.
    02-20-2005 22:29:48.871 - Hardware hangup by lowering DTR.
    02-20-2005 22:29:50.874 - Recv: +++ATH<cr>
    02-20-2005 22:29:50.874 - Unknown Response
    02-20-2005 22:29:50.874 - 9600,8,N,1, ctsfl=1, rtsctl=2
    02-20-2005 22:29:50.874 - Initializing modem.
    02-20-2005 22:29:50.884 - Waiting for a call.
    02-20-2005 22:50:37.516 - Recv: ~
    02-20-2005 22:50:37.516 - Interpreted response: Ring
    02-20-2005 22:50:37.516 - Recv: <ff>}#<c0>!}!}!} }4}"}&} } } } }%}&<ff><ff><88><8a>}'}"}
    02-20-2005 22:50:37.516 - Unknown Response
    02-20-2005 22:50:40.470 - Recv: ~
    02-20-2005 22:50:40.470 - Interpreted response: Ring
    02-20-2005 22:50:40.470 - Recv: <ff>}#<c0>!}!
    02-20-2005 22:50:40.470 - Unknown Response
    02-20-2005 22:50:40.481 - Answering the call.
    02-20-2005 22:50:40.481 - Recv: }
    02-20-2005 22:50:40.481 - Unknown Response
    02-20-2005 22:50:40.481 - Recv: !} }4}"
    02-20-2005 22:50:40.481 - Unknown Response
    02-20-2005 22:50:40.491 - Send: CLIENTSERVER
    02-20-2005 22:50:40.491 - Connection established at 9600bps.
    02-20-2005 22:50:40.491 - Error-control off or unknown.
    02-20-2005 22:50:40.491 - Data compression off or unknown.
    02-20-2005 22:51:10.494 - Read: Total: 508, Per/Sec: 14, Written: Total: 0, Per/Sec: 0
    02-20-2005 22:51:13.738 - Hanging up the modem.
    02-20-2005 22:51:13.738 - Hardware hangup by lowering DTR.
    02-20-2005 22:51:15.741 - Recv: +++ATH<cr>
    02-20-2005 22:51:15.741 - Unknown Response
    02-20-2005 22:51:15.741 - 9600,8,N,1, ctsfl=1, rtsctl=2
    02-20-2005 22:51:15.741 - Initializing modem.
    02-20-2005 22:51:15.741 - Waiting for a call.

    Edit: following all the suggestions, I am giving an IP range that is within my router's DHCP range.
     
  16. cburns14

    cburns14 New Member

    14
    0
    Dec 21, 2003
    Virginia
    I'm far from an expert at reading those log files, so I'll leave that to someone else. Someone posted earlier about adding a couple of commas at the end, and that
    made all the difference. i.e. try
    ,#296,, rather than ,#296.
    Why did you bump down to 9600? Long cable?
    I assume you triple-checked your editing of your mdmhayes file, and deleted the associated file, rebooted, etc. Turned off firewalls (including XPs in service pack 2)?
    There was a post about motorola routers earlier if you have one of those. That problem would be tough to crack without reading the post.

    Since you can't connect, I would guess the problem may lie in your creation of the incoming connection.
    Look at the properties of your incoming connection. When you look at your devices, is your connection on the correct com port? If you are using a usb adapter, look over your com settings under Device Manager (Control panel->System->Hardware). You should see (when the usb adapter is plugged in) a listing for that adapter and its com port. Are they the same? If not you need to address this.
    For the properties of your incoming connection, make sure flow control is set to none. Make sure the other options under incoming connection are in line with Otto's instructions.
     
  17. schiavonir

    schiavonir New Member

    39
    0
    Jul 17, 2000
    West...
    Yep, tried that. No difference.


    Just trying different things. Started at 115k, went to 19.2, then to 9600. They all seem to communicate with the computer, according to the logfiles.


    Oh yeah. Maybe quadruple checked, cut and pasted, deleted .pnf, rebooted, deleted and recreated the Incoming connection, everything. I'm using Win2k, so service packs and firewalls should not be an issue for me.

    I have a D-Link router.

    The computer has a single serial port which is what I am using. Since the HyperTerminal test comes out okay, I think the port is okay - no conflicts.

    Double and triple checked.

    Thanks for your response. I expected a couple rounds of clarification. One thing I suspect is my cabling. You guys know how those serial cables go. You never have quite what you need, so you string a bunch of different cables together, which is what I've done. Today, I will stop at Radio Shack and pick up a straight 9-pin to 9-pin to simplify my connection from the TiVo to the computer:

    TiVo->TiVo Serial cable->9 pin null modem->9 pin cable->9 pin serial port

    I'll see if that helps. Any other suggestions are welcome, of course. I feel really close. It just seems that TiVo is not getting a response back from the computer, which is why "bytes written" = 0 and why TiVo never moves beyond the "Connecting...." stage.

    Roger
     
  18. cburns14

    cburns14 New Member

    14
    0
    Dec 21, 2003
    Virginia
    It sounds like you are close. Sounds like simplifying your cable connections would be very worthwhile. My troubleshooting mantra is: simplify and remove variables from the equation, and cleaning up your cable setup would help.
    Keep plugging away...it'll be a great feeling when it suddenly starts working.
     
  19. cactus46

    cactus46 New Member

    770
    0
    Nov 17, 2001
    Phoenix AZ USA
    Hi Roger,

    You will never connect until you set your "Flow control" to 'None. From your log: 02-20-2005 22:28:37.308 - 9600,8,N,1, ctsfl=1, rtsctl=2

    It should look like this: 01-18-2005 18:18:55.371 - 115200,8,N,1, ctsfl=0, rtsctl=1

    cburns14 was on the right track with his Flow control suggestion. Correct this and give us an update. Good luck.

    John
     
  20. schiavonir

    schiavonir New Member

    39
    0
    Jul 17, 2000
    West...
    Good catch. The first time I set it up, I made this change. Another time, clicking the button didn't work to bring up those options. The last time, I thought I made the change, but either I didn't, or it didn't save the setting. I will definitely check that. Got myself the necessary cable to simplify everything, so I'm excited to try it out tonight.

    BTW, I was thinking 5 or 6 bucks for that cable. Not even close. $13.99 at Radio Shack. Wow, supply and demand, I guess.
     

Share This Page