Sign in with
Sign up | Sign in
Your question

Broadband Guide update failing

Last response: in Home Theatre
Share
Anonymous
April 2, 2005 2:01:03 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

I've got a replaytv model 5508 that up until 2 weeks ago was updateing
the program guide just fine
via my internet connection.

My connection consists of the replaytv on a home network
behind a linksys router. That router is then connected to the ISP's equipment.

I had to change the settings last night to start updating
via phone line because something has changed and now updating
the program guide via the network connection is failing. In watching
the progress it looks like we get most of the way through
before getting a message that the update has failed and it will
try again later. The last message I see is "combining data ..."

I'm trying to figure out if something has changed upstream with my
ISP or if something has happened to my Linksys.

Any thoughts would be appreciated.


--
=========================================================
George L. Rachor Jr. george@rachors.com
Hillsboro, Oregon http:rachors.com
United States of America Amateur Radio : KD7DCX
Anonymous
April 2, 2005 4:02:44 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
Rachor) wrote:

>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>the program guide just fine
>via my internet connection.
>
>My connection consists of the replaytv on a home network
>behind a linksys router. That router is then connected to the ISP's equipment.
>
>I had to change the settings last night to start updating
>via phone line because something has changed and now updating
>the program guide via the network connection is failing. In watching
>the progress it looks like we get most of the way through
>before getting a message that the update has failed and it will
>try again later. The last message I see is "combining data ..."
>
>I'm trying to figure out if something has changed upstream with my
>ISP or if something has happened to my Linksys.
>
>Any thoughts would be appreciated.

The way the Replay handles errors can be misleading. There can be a
failure near the beginning, then the process seems to get all the way
through before you're told about it.

Is your Replay set to get a dynamic local IP from the router? If so,
you may need to refresh it (because of ISP making changes). Otherwise,
check carefully. The ISP could have changed DNS servers.

--
Mark Lloyd
has a Replay 5xxx
http://notstupid.laughingsquid.com

"The idea that there is an invisible being who
created and still runs this old universe is so
childish, so obviously contrived, that it is hard to
believe anyone with even a modicum of education can
still fall for that scam."
Anonymous
April 2, 2005 8:41:38 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

OK... I've been through completly refreshing the linksys <including dumping all the current leases and aquiring new addresses.>

I've verified the linksys and the replaytv have agreed on the ip address being used.
I've even tried using a diffent dns with no change.
Any idea where to troubleshoot next?

George
Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:

>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>Rachor) wrote:

>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>the program guide just fine
>>via my internet connection.
>>
>>My connection consists of the replaytv on a home network
>>behind a linksys router. That router is then connected to the ISP's equipment.
>>
>>I had to change the settings last night to start updating
>>via phone line because something has changed and now updating
>>the program guide via the network connection is failing. In watching
>>the progress it looks like we get most of the way through
>>before getting a message that the update has failed and it will
>>try again later. The last message I see is "combining data ..."
>>
>>I'm trying to figure out if something has changed upstream with my
>>ISP or if something has happened to my Linksys.
>>
>>Any thoughts would be appreciated.

>The way the Replay handles errors can be misleading. There can be a
>failure near the beginning, then the process seems to get all the way
>through before you're told about it.

>Is your Replay set to get a dynamic local IP from the router? If so,
>you may need to refresh it (because of ISP making changes). Otherwise,
>check carefully. The ISP could have changed DNS servers.

>--
>Mark Lloyd
>has a Replay 5xxx
>http://notstupid.laughingsquid.com

>"The idea that there is an invisible being who
>created and still runs this old universe is so
>childish, so obviously contrived, that it is hard to
>believe anyone with even a modicum of education can
>still fall for that scam."
--
=========================================================
George L. Rachor Jr. george@rachors.com
Hillsboro, Oregon http:rachors.com
United States of America Amateur Radio : KD7DCX
Related resources
Anonymous
April 2, 2005 11:31:05 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

On Sat, 02 Apr 2005 16:41:38 -0600, george@agora.rdrop.com (George
Rachor) wrote:

>
>
>OK... I've been through completly refreshing the linksys <including dumping all the current leases and aquiring new addresses.>
>
>I've verified the linksys and the replaytv have agreed on the ip address being used.
>I've even tried using a diffent dns with no change.

You need to use the DNS abbresses provided by your ISP. Different ones
probably won't work.

BTW, one exception is if you're using WiRNS.

>Any idea where to troubleshoot next?
>

Looks like your computer (which I suppose is connected to the same
router) is working on usenet. Does the web work too? I think you may
not understand DNS too well, but it your computer works, it has
correct values. Make sure the Replay has the same ones.

>George
>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>
>>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>>Rachor) wrote:
>
>>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>>the program guide just fine
>>>via my internet connection.
>>>
>>>My connection consists of the replaytv on a home network
>>>behind a linksys router. That router is then connected to the ISP's equipment.
>>>
>>>I had to change the settings last night to start updating
>>>via phone line because something has changed and now updating
>>>the program guide via the network connection is failing. In watching
>>>the progress it looks like we get most of the way through
>>>before getting a message that the update has failed and it will
>>>try again later. The last message I see is "combining data ..."
>>>
>>>I'm trying to figure out if something has changed upstream with my
>>>ISP or if something has happened to my Linksys.
>>>
>>>Any thoughts would be appreciated.
>
>>The way the Replay handles errors can be misleading. There can be a
>>failure near the beginning, then the process seems to get all the way
>>through before you're told about it.
>
>>Is your Replay set to get a dynamic local IP from the router? If so,
>>you may need to refresh it (because of ISP making changes). Otherwise,
>>check carefully. The ISP could have changed DNS servers.
>
>>--
>>Mark Lloyd
>>has a Replay 5xxx
>>http://notstupid.laughingsquid.com
>
>>"The idea that there is an invisible being who
>>created and still runs this old universe is so
>>childish, so obviously contrived, that it is hard to
>>believe anyone with even a modicum of education can
>>still fall for that scam."

--
Mark Lloyd
has a Replay 5xxx
http://notstupid.laughingsquid.com

"The idea that there is an invisible being who
created and still runs this old universe is so
childish, so obviously contrived, that it is hard to
believe anyone with even a modicum of education can
still fall for that scam."
Anonymous
April 3, 2005 1:57:33 AM

Archived from groups: alt.video.ptv.replaytv (More info?)

Hmmm, Probably not explaining the situation too well....

My Ascii art is horrid but:

ISP
|
ISP dsl modem
|
|
My linksys (Static IP)
DNS provided by ISP
---------------------------
| |
| |
my pc replaytv
DNS matches ISP DNS matches ISP
ip provided by ip provided by
linksys linksys


My pc is able to surf the net just fine. The replaytv seems to connect to the
network but fails to complete the transaction.

I just wish there was a better way to look at the actual transactions that replaytv
is trying. Perhaps a hub between the linksys and the replaytv with a
laptop running Etherreal network trace software is my next step.


George Rachor


Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:

>On Sat, 02 Apr 2005 16:41:38 -0600, george@agora.rdrop.com (George
>Rachor) wrote:

>>
>>
>>OK... I've been through completly refreshing the linksys <including dumping all the current leases and aquiring new addresses.>
>>
>>I've verified the linksys and the replaytv have agreed on the ip address being used.
>>I've even tried using a diffent dns with no change.

>You need to use the DNS abbresses provided by your ISP. Different ones
>probably won't work.

>BTW, one exception is if you're using WiRNS.

>>Any idea where to troubleshoot next?
>>

>Looks like your computer (which I suppose is connected to the same
>router) is working on usenet. Does the web work too? I think you may
>not understand DNS too well, but it your computer works, it has
>correct values. Make sure the Replay has the same ones.

>>George
>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>
>>>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>>>Rachor) wrote:
>>
>>>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>>>the program guide just fine
>>>>via my internet connection.
>>>>
>>>>My connection consists of the replaytv on a home network
>>>>behind a linksys router. That router is then connected to the ISP's equipment.
>>>>
>>>>I had to change the settings last night to start updating
>>>>via phone line because something has changed and now updating
>>>>the program guide via the network connection is failing. In watching
>>>>the progress it looks like we get most of the way through
>>>>before getting a message that the update has failed and it will
>>>>try again later. The last message I see is "combining data ..."
>>>>
>>>>I'm trying to figure out if something has changed upstream with my
>>>>ISP or if something has happened to my Linksys.
>>>>
>>>>Any thoughts would be appreciated.
>>
>>>The way the Replay handles errors can be misleading. There can be a
>>>failure near the beginning, then the process seems to get all the way
>>>through before you're told about it.
>>
>>>Is your Replay set to get a dynamic local IP from the router? If so,
>>>you may need to refresh it (because of ISP making changes). Otherwise,
>>>check carefully. The ISP could have changed DNS servers.
>>
>>>--
>>>Mark Lloyd
>>>has a Replay 5xxx
>>>http://notstupid.laughingsquid.com
>>
>>>"The idea that there is an invisible being who
>>>created and still runs this old universe is so
>>>childish, so obviously contrived, that it is hard to
>>>believe anyone with even a modicum of education can
>>>still fall for that scam."

>--
>Mark Lloyd
>has a Replay 5xxx
>http://notstupid.laughingsquid.com

>"The idea that there is an invisible being who
>created and still runs this old universe is so
>childish, so obviously contrived, that it is hard to
>believe anyone with even a modicum of education can
>still fall for that scam."
--
=========================================================
George L. Rachor Jr. george@rachors.com
Hillsboro, Oregon http:rachors.com
United States of America Amateur Radio : KD7DCX
Anonymous
April 3, 2005 5:23:58 AM

Archived from groups: alt.video.ptv.replaytv (More info?)

I don' know about your ISP but I know my ISP dial up is very flaky
around 5am, Now, if I wait till 6am, it settles down and plays nice but
at 5am it's very flaky, I can't, for example, type a reply to a Usenet
message without re-connecting to the service.

Your ISP may also have an hour of the flake. Many do (it's the
maintance hour for the system). You may need to tell your replay to try
a different time of day for it's updates

George Rachor wrote:
> I've got a replaytv model 5508 that up until 2 weeks ago was updateing
> the program guide just fine
> via my internet connection.
>
> My connection consists of the replaytv on a home network
> behind a linksys router. That router is then connected to the ISP's equipment.
>
> I had to change the settings last night to start updating
> via phone line because something has changed and now updating
> the program guide via the network connection is failing. In watching
> the progress it looks like we get most of the way through
> before getting a message that the update has failed and it will
> try again later. The last message I see is "combining data ..."
>
> I'm trying to figure out if something has changed upstream with my
> ISP or if something has happened to my Linksys.
>
> Any thoughts would be appreciated.
>
>

--
John F Davis, in Delightful Detroit. WA8YXM(at)arrl(dot)net
"Nothing adds excitement like something that is none of your business"
Diabetic? http://community.compuserve.com/diabetes
Anonymous
April 3, 2005 8:32:57 AM

Archived from groups: alt.video.ptv.replaytv (More info?)

Have you tried plugging the RTV directly into the dsl modem to eliminate
the router as the problem? Might be worth a try. If you do it reboot the
RTV by unplugging the ethernet cable, then the power cable. Wait 30
seconds, plug in the power then the ethernet cable. Worth trying that
with the router too.

From:George Rachor
george@agora.rdrop.com

> Hmmm, Probably not explaining the situation too well....
>
> My Ascii art is horrid but:
>
> ISP
> |
> ISP dsl modem
> |
> |
> My linksys (Static IP)
> DNS provided by ISP
> ---------------------------
> | |
> | |
> my pc replaytv
> DNS matches ISP DNS matches ISP
> ip provided by ip provided by
> linksys linksys
>
>
> My pc is able to surf the net just fine. The replaytv seems to
> connect to the network but fails to complete the transaction.
>
> I just wish there was a better way to look at the actual transactions
> that replaytv is trying. Perhaps a hub between the linksys and the
> replaytv with a
> laptop running Etherreal network trace software is my next step.
>
>
> George Rachor
>
>
> Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>
>> On Sat, 02 Apr 2005 16:41:38 -0600, george@agora.rdrop.com (George
>> Rachor) wrote:
>
>>>
>>>
>>> OK... I've been through completly refreshing the linksys <including
>>> dumping all the current leases and aquiring new addresses.>
>>>
>>> I've verified the linksys and the replaytv have agreed on the ip
>>> address being used.
>>> I've even tried using a diffent dns with no change.
>
>> You need to use the DNS abbresses provided by your ISP. Different
>> ones probably won't work.
>
>> BTW, one exception is if you're using WiRNS.
>
>>> Any idea where to troubleshoot next?
>>>
>
>> Looks like your computer (which I suppose is connected to the same
>> router) is working on usenet. Does the web work too? I think you may
>> not understand DNS too well, but it your computer works, it has
>> correct values. Make sure the Replay has the same ones.
>
>>> George
>>> Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>>
>>>> On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>>>> Rachor) wrote:
>>>
>>>>> I've got a replaytv model 5508 that up until 2 weeks ago was
>>>>> updateing
>>>>> the program guide just fine
>>>>> via my internet connection.
>>>>>
>>>>> My connection consists of the replaytv on a home network
>>>>> behind a linksys router. That router is then connected to the
>>>>> ISP's equipment.
>>>>>
>>>>> I had to change the settings last night to start updating
>>>>> via phone line because something has changed and now updating
>>>>> the program guide via the network connection is failing. In
>>>>> watching
>>>>> the progress it looks like we get most of the way through
>>>>> before getting a message that the update has failed and it will
>>>>> try again later. The last message I see is "combining data ..."
>>>>>
>>>>> I'm trying to figure out if something has changed upstream with my
>>>>> ISP or if something has happened to my Linksys.
>>>>>
>>>>> Any thoughts would be appreciated.
>>>
>>>> The way the Replay handles errors can be misleading. There can be a
>>>> failure near the beginning, then the process seems to get all the
>>>> way through before you're told about it.
>>>
>>>> Is your Replay set to get a dynamic local IP from the router? If
>>>> so, you may need to refresh it (because of ISP making changes).
>>>> Otherwise, check carefully. The ISP could have changed DNS servers.
>>>
>>>> --
>>>> Mark Lloyd
>>>> has a Replay 5xxx
>>>> http://notstupid.laughingsquid.com
>>>
>>>> "The idea that there is an invisible being who
>>>> created and still runs this old universe is so
>>>> childish, so obviously contrived, that it is hard to
>>>> believe anyone with even a modicum of education can
>>>> still fall for that scam."
>
>> --
>> Mark Lloyd
>> has a Replay 5xxx
>> http://notstupid.laughingsquid.com
>
>> "The idea that there is an invisible being who
>> created and still runs this old universe is so
>> childish, so obviously contrived, that it is hard to
>> believe anyone with even a modicum of education can
>> still fall for that scam."
> --
> =========================================================
> George L. Rachor Jr. george@rachors.com
> Hillsboro, Oregon http:rachors.com
> United States of America Amateur Radio : KD7DCX
Anonymous
April 4, 2005 12:35:43 AM

Archived from groups: alt.video.ptv.replaytv (More info?)

In this case the DNS address you should feed your replay is likely
192.168.1.1 (This is the default for Linksys Routers) or whatever the
routers's local area network IP address is. The router already has the
DNS address for your isp.. Else, you'd not be reading this message

George Rachor wrote:
> Hmmm, Probably not explaining the situation too well....
>
> My Ascii art is horrid but:
>
> ISP
> |
> ISP dsl modem
> |
> |
> My linksys (Static IP)
> DNS provided by ISP
> ---------------------------
> | |
> | |
> my pc replaytv
> DNS matches ISP DNS matches ISP
> ip provided by ip provided by
> linksys linksys
>
>
> My pc is able to surf the net just fine. The replaytv seems to connect to the
> network but fails to complete the transaction.
>
> I just wish there was a better way to look at the actual transactions that replaytv
> is trying. Perhaps a hub between the linksys and the replaytv with a
> laptop running Etherreal network trace software is my next step.
>
>
> George Rachor
>
>
> Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>
>
>>On Sat, 02 Apr 2005 16:41:38 -0600, george@agora.rdrop.com (George
>>Rachor) wrote:
>
>
>>>
>>>OK... I've been through completly refreshing the linksys <including dumping all the current leases and aquiring new addresses.>
>>>
>>>I've verified the linksys and the replaytv have agreed on the ip address being used.
>>>I've even tried using a diffent dns with no change.
>
>
>>You need to use the DNS abbresses provided by your ISP. Different ones
>>probably won't work.
>
>
>>BTW, one exception is if you're using WiRNS.
>
>
>>>Any idea where to troubleshoot next?
>>>
>
>
>>Looks like your computer (which I suppose is connected to the same
>>router) is working on usenet. Does the web work too? I think you may
>>not understand DNS too well, but it your computer works, it has
>>correct values. Make sure the Replay has the same ones.
>
>
>>>George
>>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>>
>>>
>>>>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>>>>Rachor) wrote:
>>>
>>>>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>>>>the program guide just fine
>>>>>via my internet connection.
>>>>>
>>>>>My connection consists of the replaytv on a home network
>>>>>behind a linksys router. That router is then connected to the ISP's equipment.
>>>>>
>>>>>I had to change the settings last night to start updating
>>>>>via phone line because something has changed and now updating
>>>>>the program guide via the network connection is failing. In watching
>>>>>the progress it looks like we get most of the way through
>>>>>before getting a message that the update has failed and it will
>>>>>try again later. The last message I see is "combining data ..."
>>>>>
>>>>>I'm trying to figure out if something has changed upstream with my
>>>>>ISP or if something has happened to my Linksys.
>>>>>
>>>>>Any thoughts would be appreciated.
>>>
>>>>The way the Replay handles errors can be misleading. There can be a
>>>>failure near the beginning, then the process seems to get all the way
>>>>through before you're told about it.
>>>
>>>>Is your Replay set to get a dynamic local IP from the router? If so,
>>>>you may need to refresh it (because of ISP making changes). Otherwise,
>>>>check carefully. The ISP could have changed DNS servers.
>>>
>>>>--
>>>>Mark Lloyd
>>>>has a Replay 5xxx
>>>>http://notstupid.laughingsquid.com
>>>
>>>>"The idea that there is an invisible being who
>>>>created and still runs this old universe is so
>>>>childish, so obviously contrived, that it is hard to
>>>>believe anyone with even a modicum of education can
>>>>still fall for that scam."
>
>
>>--
>>Mark Lloyd
>>has a Replay 5xxx
>>http://notstupid.laughingsquid.com
>
>
>>"The idea that there is an invisible being who
>>created and still runs this old universe is so
>>childish, so obviously contrived, that it is hard to
>>believe anyone with even a modicum of education can
>>still fall for that scam."
>
> --
> =========================================================
> George L. Rachor Jr. george@rachors.com
> Hillsboro, Oregon http:rachors.com
> United States of America Amateur Radio : KD7DCX

--
John F Davis, in Delightful Detroit. WA8YXM(at)arrl(dot)net
"Nothing adds excitement like something that is none of your business"
Diabetic? http://community.compuserve.com/diabetes
Anonymous
April 4, 2005 12:35:44 AM

Archived from groups: alt.video.ptv.replaytv (More info?)

On Sun, 03 Apr 2005 20:35:43 GMT, John in Detroit
<Blanked@sbcglobal.net> wrote:

>In this case the DNS address you should feed your replay is likely
>192.168.1.1 (This is the default for Linksys Routers) or whatever the
>routers's local area network IP address is. The router already has the
>DNS address for your isp.. Else, you'd not be reading this message
>

192.168.1.1 is the default LAN IP, and gateway address (will be used
by computers to access the internet). This is very different from
DNS. Are you saying the router contains a DNS proxy as well? The
manual for my router says nothing about that. Could you give the model
number of one that does have that feature? It would be a useful one to
have.

Or is it you've confused "gateway" and "DNS"?

>George Rachor wrote:
>> Hmmm, Probably not explaining the situation too well....
>>
>> My Ascii art is horrid but:
>>
>> ISP
>> |
>> ISP dsl modem
>> |
>> |
>> My linksys (Static IP)
>> DNS provided by ISP
>> ---------------------------
>> | |
>> | |
>> my pc replaytv
>> DNS matches ISP DNS matches ISP
>> ip provided by ip provided by
>> linksys linksys
>>
>>
>> My pc is able to surf the net just fine. The replaytv seems to connect to the
>> network but fails to complete the transaction.
>>
>> I just wish there was a better way to look at the actual transactions that replaytv
>> is trying. Perhaps a hub between the linksys and the replaytv with a
>> laptop running Etherreal network trace software is my next step.
>>
>>
>> George Rachor
>>
>>
>> Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>
>>
>>>On Sat, 02 Apr 2005 16:41:38 -0600, george@agora.rdrop.com (George
>>>Rachor) wrote:
>>
>>
>>>>
>>>>OK... I've been through completly refreshing the linksys <including dumping all the current leases and aquiring new addresses.>
>>>>
>>>>I've verified the linksys and the replaytv have agreed on the ip address being used.
>>>>I've even tried using a diffent dns with no change.
>>
>>
>>>You need to use the DNS abbresses provided by your ISP. Different ones
>>>probably won't work.
>>
>>
>>>BTW, one exception is if you're using WiRNS.
>>
>>
>>>>Any idea where to troubleshoot next?
>>>>
>>
>>
>>>Looks like your computer (which I suppose is connected to the same
>>>router) is working on usenet. Does the web work too? I think you may
>>>not understand DNS too well, but it your computer works, it has
>>>correct values. Make sure the Replay has the same ones.
>>
>>
>>>>George
>>>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>>>
>>>>
>>>>>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>>>>>Rachor) wrote:
>>>>
>>>>>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>>>>>the program guide just fine
>>>>>>via my internet connection.
>>>>>>
>>>>>>My connection consists of the replaytv on a home network
>>>>>>behind a linksys router. That router is then connected to the ISP's equipment.
>>>>>>
>>>>>>I had to change the settings last night to start updating
>>>>>>via phone line because something has changed and now updating
>>>>>>the program guide via the network connection is failing. In watching
>>>>>>the progress it looks like we get most of the way through
>>>>>>before getting a message that the update has failed and it will
>>>>>>try again later. The last message I see is "combining data ..."
>>>>>>
>>>>>>I'm trying to figure out if something has changed upstream with my
>>>>>>ISP or if something has happened to my Linksys.
>>>>>>
>>>>>>Any thoughts would be appreciated.
>>>>
>>>>>The way the Replay handles errors can be misleading. There can be a
>>>>>failure near the beginning, then the process seems to get all the way
>>>>>through before you're told about it.
>>>>
>>>>>Is your Replay set to get a dynamic local IP from the router? If so,
>>>>>you may need to refresh it (because of ISP making changes). Otherwise,
>>>>>check carefully. The ISP could have changed DNS servers.
>>>>
>>>>>--
>>>>>Mark Lloyd
>>>>>has a Replay 5xxx
>>>>>http://notstupid.laughingsquid.com
>>>>
>>>>>"The idea that there is an invisible being who
>>>>>created and still runs this old universe is so
>>>>>childish, so obviously contrived, that it is hard to
>>>>>believe anyone with even a modicum of education can
>>>>>still fall for that scam."
>>
>>
>>>--
>>>Mark Lloyd
>>>has a Replay 5xxx
>>>http://notstupid.laughingsquid.com
>>
>>
>>>"The idea that there is an invisible being who
>>>created and still runs this old universe is so
>>>childish, so obviously contrived, that it is hard to
>>>believe anyone with even a modicum of education can
>>>still fall for that scam."
>>
>> --
>> =========================================================
>> George L. Rachor Jr. george@rachors.com
>> Hillsboro, Oregon http:rachors.com
>> United States of America Amateur Radio : KD7DCX

--
Mark Lloyd
has a Replay 5xxx
http://notstupid.laughingsquid.com

"The idea that there is an invisible being who
created and still runs this old universe is so
childish, so obviously contrived, that it is hard to
believe anyone with even a modicum of education can
still fall for that scam."
Anonymous
April 4, 2005 4:19:23 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

I use a D-Link DI-514 at home and a Linksys BFEW11S4 at work

Though I can see where you might think I'm confusing "Gateway" with
"DNS" the fact is you should. Where is the DNS, is it local to your LAN
or is it on the WAN (internet) The Gateway is the gateway to all of the
internet, This includes the DNS, Thus the IP address for all things
internet is 192.168.1.1 The router will then forward to the real DNS
(you may have to tell it what the real DNS IP address is) and to any
sites from there. That is why it's a router.

Mark Lloyd wrote:

>
> 192.168.1.1 is the default LAN IP, and gateway address (will be used
> by computers to access the internet). This is very different from
> DNS. Are you saying the router contains a DNS proxy as well? The
> manual for my router says nothing about that. Could you give the model
> number of one that does have that feature? It would be a useful one to
> have.
>
> Or is it you've confused "gateway" and "DNS"?
--
John F Davis, in Delightful Detroit. WA8YXM(at)arrl(dot)net
"Nothing adds excitement like something that is none of your business"
Diabetic? http://community.compuserve.com/diabetes
Anonymous
April 4, 2005 9:58:10 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

On Mon, 04 Apr 2005 12:19:23 GMT, John in Detroit
<Blanked@sbcglobal.net> wrote:

>I use a D-Link DI-514 at home and a Linksys BFEW11S4 at work
>
>Though I can see where you might think I'm confusing "Gateway" with
>"DNS" the fact is you should. Where is the DNS, is it local to your LAN
>or is it on the WAN (internet) The Gateway is the gateway to all of the
>internet, This includes the DNS, Thus the IP address for all things
>internet is 192.168.1.1

That would be nonsense. Like having a post office that always delivers
the mail correctly, even when everyhings addressed to "there".

> The router will then forward to the real DNS

Notice that:

1. That is not the way DCHP sets it for you.

2. The "gateway" is a sort of conduit. You still specify the actual
server addresses. Every time a web page is accessed, the program
(browser) used the IP address of the server. Same with DNS.

>
>(you may have to tell it what the real DNS IP address is)

The router will normally use DHCP to let the ISP set the DNS server
addresses,

>and to any
>sites from there.

>That is why it's a router.

This DNS proxy is a good thing, but it is not an essential function of
a router.

>

Unsually, I would have tried something that easy before posting about
it. I'm trying it now (no matter how unlikely it sounds). Suprisingly,
it seems to work. Note that this may or many not work with any other
router.

>Mark Lloyd wrote:
>
>>
>> 192.168.1.1 is the default LAN IP, and gateway address (will be used
>> by computers to access the internet). This is very different from
>> DNS. Are you saying the router contains a DNS proxy as well? The
>> manual for my router says nothing about that. Could you give the model
>> number of one that does have that feature? It would be a useful one to
>> have.
>>
>> Or is it you've confused "gateway" and "DNS"?

--
Mark Lloyd
has a Replay 5xxx
http://notstupid.laughingsquid.com

"The idea that there is an invisible being who
created and still runs this old universe is so
childish, so obviously contrived, that it is hard to
believe anyone with even a modicum of education can
still fall for that scam."
Anonymous
April 5, 2005 2:54:25 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

When I open a command prompt or DOS prompt window and type IPCONFIG /ALL
and press enter it returns much information about my computer's internet
connections.

It says Gateway 192.168.0.1
It ways DNS 192.168.0.1
And it gives me the IP addrsss I'm using today (Dependent on the network
adapter, 192.168.0.101 if wired, 105 if wireless)

That is at home... Here is the work configuration


1 Ethernet adapter :

Description . . . . . . . . : NETGEAR 108 Mbps Wireless PC Card
WG511T
Physical Address. . . . . . : 00-0F-B5-20-FD-79
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.1.105
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 04 05 05 2:33:16 AM
Lease Expires . . . . . . . : 04 07 05 2:33:16 AM

C:\>

Of course the actual internet connection I'm using is something else
(my IP address munged for reasons you can, I'm sure, understand)

0 Ethernet adapter :



Description . . . . . . . . : PPP Adapter.

Physical Address. . . . . . : 44-45-53-54-00-00

DHCP Enabled. . . . . . . . : Yes

IP Address. . . . . . . . . : ww.xx.yy.xzz
Subnet Mask . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . : ww.xx.yy.zz
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 01 01 80 12:00:00 AM
Lease Expires . . . . . . . : 01 01 80 12:00:00 AM




As you can likely guess. I'm on dial up just now



Mark Lloyd wrote:
> On Mon, 04 Apr 2005 12:19:23 GMT, John in Detroit
> <Blanked@sbcglobal.net> wrote:
>
>
>>I use a D-Link DI-514 at home and a Linksys BFEW11S4 at work
>>
>>Though I can see where you might think I'm confusing "Gateway" with
>>"DNS" the fact is you should. Where is the DNS, is it local to your LAN
>>or is it on the WAN (internet) The Gateway is the gateway to all of the
>>internet, This includes the DNS, Thus the IP address for all things
>>internet is 192.168.1.1
>
>
> That would be nonsense. Like having a post office that always delivers
> the mail correctly, even when everyhings addressed to "there".
>
>
>>The router will then forward to the real DNS
>
>
> Notice that:
>
> 1. That is not the way DCHP sets it for you.
>
> 2. The "gateway" is a sort of conduit. You still specify the actual
> server addresses. Every time a web page is accessed, the program
> (browser) used the IP address of the server. Same with DNS.
>
>
>>(you may have to tell it what the real DNS IP address is)
>
>
> The router will normally use DHCP to let the ISP set the DNS server
> addresses,
>
>
>>and to any
>>sites from there.
>
>
>>That is why it's a router.
>
>
> This DNS proxy is a good thing, but it is not an essential function of
> a router.
>
>
>
> Unsually, I would have tried something that easy before posting about
> it. I'm trying it now (no matter how unlikely it sounds). Suprisingly,
> it seems to work. Note that this may or many not work with any other
> router.
>
>
>>Mark Lloyd wrote:
>>
>>
>>>192.168.1.1 is the default LAN IP, and gateway address (will be used
>>>by computers to access the internet). This is very different from
>>>DNS. Are you saying the router contains a DNS proxy as well? The
>>>manual for my router says nothing about that. Could you give the model
>>>number of one that does have that feature? It would be a useful one to
>>>have.
>>>
>>>Or is it you've confused "gateway" and "DNS"?
>
>

--
John F Davis, in Delightful Detroit. WA8YXM(at)arrl(dot)net
"Nothing adds excitement like something that is none of your business"
Diabetic? http://community.compuserve.com/diabetes
Anonymous
April 5, 2005 2:54:26 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

On Tue, 05 Apr 2005 10:54:25 GMT, John in Detroit
<Blanked@sbcglobal.net> wrote:

>When I open a command prompt or DOS prompt window and type IPCONFIG /ALL
>and press enter it returns much information about my computer's internet
>connections.
>
>It says Gateway 192.168.0.1
>It ways DNS 192.168.0.1
>And it gives me the IP addrsss I'm using today (Dependent on the network
>adapter, 192.168.0.101 if wired, 105 if wireless)
>
>That is at home... Here is the work configuration
>
>
>1 Ethernet adapter :
>
> Description . . . . . . . . : NETGEAR 108 Mbps Wireless PC Card
>WG511T
> Physical Address. . . . . . : 00-0F-B5-20-FD-79
> DHCP Enabled. . . . . . . . : Yes
> IP Address. . . . . . . . . : 192.168.1.105
> Subnet Mask . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . : 192.168.1.1
> Primary WINS Server . . . . :
> Secondary WINS Server . . . :
> Lease Obtained. . . . . . . : 04 05 05 2:33:16 AM
> Lease Expires . . . . . . . : 04 07 05 2:33:16 AM
>
>C:\>
>
>Of course the actual internet connection I'm using is something else
>(my IP address munged for reasons you can, I'm sure, understand)
>
>0 Ethernet adapter :
>
>
>
> Description . . . . . . . . : PPP Adapter.
>
> Physical Address. . . . . . : 44-45-53-54-00-00
>
> DHCP Enabled. . . . . . . . : Yes
>
> IP Address. . . . . . . . . : ww.xx.yy.xzz
> Subnet Mask . . . . . . . . : 255.0.0.0
> Default Gateway . . . . . . : ww.xx.yy.zz
> DHCP Server . . . . . . . . : 255.255.255.255
> Primary WINS Server . . . . :
> Secondary WINS Server . . . :
> Lease Obtained. . . . . . . : 01 01 80 12:00:00 AM
> Lease Expires . . . . . . . : 01 01 80 12:00:00 AM
>
>
>
>
>As you can likely guess. I'm on dial up just now
>
>
>
>Mark Lloyd wrote:
>> On Mon, 04 Apr 2005 12:19:23 GMT, John in Detroit
>> <Blanked@sbcglobal.net> wrote:
>>
>>
>>>I use a D-Link DI-514 at home and a Linksys BFEW11S4 at work
>>>
>>>Though I can see where you might think I'm confusing "Gateway" with
>>>"DNS" the fact is you should. Where is the DNS, is it local to your LAN
>>>or is it on the WAN (internet) The Gateway is the gateway to all of the
>>>internet, This includes the DNS, Thus the IP address for all things
>>>internet is 192.168.1.1
>>
>>
>> That would be nonsense. Like having a post office that always delivers
>> the mail correctly, even when everyhings addressed to "there".
>>
>>
>>>The router will then forward to the real DNS
>>
>>
>> Notice that:
>>
>> 1. That is not the way DCHP sets it for you.
>>
>> 2. The "gateway" is a sort of conduit. You still specify the actual
>> server addresses. Every time a web page is accessed, the program
>> (browser) used the IP address of the server. Same with DNS.
>>
>>
>>>(you may have to tell it what the real DNS IP address is)
>>
>>
>> The router will normally use DHCP to let the ISP set the DNS server
>> addresses,
>>
>>
>>>and to any
>>>sites from there.
>>
>>
>>>That is why it's a router.
>>
>>
>> This DNS proxy is a good thing, but it is not an essential function of
>> a router.
>>
>>
>>
>> Unsually, I would have tried something that easy before posting about
>> it. I'm trying it now (no matter how unlikely it sounds). Suprisingly,
>> it seems to work. Note that this may or many not work with any other
>> router.
>>
>>
>>>Mark Lloyd wrote:
>>>
>>>
>>>>192.168.1.1 is the default LAN IP, and gateway address (will be used
>>>>by computers to access the internet). This is very different from
>>>>DNS. Are you saying the router contains a DNS proxy as well? The
>>>>manual for my router says nothing about that. Could you give the model
>>>>number of one that does have that feature? It would be a useful one to
>>>>have.
>>>>
>>>>Or is it you've confused "gateway" and "DNS"?
>>
>>

--
Mark Lloyd
has a Replay 5xxx
http://notstupid.laughingsquid.com

"The idea that there is an invisible being who
created and still runs this old universe is so
childish, so obviously contrived, that it is hard to
believe anyone with even a modicum of education can
still fall for that scam."
Anonymous
April 5, 2005 2:54:26 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

On Tue, 05 Apr 2005 10:54:25 GMT, John in Detroit
<Blanked@sbcglobal.net> wrote:

>When I open a command prompt or DOS prompt window and type IPCONFIG /ALL
>and press enter it returns much information about my computer's internet
>connections.
>
>It says Gateway 192.168.0.1
>It ways DNS 192.168.0.1
>And it gives me the IP addrsss I'm using today (Dependent on the network
>adapter, 192.168.0.101 if wired, 105 if wireless)
>

You didn't say this is being sdet by DHCP (I think it as, but it would
help to be clearer about it).

>That is at home... Here is the work configuration
>

Below, you do specify DHCP, but leave out DNS. Looks bit like trying
to be unhelpful.

I have that same model of router (Linksys) and would be interested in
knowing.

>
>1 Ethernet adapter :
>
> Description . . . . . . . . : NETGEAR 108 Mbps Wireless PC Card
>WG511T
> Physical Address. . . . . . : 00-0F-B5-20-FD-79
> DHCP Enabled. . . . . . . . : Yes
> IP Address. . . . . . . . . : 192.168.1.105
> Subnet Mask . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . : 192.168.1.1
> Primary WINS Server . . . . :
> Secondary WINS Server . . . :
> Lease Obtained. . . . . . . : 04 05 05 2:33:16 AM
> Lease Expires . . . . . . . : 04 07 05 2:33:16 AM
>
>C:\>
>
>Of course the actual internet connection I'm using is something else
>(my IP address munged for reasons you can, I'm sure, understand)
>

This would be a LAN (local network) address, and meaningless on the
internet.

>0 Ethernet adapter :
>
>
>
> Description . . . . . . . . : PPP Adapter.
>
> Physical Address. . . . . . : 44-45-53-54-00-00
>
> DHCP Enabled. . . . . . . . : Yes
>
> IP Address. . . . . . . . . : ww.xx.yy.xzz
> Subnet Mask . . . . . . . . : 255.0.0.0
> Default Gateway . . . . . . : ww.xx.yy.zz
> DHCP Server . . . . . . . . : 255.255.255.255
> Primary WINS Server . . . . :
> Secondary WINS Server . . . :
> Lease Obtained. . . . . . . : 01 01 80 12:00:00 AM
> Lease Expires . . . . . . . : 01 01 80 12:00:00 AM
>
>
>
>
>As you can likely guess. I'm on dial up just now
>
>
>
>Mark Lloyd wrote:
>> On Mon, 04 Apr 2005 12:19:23 GMT, John in Detroit
>> <Blanked@sbcglobal.net> wrote:
>>
>>
>>>I use a D-Link DI-514 at home and a Linksys BFEW11S4 at work
>>>
>>>Though I can see where you might think I'm confusing "Gateway" with
>>>"DNS" the fact is you should. Where is the DNS, is it local to your LAN
>>>or is it on the WAN (internet) The Gateway is the gateway to all of the
>>>internet, This includes the DNS, Thus the IP address for all things
>>>internet is 192.168.1.1
>>
>>
>> That would be nonsense. Like having a post office that always delivers
>> the mail correctly, even when everyhings addressed to "there".
>>
>>
>>>The router will then forward to the real DNS
>>
>>
>> Notice that:
>>
>> 1. That is not the way DCHP sets it for you.
>>
>> 2. The "gateway" is a sort of conduit. You still specify the actual
>> server addresses. Every time a web page is accessed, the program
>> (browser) used the IP address of the server. Same with DNS.
>>
>>
>>>(you may have to tell it what the real DNS IP address is)
>>
>>
>> The router will normally use DHCP to let the ISP set the DNS server
>> addresses,
>>
>>
>>>and to any
>>>sites from there.
>>
>>
>>>That is why it's a router.
>>
>>
>> This DNS proxy is a good thing, but it is not an essential function of
>> a router.
>>
>>
>>
>> Unsually, I would have tried something that easy before posting about
>> it. I'm trying it now (no matter how unlikely it sounds). Suprisingly,
>> it seems to work. Note that this may or many not work with any other
>> router.
>>
>>
>>>Mark Lloyd wrote:
>>>
>>>
>>>>192.168.1.1 is the default LAN IP, and gateway address (will be used
>>>>by computers to access the internet). This is very different from
>>>>DNS. Are you saying the router contains a DNS proxy as well? The
>>>>manual for my router says nothing about that. Could you give the model
>>>>number of one that does have that feature? It would be a useful one to
>>>>have.
>>>>
>>>>Or is it you've confused "gateway" and "DNS"?
>>
>>

--
Mark Lloyd
has a Replay 5xxx
http://notstupid.laughingsquid.com

"The idea that there is an invisible being who
created and still runs this old universe is so
childish, so obviously contrived, that it is hard to
believe anyone with even a modicum of education can
still fall for that scam."
Anonymous
April 6, 2005 3:54:21 AM

Archived from groups: alt.video.ptv.replaytv (More info?)

Mark I could not find any reply in your last reply

I'm at home now, double checked using winipcfg and hitting the MORE tab
(I just noticed the info i posted this morning did not included a DNS
list) shows the DNS and it's 192.168.0.1 the router's IP address

I do agree with the poster that said DNS proxy is not an essential
function of a router, but imagine this... Draw two circles, In one
circle marked LAN you have everything that is in your house/office,
(Note, Lans need not be limited to a single building, I know of many
multile site lans) On the very edge of this is a box marked "ROUTER" and
everything in the circle has a line to that box.

On the "outside" of the circle is a line coming from the ROUTER box to
the other circle... This line is marked "Gateway" The other circle is
THE INTERNET and it contains every URL, every IP address, Every Web page
or FTP site or IRC host or whatever which is NOT in the first circle

As you can see, To your computer everything in the world is
192.168.0/1.1 (zero or 1 in the third group depending on D-link or
Linksys) or whatever IP address your router has from within the LAN
EVERYTHING This includes the DNS server

Mark Lloyd wrote:


--
John F Davis, in Delightful Detroit. WA8YXM(at)arrl(dot)net
"Nothing adds excitement like something that is none of your business"
Diabetic? http://community.compuserve.com/diabetes
Anonymous
April 6, 2005 3:56:06 AM

Archived from groups: alt.video.ptv.replaytv (More info?)

Mark, see my other reply.. I caught that this evening (I work nights, 13
hour shifts and the last reply was sent at the end of shift, I'm much
better rested now) When I'm at home, it clearly shows the DNS being
192.168.0.1 (D-Link router) Explained in other post

Mark Lloyd wrote:
> On Tue, 05 Apr 2005 10:54:25 GMT, John in Detroit
> <Blanked@sbcglobal.net> wrote:
>
>
>>When I open a command prompt or DOS prompt window and type IPCONFIG /ALL
>>and press enter it returns much information about my computer's internet
>>connections.
>>
>>It says Gateway 192.168.0.1
>>It ways DNS 192.168.0.1
>>And it gives me the IP addrsss I'm using today (Dependent on the network
>>adapter, 192.168.0.101 if wired, 105 if wireless)
>>
>
>
> You didn't say this is being sdet by DHCP (I think it as, but it would
> help to be clearer about it).
>
>
>>That is at home... Here is the work configuration
>>
>
>
> Below, you do specify DHCP, but leave out DNS. Looks bit like trying
> to be unhelpful.
>
> I have that same model of router (Linksys) and would be interested in
> knowing.
>
>
>>1 Ethernet adapter :
>>
>> Description . . . . . . . . : NETGEAR 108 Mbps Wireless PC Card
>>WG511T
>> Physical Address. . . . . . : 00-0F-B5-20-FD-79
>> DHCP Enabled. . . . . . . . : Yes
>> IP Address. . . . . . . . . : 192.168.1.105
>> Subnet Mask . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . : 192.168.1.1
>> DHCP Server . . . . . . . . : 192.168.1.1
>> Primary WINS Server . . . . :
>> Secondary WINS Server . . . :
>> Lease Obtained. . . . . . . : 04 05 05 2:33:16 AM
>> Lease Expires . . . . . . . : 04 07 05 2:33:16 AM
>>
>>C:\>
>>
>>Of course the actual internet connection I'm using is something else
>>(my IP address munged for reasons you can, I'm sure, understand)
>>
>
>
> This would be a LAN (local network) address, and meaningless on the
> internet.
>
>
>>0 Ethernet adapter :
>>
>>
>>
>> Description . . . . . . . . : PPP Adapter.
>>
>> Physical Address. . . . . . : 44-45-53-54-00-00
>>
>> DHCP Enabled. . . . . . . . : Yes
>>
>> IP Address. . . . . . . . . : ww.xx.yy.xzz
>> Subnet Mask . . . . . . . . : 255.0.0.0
>> Default Gateway . . . . . . : ww.xx.yy.zz
>> DHCP Server . . . . . . . . : 255.255.255.255
>> Primary WINS Server . . . . :
>> Secondary WINS Server . . . :
>> Lease Obtained. . . . . . . : 01 01 80 12:00:00 AM
>> Lease Expires . . . . . . . : 01 01 80 12:00:00 AM
>>
>>
>>
>>
>>As you can likely guess. I'm on dial up just now
>>
>>
>>
>>Mark Lloyd wrote:
>>
>>>On Mon, 04 Apr 2005 12:19:23 GMT, John in Detroit
>>><Blanked@sbcglobal.net> wrote:
>>>
>>>
>>>
>>>>I use a D-Link DI-514 at home and a Linksys BFEW11S4 at work
>>>>
>>>>Though I can see where you might think I'm confusing "Gateway" with
>>>>"DNS" the fact is you should. Where is the DNS, is it local to your LAN
>>>>or is it on the WAN (internet) The Gateway is the gateway to all of the
>>>>internet, This includes the DNS, Thus the IP address for all things
>>>>internet is 192.168.1.1
>>>
>>>
>>>That would be nonsense. Like having a post office that always delivers
>>>the mail correctly, even when everyhings addressed to "there".
>>>
>>>
>>>
>>>>The router will then forward to the real DNS
>>>
>>>
>>>Notice that:
>>>
>>>1. That is not the way DCHP sets it for you.
>>>
>>>2. The "gateway" is a sort of conduit. You still specify the actual
>>>server addresses. Every time a web page is accessed, the program
>>>(browser) used the IP address of the server. Same with DNS.
>>>
>>>
>>>
>>>>(you may have to tell it what the real DNS IP address is)
>>>
>>>
>>>The router will normally use DHCP to let the ISP set the DNS server
>>>addresses,
>>>
>>>
>>>
>>>>and to any
>>>>sites from there.
>>>
>>>
>>>>That is why it's a router.
>>>
>>>
>>>This DNS proxy is a good thing, but it is not an essential function of
>>>a router.
>>>
>>>
>>>
>>>Unsually, I would have tried something that easy before posting about
>>>it. I'm trying it now (no matter how unlikely it sounds). Suprisingly,
>>>it seems to work. Note that this may or many not work with any other
>>>router.
>>>
>>>
>>>
>>>>Mark Lloyd wrote:
>>>>
>>>>
>>>>
>>>>>192.168.1.1 is the default LAN IP, and gateway address (will be used
>>>>>by computers to access the internet). This is very different from
>>>>>DNS. Are you saying the router contains a DNS proxy as well? The
>>>>>manual for my router says nothing about that. Could you give the model
>>>>>number of one that does have that feature? It would be a useful one to
>>>>>have.
>>>>>
>>>>>Or is it you've confused "gateway" and "DNS"?
>>>
>>>
>

--
John F Davis, in Delightful Detroit. WA8YXM(at)arrl(dot)net
"Nothing adds excitement like something that is none of your business"
Diabetic? http://community.compuserve.com/diabetes
Anonymous
April 6, 2005 1:43:42 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

On Tue, 05 Apr 2005 23:54:21 GMT, John in Detroit
<Blanked@sbcglobal.net> wrote:

>Mark I could not find any reply in your last reply
>

Sorry, I unintentionally hit 'send' too soon. I did make a reply just
after that.

>I'm at home now, double checked using winipcfg and hitting the MORE tab
>(I just noticed the info i posted this morning did not included a DNS
>list) shows the DNS and it's 192.168.0.1 the router's IP address
>
>I do agree with the poster that said DNS proxy is not an essential
>function of a router

And I said it was a desirable feature.

>, but imagine this... Draw two circles, In one
>circle marked LAN you have everything that is in your house/office,
>(Note, Lans need not be limited to a single building, I know of many
>multile site lans) On the very edge of this is a box marked "ROUTER" and
>everything in the circle has a line to that box.
>
>On the "outside" of the circle is a line coming from the ROUTER box to
>the other circle... This line is marked "Gateway" The other circle is
>THE INTERNET and it contains every URL, every IP address, Every Web page
>or FTP site or IRC host or whatever which is NOT in the first circle
>
>As you can see, To your computer everything in the world is
>192.168.0/1.1 (zero or 1 in the third group depending on D-link or
>Linksys) or whatever IP address your router has from within the LAN
>EVERYTHING This includes the DNS server
>

Think about that. If EVERYTHING was 192.168.1.1 (or whatever), web
servers would have no way to distinguish between them (I'm thinking
about that "South Park" episode where everyone and everything was
called "Marklar"). 192.168.1.1 is the LAN address or the ROUTER.
Internet servers (including DNS) have thier own addresses, which
programs (clients) use to access them.

>Mark Lloyd wrote:

--
Mark Lloyd
has a Replay 5xxx
http://notstupid.laughingsquid.com

"The idea that there is an invisible being who
created and still runs this old universe is so
childish, so obviously contrived, that it is hard to
believe anyone with even a modicum of education can
still fall for that scam."
Anonymous
April 7, 2005 5:56:13 AM

Archived from groups: alt.video.ptv.replaytv (More info?)

No, The client on your computer sees only one address The router, The
router is the one that goes out on the web and sees all the other
addresses, but your terminal client (Mail, News, WWW whatever) sees only
the router It is the gate through which all data must pass

Mark Lloyd wrote:
>
> Think about that. If EVERYTHING was 192.168.1.1 (or whatever), web
> servers would have no way to distinguish between them (I'm thinking
> about that "South Park" episode where everyone and everything was
> called "Marklar"). 192.168.1.1 is the LAN address or the ROUTER.
> Internet servers (including DNS) have thier own addresses, which
> programs (clients) use to access them.
>
>
>>Mark Lloyd wrote:
>
>

--
John F Davis, in Delightful Detroit. WA8YXM(at)arrl(dot)net
"Nothing adds excitement like something that is none of your business"
Diabetic? http://community.compuserve.com/diabetes
Anonymous
April 11, 2005 1:03:34 AM

Archived from groups: alt.video.ptv.replaytv (More info?)

Mark,


I bypassed the linksys and got the same result (Most of the way through the transaction
to replay then a failure message.

I put a sniffer on the network line between the replay and my homenetwork.

1. The replay is getting the time via ntp from production.replaytv.net
2. On the first HTTP Get to production.replaytv.net I see the following curious
line:
Dissector bug, protocol HTTP: "Request URI" - "http.request.uri" invalid length: -5 (proto.c:2104)


The following HTTP Gets have the same curious line...

Any new thoughts?

George Rachor


Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:

>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>Rachor) wrote:

>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>the program guide just fine
>>via my internet connection.
>>
>>My connection consists of the replaytv on a home network
>>behind a linksys router. That router is then connected to the ISP's equipment.
>>
>>I had to change the settings last night to start updating
>>via phone line because something has changed and now updating
>>the program guide via the network connection is failing. In watching
>>the progress it looks like we get most of the way through
>>before getting a message that the update has failed and it will
>>try again later. The last message I see is "combining data ..."
>>
>>I'm trying to figure out if something has changed upstream with my
>>ISP or if something has happened to my Linksys.
>>
>>Any thoughts would be appreciated.

>The way the Replay handles errors can be misleading. There can be a
>failure near the beginning, then the process seems to get all the way
>through before you're told about it.

>Is your Replay set to get a dynamic local IP from the router? If so,
>you may need to refresh it (because of ISP making changes). Otherwise,
>check carefully. The ISP could have changed DNS servers.

>--
>Mark Lloyd
>has a Replay 5xxx
>http://notstupid.laughingsquid.com

>"The idea that there is an invisible being who
>created and still runs this old universe is so
>childish, so obviously contrived, that it is hard to
>believe anyone with even a modicum of education can
>still fall for that scam."
--
=========================================================
George L. Rachor Jr. george@rachors.com
Hillsboro, Oregon http:rachors.com
United States of America Amateur Radio : KD7DCX
Anonymous
April 11, 2005 2:49:23 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

On Sun, 10 Apr 2005 21:03:34 -0500, george@agora.rdrop.com (George
Rachor) wrote:

>Mark,
>
>
>I bypassed the linksys and got the same result (Most of the way through the transaction
>to replay then a failure message.
>
>I put a sniffer on the network line between the replay and my homenetwork.
>
>1. The replay is getting the time via ntp from production.replaytv.net
>2. On the first HTTP Get to production.replaytv.net I see the following curious
> line:
> Dissector bug, protocol HTTP: "Request URI" - "http.request.uri" invalid length: -5 (proto.c:2104)
>
>
>The following HTTP Gets have the same curious line...
>
>Any new thoughts?
>

The problem may involve merging new information with an existing
(corrupted) guide. Try clearing the Replay guide using 2-4-3-Zones
option 2 (people say you need to do this 2 times), then requesting a
new guide (manual connect).

>George Rachor
>
>
>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>
>>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>>Rachor) wrote:
>
>>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>>the program guide just fine
>>>via my internet connection.
>>>
>>>My connection consists of the replaytv on a home network
>>>behind a linksys router. That router is then connected to the ISP's equipment.
>>>
>>>I had to change the settings last night to start updating
>>>via phone line because something has changed and now updating
>>>the program guide via the network connection is failing. In watching
>>>the progress it looks like we get most of the way through
>>>before getting a message that the update has failed and it will
>>>try again later. The last message I see is "combining data ..."
>>>
>>>I'm trying to figure out if something has changed upstream with my
>>>ISP or if something has happened to my Linksys.
>>>
>>>Any thoughts would be appreciated.
>
>>The way the Replay handles errors can be misleading. There can be a
>>failure near the beginning, then the process seems to get all the way
>>through before you're told about it.
>
>>Is your Replay set to get a dynamic local IP from the router? If so,
>>you may need to refresh it (because of ISP making changes). Otherwise,
>>check carefully. The ISP could have changed DNS servers.
>
>>--
>>Mark Lloyd
>>has a Replay 5xxx
>>http://notstupid.laughingsquid.com
>
>>"The idea that there is an invisible being who
>>created and still runs this old universe is so
>>childish, so obviously contrived, that it is hard to
>>believe anyone with even a modicum of education can
>>still fall for that scam."

--
Mark Lloyd
has a Replay 5xxx
http://notstupid.laughingsquid.com

"The idea that there is an invisible being who
created and still runs this old universe is so
childish, so obviously contrived, that it is hard to
believe anyone with even a modicum of education can
still fall for that scam."
Anonymous
April 12, 2005 12:55:13 AM

Archived from groups: alt.video.ptv.replaytv (More info?)

Hmmm,

I tried clearing the guide but only once. I'll try clearing the guide twice
and see if that makes a difference.

George


Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:

>On Sun, 10 Apr 2005 21:03:34 -0500, george@agora.rdrop.com (George
>Rachor) wrote:

>>Mark,
>>
>>
>>I bypassed the linksys and got the same result (Most of the way through the transaction
>>to replay then a failure message.
>>
>>I put a sniffer on the network line between the replay and my homenetwork.
>>
>>1. The replay is getting the time via ntp from production.replaytv.net
>>2. On the first HTTP Get to production.replaytv.net I see the following curious
>> line:
>> Dissector bug, protocol HTTP: "Request URI" - "http.request.uri" invalid length: -5 (proto.c:2104)
>>
>>
>>The following HTTP Gets have the same curious line...
>>
>>Any new thoughts?
>>

>The problem may involve merging new information with an existing
>(corrupted) guide. Try clearing the Replay guide using 2-4-3-Zones
>option 2 (people say you need to do this 2 times), then requesting a
>new guide (manual connect).

>>George Rachor
>>
>>
>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>
>>>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>>>Rachor) wrote:
>>
>>>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>>>the program guide just fine
>>>>via my internet connection.
>>>>
>>>>My connection consists of the replaytv on a home network
>>>>behind a linksys router. That router is then connected to the ISP's equipment.
>>>>
>>>>I had to change the settings last night to start updating
>>>>via phone line because something has changed and now updating
>>>>the program guide via the network connection is failing. In watching
>>>>the progress it looks like we get most of the way through
>>>>before getting a message that the update has failed and it will
>>>>try again later. The last message I see is "combining data ..."
>>>>
>>>>I'm trying to figure out if something has changed upstream with my
>>>>ISP or if something has happened to my Linksys.
>>>>
>>>>Any thoughts would be appreciated.
>>
>>>The way the Replay handles errors can be misleading. There can be a
>>>failure near the beginning, then the process seems to get all the way
>>>through before you're told about it.
>>
>>>Is your Replay set to get a dynamic local IP from the router? If so,
>>>you may need to refresh it (because of ISP making changes). Otherwise,
>>>check carefully. The ISP could have changed DNS servers.
>>
>>>--
>>>Mark Lloyd
>>>has a Replay 5xxx
>>>http://notstupid.laughingsquid.com
>>
>>>"The idea that there is an invisible being who
>>>created and still runs this old universe is so
>>>childish, so obviously contrived, that it is hard to
>>>believe anyone with even a modicum of education can
>>>still fall for that scam."

>--
>Mark Lloyd
>has a Replay 5xxx
>http://notstupid.laughingsquid.com

>"The idea that there is an invisible being who
>created and still runs this old universe is so
>childish, so obviously contrived, that it is hard to
>believe anyone with even a modicum of education can
>still fall for that scam."
--
=========================================================
George L. Rachor Jr. george@rachors.com
Hillsboro, Oregon http:rachors.com
United States of America Amateur Radio : KD7DCX
Anonymous
April 12, 2005 3:53:19 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

OK... Cleared the guide twice but still getting the error right after 'combining data'.

I had to change back to dialup to get the guide re-populated...

I'm tempted to buy another replay and see if it has the same problem. That would let me determine
if the problem is in the unit (bad software) or upstream in my network.
I was thinking about another replay anyway.

George


Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:

>On Sun, 10 Apr 2005 21:03:34 -0500, george@agora.rdrop.com (George
>Rachor) wrote:

>>Mark,
>>
>>
>>I bypassed the linksys and got the same result (Most of the way through the transaction
>>to replay then a failure message.
>>
>>I put a sniffer on the network line between the replay and my homenetwork.
>>
>>1. The replay is getting the time via ntp from production.replaytv.net
>>2. On the first HTTP Get to production.replaytv.net I see the following curious
>> line:
>> Dissector bug, protocol HTTP: "Request URI" - "http.request.uri" invalid length: -5 (proto.c:2104)
>>
>>
>>The following HTTP Gets have the same curious line...
>>
>>Any new thoughts?
>>

>The problem may involve merging new information with an existing
>(corrupted) guide. Try clearing the Replay guide using 2-4-3-Zones
>option 2 (people say you need to do this 2 times), then requesting a
>new guide (manual connect).

>>George Rachor
>>
>>
>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>
>>>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>>>Rachor) wrote:
>>
>>>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>>>the program guide just fine
>>>>via my internet connection.
>>>>
>>>>My connection consists of the replaytv on a home network
>>>>behind a linksys router. That router is then connected to the ISP's equipment.
>>>>
>>>>I had to change the settings last night to start updating
>>>>via phone line because something has changed and now updating
>>>>the program guide via the network connection is failing. In watching
>>>>the progress it looks like we get most of the way through
>>>>before getting a message that the update has failed and it will
>>>>try again later. The last message I see is "combining data ..."
>>>>
>>>>I'm trying to figure out if something has changed upstream with my
>>>>ISP or if something has happened to my Linksys.
>>>>
>>>>Any thoughts would be appreciated.
>>
>>>The way the Replay handles errors can be misleading. There can be a
>>>failure near the beginning, then the process seems to get all the way
>>>through before you're told about it.
>>
>>>Is your Replay set to get a dynamic local IP from the router? If so,
>>>you may need to refresh it (because of ISP making changes). Otherwise,
>>>check carefully. The ISP could have changed DNS servers.
>>
>>>--
>>>Mark Lloyd
>>>has a Replay 5xxx
>>>http://notstupid.laughingsquid.com
>>
>>>"The idea that there is an invisible being who
>>>created and still runs this old universe is so
>>>childish, so obviously contrived, that it is hard to
>>>believe anyone with even a modicum of education can
>>>still fall for that scam."

>--
>Mark Lloyd
>has a Replay 5xxx
>http://notstupid.laughingsquid.com

>"The idea that there is an invisible being who
>created and still runs this old universe is so
>childish, so obviously contrived, that it is hard to
>believe anyone with even a modicum of education can
>still fall for that scam."
--
=========================================================
George L. Rachor Jr. george@rachors.com
Hillsboro, Oregon http:rachors.com
United States of America Amateur Radio : KD7DCX
Anonymous
April 12, 2005 4:58:42 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

On Tue, 12 Apr 2005 11:53:19 -0500, george@agora.rdrop.com (George
Rachor) wrote:

>
>OK... Cleared the guide twice but still getting the error right after 'combining data'.
>
>I had to change back to dialup to get the guide re-populated...
>
>I'm tempted to buy another replay and see if it has the same problem. That would let me determine
>if the problem is in the unit (bad software) or upstream in my network.
>I was thinking about another replay anyway.
>
>George
>

It's spending more money, but probably a good idea. Problems are
easier to locate when you have multiple units.

>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>
>>On Sun, 10 Apr 2005 21:03:34 -0500, george@agora.rdrop.com (George
>>Rachor) wrote:
>
>>>Mark,
>>>
>>>
>>>I bypassed the linksys and got the same result (Most of the way through the transaction
>>>to replay then a failure message.
>>>
>>>I put a sniffer on the network line between the replay and my homenetwork.
>>>
>>>1. The replay is getting the time via ntp from production.replaytv.net
>>>2. On the first HTTP Get to production.replaytv.net I see the following curious
>>> line:
>>> Dissector bug, protocol HTTP: "Request URI" - "http.request.uri" invalid length: -5 (proto.c:2104)
>>>
>>>
>>>The following HTTP Gets have the same curious line...
>>>
>>>Any new thoughts?
>>>
>
>>The problem may involve merging new information with an existing
>>(corrupted) guide. Try clearing the Replay guide using 2-4-3-Zones
>>option 2 (people say you need to do this 2 times), then requesting a
>>new guide (manual connect).
>
>>>George Rachor
>>>
>>>
>>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>>
>>>>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>>>>Rachor) wrote:
>>>
>>>>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>>>>the program guide just fine
>>>>>via my internet connection.
>>>>>
>>>>>My connection consists of the replaytv on a home network
>>>>>behind a linksys router. That router is then connected to the ISP's equipment.
>>>>>
>>>>>I had to change the settings last night to start updating
>>>>>via phone line because something has changed and now updating
>>>>>the program guide via the network connection is failing. In watching
>>>>>the progress it looks like we get most of the way through
>>>>>before getting a message that the update has failed and it will
>>>>>try again later. The last message I see is "combining data ..."
>>>>>
>>>>>I'm trying to figure out if something has changed upstream with my
>>>>>ISP or if something has happened to my Linksys.
>>>>>
>>>>>Any thoughts would be appreciated.
>>>
>>>>The way the Replay handles errors can be misleading. There can be a
>>>>failure near the beginning, then the process seems to get all the way
>>>>through before you're told about it.
>>>
>>>>Is your Replay set to get a dynamic local IP from the router? If so,
>>>>you may need to refresh it (because of ISP making changes). Otherwise,
>>>>check carefully. The ISP could have changed DNS servers.
>>>
>>>>--
>>>>Mark Lloyd
>>>>has a Replay 5xxx
>>>>http://notstupid.laughingsquid.com
>>>
>>>>"The idea that there is an invisible being who
>>>>created and still runs this old universe is so
>>>>childish, so obviously contrived, that it is hard to
>>>>believe anyone with even a modicum of education can
>>>>still fall for that scam."
>
>>--
>>Mark Lloyd
>>has a Replay 5xxx
>>http://notstupid.laughingsquid.com
>
>>"The idea that there is an invisible being who
>>created and still runs this old universe is so
>>childish, so obviously contrived, that it is hard to
>>believe anyone with even a modicum of education can
>>still fall for that scam."

--
Mark Lloyd
has a Replay 5xxx
http://notstupid.laughingsquid.com

"The idea that there is an invisible being who
created and still runs this old universe is so
childish, so obviously contrived, that it is hard to
believe anyone with even a modicum of education can
still fall for that scam."
Anonymous
April 12, 2005 9:32:27 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

I was going to get one anyway.... Might as well do it now.

I did notice one more difference between dialup conversations
and ethernet conversation.

When doing Ethernet based conversations I see dialog about getting replayzones. There
is a seperate message for zones 1-16 and I don't see this with the phone based
conversations.

Thanks for the suggestions.

George Rachor
george@rachors.com

Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:


>On Tue, 12 Apr 2005 11:53:19 -0500, george@agora.rdrop.com (George
>Rachor) wrote:

>>
>>OK... Cleared the guide twice but still getting the error right after 'combining data'.
>>
>>I had to change back to dialup to get the guide re-populated...
>>
>>I'm tempted to buy another replay and see if it has the same problem. That would let me determine
>>if the problem is in the unit (bad software) or upstream in my network.
>>I was thinking about another replay anyway.
>>
>>George
>>

>It's spending more money, but probably a good idea. Problems are
>easier to locate when you have multiple units.

>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>
>>>On Sun, 10 Apr 2005 21:03:34 -0500, george@agora.rdrop.com (George
>>>Rachor) wrote:
>>
>>>>Mark,
>>>>
>>>>
>>>>I bypassed the linksys and got the same result (Most of the way through the transaction
>>>>to replay then a failure message.
>>>>
>>>>I put a sniffer on the network line between the replay and my homenetwork.
>>>>
>>>>1. The replay is getting the time via ntp from production.replaytv.net
>>>>2. On the first HTTP Get to production.replaytv.net I see the following curious
>>>> line:
>>>> Dissector bug, protocol HTTP: "Request URI" - "http.request.uri" invalid length: -5 (proto.c:2104)
>>>>
>>>>
>>>>The following HTTP Gets have the same curious line...
>>>>
>>>>Any new thoughts?
>>>>
>>
>>>The problem may involve merging new information with an existing
>>>(corrupted) guide. Try clearing the Replay guide using 2-4-3-Zones
>>>option 2 (people say you need to do this 2 times), then requesting a
>>>new guide (manual connect).
>>
>>>>George Rachor
>>>>
>>>>
>>>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>>>
>>>>>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>>>>>Rachor) wrote:
>>>>
>>>>>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>>>>>the program guide just fine
>>>>>>via my internet connection.
>>>>>>
>>>>>>My connection consists of the replaytv on a home network
>>>>>>behind a linksys router. That router is then connected to the ISP's equipment.
>>>>>>
>>>>>>I had to change the settings last night to start updating
>>>>>>via phone line because something has changed and now updating
>>>>>>the program guide via the network connection is failing. In watching
>>>>>>the progress it looks like we get most of the way through
>>>>>>before getting a message that the update has failed and it will
>>>>>>try again later. The last message I see is "combining data ..."
>>>>>>
>>>>>>I'm trying to figure out if something has changed upstream with my
>>>>>>ISP or if something has happened to my Linksys.
>>>>>>
>>>>>>Any thoughts would be appreciated.
>>>>
>>>>>The way the Replay handles errors can be misleading. There can be a
>>>>>failure near the beginning, then the process seems to get all the way
>>>>>through before you're told about it.
>>>>
>>>>>Is your Replay set to get a dynamic local IP from the router? If so,
>>>>>you may need to refresh it (because of ISP making changes). Otherwise,
>>>>>check carefully. The ISP could have changed DNS servers.
>>>>
>>>>>--
>>>>>Mark Lloyd
>>>>>has a Replay 5xxx
>>>>>http://notstupid.laughingsquid.com
>>>>
>>>>>"The idea that there is an invisible being who
>>>>>created and still runs this old universe is so
>>>>>childish, so obviously contrived, that it is hard to
>>>>>believe anyone with even a modicum of education can
>>>>>still fall for that scam."
>>
>>>--
>>>Mark Lloyd
>>>has a Replay 5xxx
>>>http://notstupid.laughingsquid.com
>>
>>>"The idea that there is an invisible being who
>>>created and still runs this old universe is so
>>>childish, so obviously contrived, that it is hard to
>>>believe anyone with even a modicum of education can
>>>still fall for that scam."

>--
>Mark Lloyd
>has a Replay 5xxx
>http://notstupid.laughingsquid.com

>"The idea that there is an invisible being who
>created and still runs this old universe is so
>childish, so obviously contrived, that it is hard to
>believe anyone with even a modicum of education can
>still fall for that scam."
--
=========================================================
George L. Rachor Jr. george@rachors.com
Hillsboro, Oregon http:rachors.com
United States of America Amateur Radio : KD7DCX
Anonymous
April 13, 2005 3:42:06 AM

Archived from groups: alt.video.ptv.replaytv (More info?)

george@agora.rdrop.com (George Rachor) writes:
OK... Looked again at Etherreal packets between my replay and production.replaytv.net and discovered that my replaytv
is sending a series of commands for which production.replaytv.net is returning the message
"400- Bad Request"

so it looks like my replay is requesting bad information. Funny how that doesn't screw
things up when dialing.

George


>I was going to get one anyway.... Might as well do it now.

>I did notice one more difference between dialup conversations
>and ethernet conversation.

>When doing Ethernet based conversations I see dialog about getting replayzones. There
>is a seperate message for zones 1-16 and I don't see this with the phone based
>conversations.

>Thanks for the suggestions.

>George Rachor
>george@rachors.com

>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:


>>On Tue, 12 Apr 2005 11:53:19 -0500, george@agora.rdrop.com (George
>>Rachor) wrote:

>>>
>>>OK... Cleared the guide twice but still getting the error right after 'combining data'.
>>>
>>>I had to change back to dialup to get the guide re-populated...
>>>
>>>I'm tempted to buy another replay and see if it has the same problem. That would let me determine
>>>if the problem is in the unit (bad software) or upstream in my network.
>>>I was thinking about another replay anyway.
>>>
>>>George
>>>

>>It's spending more money, but probably a good idea. Problems are
>>easier to locate when you have multiple units.

>>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>>
>>>>On Sun, 10 Apr 2005 21:03:34 -0500, george@agora.rdrop.com (George
>>>>Rachor) wrote:
>>>
>>>>>Mark,
>>>>>
>>>>>
>>>>>I bypassed the linksys and got the same result (Most of the way through the transaction
>>>>>to replay then a failure message.
>>>>>
>>>>>I put a sniffer on the network line between the replay and my homenetwork.
>>>>>
>>>>>1. The replay is getting the time via ntp from production.replaytv.net
>>>>>2. On the first HTTP Get to production.replaytv.net I see the following curious
>>>>> line:
>>>>> Dissector bug, protocol HTTP: "Request URI" - "http.request.uri" invalid length: -5 (proto.c:2104)
>>>>>
>>>>>
>>>>>The following HTTP Gets have the same curious line...
>>>>>
>>>>>Any new thoughts?
>>>>>
>>>
>>>>The problem may involve merging new information with an existing
>>>>(corrupted) guide. Try clearing the Replay guide using 2-4-3-Zones
>>>>option 2 (people say you need to do this 2 times), then requesting a
>>>>new guide (manual connect).
>>>
>>>>>George Rachor
>>>>>
>>>>>
>>>>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>>>>
>>>>>>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>>>>>>Rachor) wrote:
>>>>>
>>>>>>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>>>>>>the program guide just fine
>>>>>>>via my internet connection.
>>>>>>>
>>>>>>>My connection consists of the replaytv on a home network
>>>>>>>behind a linksys router. That router is then connected to the ISP's equipment.
>>>>>>>
>>>>>>>I had to change the settings last night to start updating
>>>>>>>via phone line because something has changed and now updating
>>>>>>>the program guide via the network connection is failing. In watching
>>>>>>>the progress it looks like we get most of the way through
>>>>>>>before getting a message that the update has failed and it will
>>>>>>>try again later. The last message I see is "combining data ..."
>>>>>>>
>>>>>>>I'm trying to figure out if something has changed upstream with my
>>>>>>>ISP or if something has happened to my Linksys.
>>>>>>>
>>>>>>>Any thoughts would be appreciated.
>>>>>
>>>>>>The way the Replay handles errors can be misleading. There can be a
>>>>>>failure near the beginning, then the process seems to get all the way
>>>>>>through before you're told about it.
>>>>>
>>>>>>Is your Replay set to get a dynamic local IP from the router? If so,
>>>>>>you may need to refresh it (because of ISP making changes). Otherwise,
>>>>>>check carefully. The ISP could have changed DNS servers.
>>>>>
>>>>>>--
>>>>>>Mark Lloyd
>>>>>>has a Replay 5xxx
>>>>>>http://notstupid.laughingsquid.com
>>>>>
>>>>>>"The idea that there is an invisible being who
>>>>>>created and still runs this old universe is so
>>>>>>childish, so obviously contrived, that it is hard to
>>>>>>believe anyone with even a modicum of education can
>>>>>>still fall for that scam."
>>>
>>>>--
>>>>Mark Lloyd
>>>>has a Replay 5xxx
>>>>http://notstupid.laughingsquid.com
>>>
>>>>"The idea that there is an invisible being who
>>>>created and still runs this old universe is so
>>>>childish, so obviously contrived, that it is hard to
>>>>believe anyone with even a modicum of education can
>>>>still fall for that scam."

>>--
>>Mark Lloyd
>>has a Replay 5xxx
>>http://notstupid.laughingsquid.com

>>"The idea that there is an invisible being who
>>created and still runs this old universe is so
>>childish, so obviously contrived, that it is hard to
>>believe anyone with even a modicum of education can
>>still fall for that scam."
>--
>=========================================================
>George L. Rachor Jr. george@rachors.com
>Hillsboro, Oregon http:rachors.com
>United States of America Amateur Radio : KD7DCX
--
=========================================================
George L. Rachor Jr. george@rachors.com
Hillsboro, Oregon http:rachors.com
United States of America Amateur Radio : KD7DCX
Anonymous
April 13, 2005 5:26:50 PM

Archived from groups: alt.video.ptv.replaytv (More info?)

On Tue, 12 Apr 2005 23:42:06 -0500, george@agora.rdrop.com (George
Rachor) wrote:

>george@agora.rdrop.com (George Rachor) writes:
>OK... Looked again at Etherreal packets between my replay and production.replaytv.net and discovered that my replaytv
>is sending a series of commands for which production.replaytv.net is returning the message
>"400- Bad Request"
>
>so it looks like my replay is requesting bad information. Funny how that doesn't screw
>things up when dialing.
>
>George
>

The software could be so corrrupted that the only thing you can do is
restore a new software image. This will mean you lose all your
personal settings (such as theme channels) and recorded shows, but
will not affect activation.

>
>>I was going to get one anyway.... Might as well do it now.
>
>>I did notice one more difference between dialup conversations
>>and ethernet conversation.
>
>>When doing Ethernet based conversations I see dialog about getting replayzones. There
>>is a seperate message for zones 1-16 and I don't see this with the phone based
>>conversations.
>
>>Thanks for the suggestions.
>
>>George Rachor
>>george@rachors.com
>
>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>
>
>>>On Tue, 12 Apr 2005 11:53:19 -0500, george@agora.rdrop.com (George
>>>Rachor) wrote:
>
>>>>
>>>>OK... Cleared the guide twice but still getting the error right after 'combining data'.
>>>>
>>>>I had to change back to dialup to get the guide re-populated...
>>>>
>>>>I'm tempted to buy another replay and see if it has the same problem. That would let me determine
>>>>if the problem is in the unit (bad software) or upstream in my network.
>>>>I was thinking about another replay anyway.
>>>>
>>>>George
>>>>
>
>>>It's spending more money, but probably a good idea. Problems are
>>>easier to locate when you have multiple units.
>
>>>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>>>
>>>>>On Sun, 10 Apr 2005 21:03:34 -0500, george@agora.rdrop.com (George
>>>>>Rachor) wrote:
>>>>
>>>>>>Mark,
>>>>>>
>>>>>>
>>>>>>I bypassed the linksys and got the same result (Most of the way through the transaction
>>>>>>to replay then a failure message.
>>>>>>
>>>>>>I put a sniffer on the network line between the replay and my homenetwork.
>>>>>>
>>>>>>1. The replay is getting the time via ntp from production.replaytv.net
>>>>>>2. On the first HTTP Get to production.replaytv.net I see the following curious
>>>>>> line:
>>>>>> Dissector bug, protocol HTTP: "Request URI" - "http.request.uri" invalid length: -5 (proto.c:2104)
>>>>>>
>>>>>>
>>>>>>The following HTTP Gets have the same curious line...
>>>>>>
>>>>>>Any new thoughts?
>>>>>>
>>>>
>>>>>The problem may involve merging new information with an existing
>>>>>(corrupted) guide. Try clearing the Replay guide using 2-4-3-Zones
>>>>>option 2 (people say you need to do this 2 times), then requesting a
>>>>>new guide (manual connect).
>>>>
>>>>>>George Rachor
>>>>>>
>>>>>>
>>>>>>Mark Lloyd <mlloyd@5xxxmail.com5xxx> writes:
>>>>>>
>>>>>>>On Sat, 02 Apr 2005 10:01:03 -0600, george@agora.rdrop.com (George
>>>>>>>Rachor) wrote:
>>>>>>
>>>>>>>>I've got a replaytv model 5508 that up until 2 weeks ago was updateing
>>>>>>>>the program guide just fine
>>>>>>>>via my internet connection.
>>>>>>>>
>>>>>>>>My connection consists of the replaytv on a home network
>>>>>>>>behind a linksys router. That router is then connected to the ISP's equipment.
>>>>>>>>
>>>>>>>>I had to change the settings last night to start updating
>>>>>>>>via phone line because something has changed and now updating
>>>>>>>>the program guide via the network connection is failing. In watching
>>>>>>>>the progress it looks like we get most of the way through
>>>>>>>>before getting a message that the update has failed and it will
>>>>>>>>try again later. The last message I see is "combining data ..."
>>>>>>>>
>>>>>>>>I'm trying to figure out if something has changed upstream with my
>>>>>>>>ISP or if something has happened to my Linksys.
>>>>>>>>
>>>>>>>>Any thoughts would be appreciated.
>>>>>>
>>>>>>>The way the Replay handles errors can be misleading. There can be a
>>>>>>>failure near the beginning, then the process seems to get all the way
>>>>>>>through before you're told about it.
>>>>>>
>>>>>>>Is your Replay set to get a dynamic local IP from the router? If so,
>>>>>>>you may need to refresh it (because of ISP making changes). Otherwise,
>>>>>>>check carefully. The ISP could have changed DNS servers.
>>>>>>
>>>>>>>--
>>>>>>>Mark Lloyd
>>>>>>>has a Replay 5xxx
>>>>>>>http://notstupid.laughingsquid.com
>>>>>>
>>>>>>>"The idea that there is an invisible being who
>>>>>>>created and still runs this old universe is so
>>>>>>>childish, so obviously contrived, that it is hard to
>>>>>>>believe anyone with even a modicum of education can
>>>>>>>still fall for that scam."
>>>>
>>>>>--
>>>>>Mark Lloyd
>>>>>has a Replay 5xxx
>>>>>http://notstupid.laughingsquid.com
>>>>
>>>>>"The idea that there is an invisible being who
>>>>>created and still runs this old universe is so
>>>>>childish, so obviously contrived, that it is hard to
>>>>>believe anyone with even a modicum of education can
>>>>>still fall for that scam."
>
>>>--
>>>Mark Lloyd
>>>has a Replay 5xxx
>>>http://notstupid.laughingsquid.com
>
>>>"The idea that there is an invisible being who
>>>created and still runs this old universe is so
>>>childish, so obviously contrived, that it is hard to
>>>believe anyone with even a modicum of education can
>>>still fall for that scam."
>>--
>>=========================================================
>>George L. Rachor Jr. george@rachors.com
>>Hillsboro, Oregon http:rachors.com
>>United States of America Amateur Radio : KD7DCX

--
Mark Lloyd
has a Replay 5xxx
http://notstupid.laughingsquid.com

"The idea that there is an invisible being who
created and still runs this old universe is so
childish, so obviously contrived, that it is hard to
believe anyone with even a modicum of education can
still fall for that scam."
!