On 8/23/06, <b class="gmail_sendername">Ryan Pisani</b> <<a href="mailto:mythtv@frouse3.homelinux.com">mythtv@frouse3.homelinux.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> <a href="http://datadirect.webservices.zap2it.com/tvlistings/xtvdService">http://datadirect.webservices.zap2it.com/tvlistings/xtvdService</a><br>> => `-'<br>> Resolving datadirect.webservices.zap2it.com..
. <a href="http://206.18.98.160">206.18.98.160</a><br>> Connecting to datadirect.webservices.zap2it.com|206.18.98.160|:80...<br>> connected.<br>> HTTP request sent, awaiting response... 401 Unauthorized<br>> Connecting to
datadirect.webservices.zap2it.com|206.18.98.160|:80...<br>> connected.<br>> HTTP request sent, awaiting response... 200 OK<br>> Length: unspecified [text/xml]<br><br><br>Considering you're getting an "unauthorized" response, it looks like
<br>you've let your zap2it account expire. Have you gone to <a href="http://labs.zap2it.com">labs.zap2it.com</a><br>and seen the status of your account?</blockquote><div><br>Nope, that's not the problem. You *always* get the "Unauthorized" response the first time; it's the second connection that matters. (That's the way HTTP authentication works.) There's some other problem going on here.
<br><br>Carl Fongheiser<br></div><br></div><br>