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

Hi folks.

I used to have my rtv's network connection running well. I was running
a Lucent SDSL interface. Though the DHCP server was running (for guests
with laptops), the rtv never seemed to be able to talk to it. I
configured the rtv with a static IP and all was fine. I didn't even
need to add a MAC-to-IP static IP for the replay

So, I changed ISPs. Now I have a Westell Versalink on Verizon, and the
rtv won't network won't all. (PC works fine.)

First, I tried DHCP, which didn't work just like before. Whenever it
tries to get the IP from DHCP, it fails after a timeout. Usually in the
"More Info" one of three doesn't respond. Don't know why.

So, I tried doing a static IP as before. That doesn't work either.
Same as above.

I read the networking thread, and try disabled my DHCP server. Doesn't
work either.

And, my router's DHCP server doesn't allow you to associate an IP with a
MAC. Well, it sorta does, but only if it detects the device and guesses
it's name - which it doesn't for the rtv.

The interesting thing is in my router's logs:
DNS: Unknown host: 'production.replaytv.net.replaytv.net'
DNS: Unknown host: 'rddns-production.replaytv.net.replaytv.net'
DNS: Unknown host: 'rddns-production-backup.replaytv.net.replaytv.net'
DNS: Unknown host: 'rddns-production-backup.replaytv.net'

And I can't run my PC as a rtv server, since it's not on all the time -
the rtv is.

Ideas??

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

Do you have a Versalink 327W with wireless? I just got that too and sort of
having the same problems. The wireless can see the other systems connected
via CAT5 ports, but not other wireless connected systems. My old Netgear
router works fine before switching over to the Versalink.

One solution, I was thinking of, if I can't get an answer from Verizon or
Westell. Is buy the older Westell 2100 modem, from eBay, and hook up my
Netgear router to it. I know it works because my office, near my house is
currently running that setup.

The other solution you could try is to create a RIP from the RPTV straight
out to the internet. I don't know how vulnerable the RPTV, but I have not
heard of them being hacked over the internet.

Good Luck! and keep us posted.

JW

"SJT" <tringali@yahoo.com> wrote in message
newsk2Bd.6047$PY6.6022@trndny02...
> Hi folks.
>
> I used to have my rtv's network connection running well. I was running
> a Lucent SDSL interface. Though the DHCP server was running (for guests
> with laptops), the rtv never seemed to be able to talk to it. I
> configured the rtv with a static IP and all was fine. I didn't even
> need to add a MAC-to-IP static IP for the replay
>
> So, I changed ISPs. Now I have a Westell Versalink on Verizon, and the
> rtv won't network won't all. (PC works fine.)
>
> First, I tried DHCP, which didn't work just like before. Whenever it
> tries to get the IP from DHCP, it fails after a timeout. Usually in the
> "More Info" one of three doesn't respond. Don't know why.
>
> So, I tried doing a static IP as before. That doesn't work either.
> Same as above.
>
> I read the networking thread, and try disabled my DHCP server. Doesn't
> work either.
>
> And, my router's DHCP server doesn't allow you to associate an IP with a
> MAC. Well, it sorta does, but only if it detects the device and guesses
> it's name - which it doesn't for the rtv.
>
> The interesting thing is in my router's logs:
> DNS: Unknown host: 'production.replaytv.net.replaytv.net'
> DNS: Unknown host: 'rddns-production.replaytv.net.replaytv.net'
> DNS: Unknown host: 'rddns-production-backup.replaytv.net.replaytv.net'
> DNS: Unknown host: 'rddns-production-backup.replaytv.net'
>
> And I can't run my PC as a rtv server, since it's not on all the time -
> the rtv is.
>
> Ideas??

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

Joseph Wind wrote:

> Do you have a Versalink 327W with wireless?

Yes, I do. I have the wireless turned off, though.

I ran a test last night, while it was trying to connect via manual
setup, I ran a ping on the IP I assigned to the rtv. Turns out that
there a good deal of packet loss, about 75%.

So, I'm going to try a new network cable. I had already tried it awhile
back and it failed, but I read some posts here about how to boot and
connect everything in order, so I need to try that again.

The old Lucent was a 10mbit hub, and the Westell is a 100mbit switch, so
maybe it's more sensitive to bad cables now.

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

"ST" <tringali@yahoo.com> wrote in message
news:6zeBd.17002$2X6.8222@trnddc07...
> So, I'm going to try a new network cable. I had already tried it awhile
> back and it failed, but I read some posts here about how to boot and
> connect everything in order, so I need to try that again.
>
> The old Lucent was a 10mbit hub, and the Westell is a 100mbit switch, so
> maybe it's more sensitive to bad cables now.

10M-bit is what some people call barb wire technology. It will run almost
on anything including barb wire. 100Mbit and 1Gbit are more sensitive to
line quality. It might just be your cable and your setup. How far is it
from your unit to the modem? You could install a 10Mbit hub between the
Replay and the Westell, to see if it is the cable.

Good Luck!

JW

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

The cable is pretty long, about 25' into the basement, and cable is
probably even longer than that. I'll get a new cable and see if the
pings work any better.

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

On Fri, 31 Dec 2004 01:55:47 GMT, SJT <tringali@yahoo.com> wrote:

>Hi folks.
>
>I used to have my rtv's network connection running well. I was running
>a Lucent SDSL interface. Though the DHCP server was running (for guests
>with laptops), the rtv never seemed to be able to talk to it. I
>configured the rtv with a static IP and all was fine. I didn't even
>need to add a MAC-to-IP static IP for the replay
>
>So, I changed ISPs. Now I have a Westell Versalink on Verizon, and the
>rtv won't network won't all. (PC works fine.)
>
>First, I tried DHCP, which didn't work just like before. Whenever it
>tries to get the IP from DHCP, it fails after a timeout. Usually in the
>"More Info" one of three doesn't respond. Don't know why.
>
>So, I tried doing a static IP as before. That doesn't work either.
>Same as above.
>
>I read the networking thread, and try disabled my DHCP server. Doesn't
>work either.
>
>And, my router's DHCP server doesn't allow you to associate an IP with a
>MAC. Well, it sorta does, but only if it detects the device and guesses
>it's name - which it doesn't for the rtv.
>

The Replay naming bug was fixd once. I guess they broke it later.

>The interesting thing is in my router's logs:
> DNS: Unknown host: 'production.replaytv.net.replaytv.net'
> DNS: Unknown host: 'rddns-production.replaytv.net.replaytv.net'
> DNS: Unknown host: 'rddns-production-backup.replaytv.net.replaytv.net'
> DNS: Unknown host: 'rddns-production-backup.replaytv.net'
>

When you changed ISPs, you changed DNS server addresses (there's
usually 2 of them). All your networked devices (both computer and
Replays) need to have the correct values. You may need to update some
settings. If you have an internet connection at any computer, you can
get that information from the router. Also, check the ISPs website or
contact them.

>And I can't run my PC as a rtv server, since it's not on all the time -
>the rtv is.
>
>Ideas??

My router (Linksys) doesn't support permanently assigned IP addresses
(often called "static DHCP" ). My solution was to disable its DHCP
server and use the program from
http://ruttkamp.gmxhome.de/dhcpsrv/dhcpsrv.htm. You run this program
on any computer on your network and it lets you assign specific IP
addresses to each networked device. You don't have to have it running
all the time, just when you're rebooting a device on the network.

Since I installed that (a few months ago), I have not had a problem
with a Replay (I have 3 5xxx units) communicating on the network.

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

"It is a curious thing that every creed promises a
paradise which will be absolutely uninhabitable for
anyone of civilized taste." -- Evelyn Waugh

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

On Fri, 31 Dec 2004 17:13:21 GMT, "Joseph Wind" <jpg@gif.com> wrote:

>"ST" <tringali@yahoo.com> wrote in message
>news:6zeBd.17002$2X6.8222@trnddc07...
>> So, I'm going to try a new network cable. I had already tried it awhile
>> back and it failed, but I read some posts here about how to boot and
>> connect everything in order, so I need to try that again.
>>
>> The old Lucent was a 10mbit hub, and the Westell is a 100mbit switch, so
>> maybe it's more sensitive to bad cables now.
>
>10M-bit is what some people call barb wire technology. It will run almost
>on anything including barb wire. 100Mbit and 1Gbit are more sensitive to
>line quality. It might just be your cable and your setup. How far is it
>from your unit to the modem? You could install a 10Mbit hub between the
>Replay and the Westell, to see if it is the cable.
>
>Good Luck!
>
>JW
>
>
>

My first network was 10Mbit. It worked fine with one of the cables
wired incorrectly (pins 3&6 were connected to the same pins on each
end, but were not in the same pair). 100Mbit refused to work on this
cable. It needed the cable to be fixed, to put 3&6 in the same pair.

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

"It is a curious thing that every creed promises a
paradise which will be absolutely uninhabitable for
anyone of civilized taste." -- Evelyn Waugh

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

SJT wrote:
> Hi folks.
>
>I didn't even
> need to add a MAC-to-IP static IP for the replay

Yes, YOU DO. Replays have a network bug that allows the OS and hdw to
have different IP addresses. The router should be set to DHCP AND set up
reserve ip addresses for the Replay. If there is no DHCP server the
Replay will still look for one (even if set for static) and delay
booting for several minutes.

make the changes to the router, set the Replay to DHCP in setup. Save
the config. Turn off the Replay, pull the plug for 5 minutes and then
repower. After the replay boots up, go into network setup and change it
from DHCP (it should have downloaded the new info from the router) to
static.

Everything should work fine and continue to do so.

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

On Fri, 31 Dec 2004 15:37:25 -0500, Tony D <nospam@nospam.com> wrote:

>SJT wrote:
>> Hi folks.
>>
>>I didn't even
>> need to add a MAC-to-IP static IP for the replay
>
>Yes, YOU DO. Replays have a network bug that allows the OS and hdw to
>have different IP addresses. The router should be set to DHCP AND set up
>reserve ip addresses for the Replay. If there is no DHCP server the
>Replay will still look for one (even if set for static) and delay
>booting for several minutes.
>
>make the changes to the router, set the Replay to DHCP in setup. Save
>the config. Turn off the Replay, pull the plug for 5 minutes and then
>repower. After the replay boots up, go into network setup and change it
>from DHCP (it should have downloaded the new info from the router) to
>static.
>
>Everything should work fine and continue to do so.

The program (http://ruttkamp.gmxhome.de/dhcpsrv/dhcpsrv.htm ) I often
post a link to is something you can use if your router doesn't allow
this. Put it on any computer on your network and turn off the one in
the router. I've been using it for a few months now, and have had no
Replays failing to use the network.

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

"It is a curious thing that every creed promises a
paradise which will be absolutely uninhabitable for
anyone of civilized taste." -- Evelyn Waugh

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

ST wrote:
> The cable is pretty long, about 25' into the basement, and cable is
> probably even longer than that. I'll get a new cable and see if the
> pings work any better.

Just so you know... I run fifty feet between this laptop and the router
when in wired mode (No wire when in wireless... but I don't often use
that mode) and get zero packet loss between it and the replay

Replay is on, I think a six foot Cat-5 (it's next to the router only
thing physically closer to the router is the modem, The router sits atop
it sometimes (in front of it just now) and the monitor for my other two
computers (router bolted to it)

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

"Mark Lloyd" <mlloyd@5xxxmail.com5xxx> wrote in message
news:nmhbt0pfonfimder57i8khj9mnko9i6pss@4ax.com...
> On Fri, 31 Dec 2004 15:37:25 -0500, Tony D <nospam@nospam.com> wrote:
>
> >SJT wrote:
> >> Hi folks.
> >>
> >>I didn't even
> >> need to add a MAC-to-IP static IP for the replay
> >
> >Yes, YOU DO. Replays have a network bug that allows the OS and hdw to
> >have different IP addresses. The router should be set to DHCP AND set up
> >reserve ip addresses for the Replay. If there is no DHCP server the
> >Replay will still look for one (even if set for static) and delay
> >booting for several minutes.
> >
> >make the changes to the router, set the Replay to DHCP in setup. Save
> >the config. Turn off the Replay, pull the plug for 5 minutes and then
> >repower. After the replay boots up, go into network setup and change it
> >from DHCP (it should have downloaded the new info from the router) to
> >static.
> >
> >Everything should work fine and continue to do so.
>
> The program (http://ruttkamp.gmxhome.de/dhcpsrv/dhcpsrv.htm ) I often
> post a link to is something you can use if your router doesn't allow
> this. Put it on any computer on your network and turn off the one in
> the router. I've been using it for a few months now, and have had no
> Replays failing to use the network.

Why not just assign a static IP to each system? If you have 5 or less
systems that require IPs it's easier to just give them each Static IP. That
way you know which IP is assigned to certain system. DHCP is was designed
to be used on larger network, and was subsequently used for Novice users
because it's practically "plug and play". DHCP is not fool proof, because
the IP do expire, if you set them for a year. If for some reason the router
(DHCP server) is rebooted, the table is cleared and IPs that were assigned,
may become invalid, thus causing errors.

Most routers don't use the entire range of IP subnet. i.e. 192.168.1.1 to
192.168.1.255 They usually assign a smaller range like 192.168.1.100 to
192.168.1.128. Everything else can be used for static IP, except for
192.168.1.1 which is usually the router's default IP and gateway IP.

How hard is it to write the assigned IP address on a piece of masking tape
on the side or back of the unit?

Happy New Year everyone!!!

JW

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

"Mark Lloyd" <mlloyd@5xxxmail.com5xxx> wrote in message
news:tq4bt09f8l9r4v38q5sand83l53n2e340i@4ax.com...
> On Fri, 31 Dec 2004 17:13:21 GMT, "Joseph Wind" <jpg@gif.com> wrote:
>
> My first network was 10Mbit. It worked fine with one of the cables
> wired incorrectly (pins 3&6 were connected to the same pins on each
> end, but were not in the same pair). 100Mbit refused to work on this
> cable. It needed the cable to be fixed, to put 3&6 in the same pair.
>

10Mbit only needs two wires to work. The reason your 3&6 did not work was
because they were not on the same twisted pair. The same color should be on
the same pin. 1/2, 3/6, 4/5, and 7/8 are each a twisted pair needed for
Ethernet. 10Mbit has a range of 1000ft, while 100Mbit has a range of half
of that.

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

Success!

The old wire must have a had a kink or something that didn't like
running at 100mbit. I created a new wire from scratch, tested it with a
wire tester to make sure I didn't mess up the wiring, and it worked great.

Even DHCP worked... I was shocked to see it worked! I could download
the channel guide, and DVArchive can see it now. Which is all I really
need. This brings me back to what I had before I switched ISPs.

So I rebooted it, and I indeed watched get an address via DHCP, and then
another:

IP Address MAC Address Name Status
192.168.1.45 00:0a:97:02:0c:ec rtv family room Active
192.168.1.46 00:0a:97:02:0c:ec * Inactive
192.168.1.47 00:01:02:c0:9d:80 miles Active

The funny thing is that I had a ping to .46 running the entire time
during boot. In the middle of the boot, I swear, it switched to .45. I
thought I was seeing things, so started another ping to .46. Sure
enough, a ping to .46 results in it pinging .45! Maybe an ICMP redirect
or something weird like that. Never seen one before.

So, what does forcing a static IP (DHCP) do? Does it make IVS work?
Everything else seems fine now.

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

> Why not just assign a static IP to each system? If you have 5 or less
> systems that require IPs it's easier to just give them each Static IP. That
> way you know which IP is assigned to certain system. DHCP is was designed
> to be used on larger network, and was subsequently used for Novice users
> because it's practically "plug and play". DHCP is not fool proof, because
> the IP do expire, if you set them for a year. If for some reason the router
> (DHCP server) is rebooted, the table is cleared and IPs that were assigned,
> may become invalid, thus causing errors.
>
> Most routers don't use the entire range of IP subnet. i.e. 192.168.1.1 to
> 192.168.1.255 They usually assign a smaller range like 192.168.1.100 to
> 192.168.1.128. Everything else can be used for static IP, except for
> 192.168.1.1 which is usually the router's default IP and gateway IP.
>
> How hard is it to write the assigned IP address on a piece of masking tape
> on the side or back of the unit?

And AGAIN, static alone will not fix the Replay network bug because on
bootup either the hdw or OS will issue a DHCP request ANYWAY. Using
reserved ips in the router is the only way to insure both parts of the
Replay always get the same address.

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

"Tony D" <nospam@nospam.com> wrote in message
newsLudneOcRak9kkvcRVn-1Q@comcast.com...
> > Why not just assign a static IP to each system? If you have 5 or less
> > systems that require IPs it's easier to just give them each Static IP.
That
> > way you know which IP is assigned to certain system. DHCP is was
designed
> > to be used on larger network, and was subsequently used for Novice users
> > because it's practically "plug and play". DHCP is not fool proof,
because
> > the IP do expire, if you set them for a year. If for some reason the
router
> > (DHCP server) is rebooted, the table is cleared and IPs that were
assigned,
> > may become invalid, thus causing errors.
> >
> > Most routers don't use the entire range of IP subnet. i.e. 192.168.1.1
to
> > 192.168.1.255 They usually assign a smaller range like 192.168.1.100 to
> > 192.168.1.128. Everything else can be used for static IP, except for
> > 192.168.1.1 which is usually the router's default IP and gateway IP.
> >
> > How hard is it to write the assigned IP address on a piece of masking
tape
> > on the side or back of the unit?
>
> And AGAIN, static alone will not fix the Replay network bug because on
> bootup either the hdw or OS will issue a DHCP request ANYWAY. Using
> reserved ips in the router is the only way to insure both parts of the
> Replay always get the same address.

Then why does RPTV allow you to assign a static IP? Network Bug Error? OK.
But in that scenario, your still better off assigning everything else a
static IP and use one IP for DHCP, which may still cause errors. If another
system come online and is on DCHP, which most are on by default anyways.
Now you have an IP conflict.

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

On Sat, 01 Jan 2005 01:54:22 GMT, "Joseph Wind" <jpg@gif.com> wrote:

>"Mark Lloyd" <mlloyd@5xxxmail.com5xxx> wrote in message
>news:tq4bt09f8l9r4v38q5sand83l53n2e340i@4ax.com...
>> On Fri, 31 Dec 2004 17:13:21 GMT, "Joseph Wind" <jpg@gif.com> wrote:
>>
>> My first network was 10Mbit. It worked fine with one of the cables
>> wired incorrectly (pins 3&6 were connected to the same pins on each
>> end, but were not in the same pair). 100Mbit refused to work on this
>> cable. It needed the cable to be fixed, to put 3&6 in the same pair.
>>
>
>10Mbit only needs two wires to work.

That would be 2 pairs.

> The reason your 3&6 did not work was
>because they were not on the same twisted pair.

True. Of course they DID work with 10Mbit.

> The same color should be on
>the same pin. 1/2, 3/6, 4/5, and 7/8 are each a twisted pair needed for
>Ethernet.

Only the first 2 pairs are needed for most forms of ethernet. I heard
about one that needed all 4 pairs once, but it's not in common use.

> 10Mbit has a range of 1000ft, while 100Mbit has a range of half
>of that.
>

How are you determining the range, and what effect do switches have on
that?

The information I have (which is for 10Mbit) says a cable can be 100
meters (about 325 feet), and up to 5 segments can be used. That makes
the range 1625 feet (maximum between any 2 machines).

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

"It is a curious thing that every creed promises a
paradise which will be absolutely uninhabitable for
anyone of civilized taste." -- Evelyn Waugh

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

On Fri, 31 Dec 2004 21:49:03 -0500, Tony D <nospam@nospam.com> wrote:

>> Why not just assign a static IP to each system? If you have 5 or less
>> systems that require IPs it's easier to just give them each Static IP. That
>> way you know which IP is assigned to certain system. DHCP is was designed
>> to be used on larger network, and was subsequently used for Novice users
>> because it's practically "plug and play". DHCP is not fool proof, because
>> the IP do expire, if you set them for a year. If for some reason the router
>> (DHCP server) is rebooted, the table is cleared and IPs that were assigned,
>> may become invalid, thus causing errors.
>>
>> Most routers don't use the entire range of IP subnet. i.e. 192.168.1.1 to
>> 192.168.1.255 They usually assign a smaller range like 192.168.1.100 to
>> 192.168.1.128. Everything else can be used for static IP, except for
>> 192.168.1.1 which is usually the router's default IP and gateway IP.
>>
>> How hard is it to write the assigned IP address on a piece of masking tape
>> on the side or back of the unit?
>
>And AGAIN, static alone will not fix the Replay network bug because on
>bootup either the hdw or OS will issue a DHCP request ANYWAY. Using
>reserved ips in the router

Small correction: reserved IPs in the DHCP server. A lot of routers
don't have that ability. In that case, you can use software on a
computer instead.

> is the only way