Poopli Replay Request Forum

Poopli Replay Request Forum : Powered by vBulletin version 2.3.4

Poopli Replay Request Forum > Main Category > Poopli Help > IVS IP issues?

Last Thread Next Thread

Author

Thread

mnspyder
Somebody

Registered: Mar 2004
Location:
Posts: 19

IVS IP issues?

For the last couple weeks I have noticed that when I do the IVS test about half of the time I get the following error:

Asked ReplayTV server about unit at ISN 00004-54832-34224.
Found on Replay server.

The IP for your ReplayTV is 66.41.111.230
The Port for your ReplayTV is 0
Unable to contact ReplayTV unit.
500 Can't connect to 66.41.111.230:0 (connect: timeout)
Check your port forwarding settings.

If I force a net connect, and redo the test, then it is successful and tells me my settings are correct.

It seems to happen sporadically, but then again, I usually test just before I send or request a show. After getting show requests declined and being told my settings aren't right, I've gotten to the point where I do an IVS test 5-6 times a day when I am sending or receiving a show. Sometimes it is successful, sometimes I get the above result and then force another net connect.

This problem seemed to just start recently since everything worked the first month or so of using poopli and IVS. Any suggestions?

I have a cable modem, my IP address and router settings have not changed since I first set up IVS. The above IP address is not assigned to me, but is a comcast address.

Thanks.

Report this post to a moderator | IP: Logged

05-15-2004 08:48 PM

Click here to Send mnspyder a Private Message

Conspiracy
Member Uber-Supreme

Registered: Feb 2004
Location: Folsom, CA
Posts: 376

Are you sure your WAN IP address hasn't changed? Because that's what it sounds like.

__________________
Status: Spritely
Hundreds of hours of 5k viewing Here

Report this post to a moderator | IP: Logged

05-16-2004 11:45 PM

Click here to Send Conspiracy a Private Message

mnspyder
Somebody

Registered: Mar 2004
Location:
Posts: 19

Yes. According to the cable modem and IP Chicken, the public address is the same as it has been for several months. My external address is on the 66.41.15.x range, so same provider (comcast), but still never has been the 66.41.111.230 address the IVS tester shows.

Speaking of the incorrect address, I have successfully sent two shows this weekend, but the tester repeatedly shows the invalid address and instead replies with the address from my first post (66.41.111.230). I have forced a net connect at least eight times today and re-run the test to get it to show the correct address and success message, but when I come back and run the test an hour later, I get the above error yet again.

Could it be an error with the IVS test app instead of with IVS or my settings?

Report this post to a moderator | IP: Logged

05-17-2004 02:52 AM

hover
the floating poopli

Registered: Feb 2004
Location: San Antonio, TX
Posts: 1079

Have you looked into [this] thread? It's possible that someone else might have the same ISN# as you and whenever their unit checks in it registers their ip and not yours. Just a possibility.

__________________
[My Shows]

5060 w/ 250gb hd
5040 w/ 250gb hd
5040 w/ 40gb hd ($30 refurb)
5040 w/ 40gb hd ($30 refurb)

6mb/512kb (as of 04/30/04)

Report this post to a moderator | IP: Logged

05-17-2004 05:06 AM

Click here to Send hover a Private Message

j.m.
Senior Member

Registered: Feb 2004
Location:
Posts: 448

quote:
Originally posted by mnspyder
Yes. According to the cable modem and IP Chicken, the public address is the same as it has been for several months. My external address is on the 66.41.15.x range, so same provider (comcast), but still never has been the 66.41.111.230 address the IVS tester shows.

Speaking of the incorrect address, I have successfully sent two shows this weekend, but the tester repeatedly shows the invalid address and instead replies with the address from my first post (66.41.111.230). I have forced a net connect at least eight times today and re-run the test to get it to show the correct address and success message, but when I come back and run the test an hour later, I get the above error yet again.

Could it be an error with the IVS test app instead of with IVS or my settings?

No. The IVS tester just reports the info that is listed in the RDDNS database. Currently, it is showing the 66.41.111.230 address. I believe hover is right, and you are another victim of the duplicate ISN problem. I will monitor the RDDNS DB to see if I can catch it when your IP is in control.

In the duplicate ISN thread, I theorized that the problem very likely affects *at least* those ISNs in the range from
00004-54832-33871 to
00004-54832-34504
since those are (were?) the only two known confirmed instances of this problem. Your ISN (00004-54832-34224) does fall within this range, so it seems plausible that you also have a duplicate ISN/MAC address and that my theory is correct.

If we can confirm you indeed have a duplicate ISN/MAC, sfhub and I can likely fix the problem for you. Again, I will monitor your ISN and see if that reveals anything.

__________________
j.m.'s ReplayTV Tools
Home of WinDVA, the Win32 DVArchive launcher
You shan't kick an O'Brien.
PM box perpetually full. Please email.

Report this post to a moderator | IP: Logged

05-17-2004 05:43 AM

Click here to Send j.m. a Private Message

j.m.
Senior Member

Registered: Feb 2004
Location:
Posts: 448

Well, looks like we probably have another confirmed duplicate ISN case.

code:
rddns lookup 00004-54832-34224
<UnitTicket isn="00004-54832-34224" ip="66.41.15.144" port="32123" lastupdatedda
te="2004-05-17 06:23:07" />

rddns lookup 00004-54832-34224
<UnitTicket isn="00004-54832-34224" ip="66.41.111.230" port="0" lastupdateddate=
"2004-05-17 06:24:42" />

As it is mnspyder, your ReplayTV will control the ISN for only about 90 seconds a day. As a stopgap measure, you should reboot your ReplayTV at around 23 minutes past the hour in order to maximize the time that your ReplayTV controls the ISN. This will work for a while (probably until one of the units is rebooted), but it is not a permanent solution.

This new case tends to make me think the worst case prediction I made is true, and there is a huge block of duplicate ISNs. Also, I think this new evidence indicates the problem is worse than some thought. The fact that the port number is "0" most likely indicates that IVS has NOT been set up on that other unit. This means two things: 1) it will be difficult to find out who that unit belongs to in order to contact him and 2) IVS-capable ReplayTVs update RDDNS even when they aren't configured for IVS (presumably as long as they are contacted via broadband).

The good news is that sfhub and I should be able to fix this problem for those affected. Please PM sfhub for details. The bad news is there are probably LOTS of others who have or will have this problem and don't know it. Again, if your ISN falls in the range from
00004-54832-33871 to
00004-54832-34504
I would keep an eye out for problems, as I believe all of these may potentially be affected by the duplicate ISN problem. If so, it is likely that this range also extends an uknown number of ISNs farther in both directions.

__________________
j.m.'s ReplayTV Tools
Home of WinDVA, the Win32 DVArchive launcher
You shan't kick an O'Brien.
PM box perpetually full. Please email.

Report this post to a moderator | IP: Logged

05-17-2004 07:44 AM

mnspyder
Somebody

Registered: Mar 2004
Location:
Posts: 19

Thanks for the suggestion. I rebooted at 8:23 (central) this morning and my info seems to have held for the last 15 minutes. I sent sfhub a pm a few minutes ago.

Report this post to a moderator | IP: Logged

05-17-2004 02:42 PM

j.m.
Senior Member

Registered: Feb 2004
Location:
Posts: 448

quote:
Originally posted by mnspyder
Thanks for the suggestion. I rebooted at 8:23 (central) this morning and my info seems to have held for the last 15 minutes. I sent sfhub a pm a few minutes ago.

Wow, good timing on the reboot. Your unit now updates *1 second* after the other unit does. That is cutting it really close (I thought your reboot would take a few seconds longer than it did), but your unit is holding it for now. Hopefully, it will stay that way until we can get you fixed up.

__________________
j.m.'s ReplayTV Tools
Home of WinDVA, the Win32 DVArchive launcher
You shan't kick an O'Brien.
PM box perpetually full. Please email.

Report this post to a moderator | IP: Logged

05-17-2004 07:35 PM

All times are GMT. The time now is 07:33 PM.

Last Thread Next Thread

Show Printable Version |

Email this Page |

Subscribe to this Thread

Forum Jump:

Rate This Thread:

Forum Rules:

You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is ON

< Contact Us - Poopli Replay Request >