Planet Replay

[parabola2020]

Hello:

I have been through the postings at avsforum and here and cannot find a solution for my problem. I have setup WiRNS following the instructions and everything seems to be fine. It downloads the data from zap2it without a problem and I can see it under Tools->Channel Guide.

When I change the zip code the Replay starts looking for new program guide and I see the message:

[DNS] Spoofing response of xx bytes

It then does that for a long time until the Replay times out with the following error:

ReplayTV was unable to connect to the ReplayTV service to get local phone numbers and TV Channels.

Unexpected result code (844c002)

I have a Replay 4080 and the guide data was downloading fine before I made the required changes.

Bellow a copy of the command windows when a start WiRNS:

[2004-05-07 18:18:49] WiRNS v1.1.2 build 1285 - (c) 2004 kjac
[2004-05-07 18:18:49] Thanks: ijprest, waynethedvrguy, Remmer99, gduprey, LeeTho
mpson, j.m., archdog99, FlipFlop and all the other Replay Hackers out there.
[2004-05-07 18:18:49] Initializing.
[2004-05-07 18:18:49] Cleaning up database.
[2004-05-07 18:18:49] Vacuuming database
[2004-05-07 18:18:50] Detected that I'm running from command line.
[2004-05-07 18:18:50] Loading configuration
[2004-05-07 18:18:50] Starting guide update timer.
[2004-05-07 18:18:50] Detected configuration settings. Starting Replay Emulatio
n server on: 10.0.0.5
[2004-05-07 18:18:50] Loading server plugins.
[2004-05-07 18:18:50] Loading ReplayZone genre data.
[2004-05-07 18:18:50] Plugin: ChannelGuideProvider.dll (1.0.1549.1268) loaded.
[2004-05-07 18:18:50] Refreshing RecordingGuide for: Estudio(10.0.0.6)
[2004-05-07 18:18:58] Parsed 30/30 entries.
[2004-05-07 18:18:58] Plugin: GuideServer.dll (1.0.1549.1267) loaded.
[2004-05-07 18:18:58] Plugin: HeadendProvider.dll (1.0.1549.1265) loaded.
[2004-05-07 18:18:58] Plugin: PutSyslogProvider.dll (1.0.1549.1265) loaded.
[2004-05-07 18:18:58] Plugin: ServerManagment.dll (1.0.1549.1264) loaded.
[2004-05-07 18:18:59] Plugin: XactProvider.dll (1.0.1549.1270) loaded.
[2004-05-07 18:18:59] Plugin: ZipcodeProvider.dll (1.0.1549.1272) loaded.
[2004-05-07 18:18:59] Replay Network Server Emulation started.
[2004-05-07 18:18:59] Starting configuration server on 127.0.0.1:8923
[2004-05-07 18:18:59] Loading server plugins.
[2004-05-07 18:18:59] Plugin: ServerManagment.dll (1.0.1549.1264) loaded.
[2004-05-07 18:18:59] Replay Network Server Emulation started.
[2004-05-07 18:18:59] Starting ntp proxy server.
[2004-05-07 18:18:59] Starting DNS Proxy
[DNS] micro_dns initializing
[DNS] Attempting to reply with 10.0.0.5 for production queries.
[DNS] Attempting to proxy non-production requests to 196.3.81.5.
[DNS] micro_dns listing on port 53

Any idea on what might be wrong?

Thank you!

P2020

[kjac]

Do you have multiple ip addresses on your pc?

There is currently a bug with micro_dns that if you have wirnsip set to an ip that isn't the first ip on the interface it'll cause issues.

-kjac

[parabola2020]

kjac

Thank you for your fast response.

I have two ip addresses but I don't know which one is the first one. So I tried changing the DNS numbers on the Replay to the other address (10.0.0.55), but the Replay was not taking it. I then decided to leave the Replay as it was, with DNS 10.0.0.5 and eliminate the 10.0.0.55 from my PC. I still get the same error with only one IP address on my pc.

Help!

P2020

[parabola2020]

Can someone please help me get my system configuration right?

Everything seems to be correct, but still WiRNS does not work. I had two ip addresses on my pc, but got rid of one, and rebooted it. I have also deleted the WiRNS databases and restarted the server.

1. The DD account is setup and I can see the data on http://10.0.0.5
2. The WiRNS server starts and there are no errors
3. The Replay network settings have both DNS pointing to 10.0.0.5, which is the wirnsip.
4. When I try to change the zipcode, the replay says it is getting new tv guide data and I see the "spoofing response of xx bytes" on the wirns command window, but after several minutes and several spoofing messages, the replay times out with an error.

If I change the replay settings back to what they were orginally, I have no problem communicating with the mothership.

Any help will be very much appreciated.

P2020

[kjac]

Get ethereal, and run it on your pc with the filter "port 80", and send us the attached dump file so we can debug whats going on with your connection.

-kjac

[parabola2020]

kjac:

Below the packet information from the dump. "tcp port 80" did not capture anything, so i changed it to "host 10.0.0.5"

No. Time Source Destination Protocol Info
1 0.000000 192.168.0.166 10.0.0.5 DNS Standard query A production-2.replaytv.net
2 0.000205 10.0.0.5 192.168.0.166 DNS Standard query response A 10.0.0.5
3 4.997130 192.168.0.166 10.0.0.5 DNS Standard query A production-2.replaytv.net
4 4.997330 10.0.0.5 192.168.0.166 DNS Standard query response A 10.0.0.5
5 9.997170 192.168.0.166 10.0.0.5 DNS Standard query A production-2.replaytv.net
6 9.997364 10.0.0.5 192.168.0.166 DNS
etc.. <all the packets are the same>

The strange thing is that my replay's ip is 10.0.0.6, and I can ping to it, so I don't know where 192.168.0.166 is coming from. I remembered I had seen something similar to that when I ran DVarchive, so I checked, and here's the log from that program (which I am not running at the same time as WiRNS):

05/11 15:27:01 Notice: DVArchive V3.0 starting
05/11 15:27:03 Notice: DVArchive Server Started
05/11 15:27:05 Notice: Scheduler Now Running
05/11 15:27:09 Notice: UPNP:: Received UPnP packet from previously unknown DVR @ 192.168.0.166 -- looking up DVR info
05/11 15:27:26 ERROR: Unable to fetch details for DVR 10.0.0.16:80 -- Connection timed out: connect
05/11 15:27:26 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:27:26 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:27:26 Notice: UPNP:: DVArchive has recognized new DVR ReplayTV named Living Room at 10.0.0.6:80 (Serial xxx)
05/11 15:27:26 ERROR: VELOCITY:: ResourceManager : unable to find resource 'Lib/VelocityMacros.vm' in any resource loader.
05/11 15:27:26 ERROR: VELOCITY:: ResourceManager : unable to find resource 'Lib/CustomMacros.vm' in any resource loader.
05/11 15:27:27 DVR Living Room Photo space not allocated (less than 512MB) - Photos usage is disabled for this ReplayTV
05/11 15:27:27 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:27:30 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:27:32 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:27:34 Notice: Timestamp offset for Living Room set to 5 seconds.
05/11 15:27:34 DVR Living Room space usage update: Total Capacity 74.04GB, Remaining 59.49GB
05/11 15:27:48 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:27:50 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:27:51 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:27:54 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:27:56 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:28:09 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:28:12 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:28:14 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:28:15 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect
05/11 15:28:18 Warn: REPLAY_SERVER: Rejected attempt by remote/external client 192.168.0.166 to connect

Thanks,

P2020[/img]

[kjac]

You've got some serious network wonkyness. You're going to need to track down what has that 192.168.0.166 ip and resolve that.. its causing issues.

-kjac

[parabola2020]

Anyone have any suggestions? I am clueless

[parabola2020]

I just wanted to let everyone know that i was able to solve the problem in case someone has the same issue at some point.

I had originally setup my replay in a network with 192.168.x.x addresses, but had to change it to 10.0.0.x later when i switched ISPs.

For some reason the Replay kept the old address, as well as the new one and was trying to use the old address to communicate with WiRNS. I had to change all my network addresses, including the DSL modem to 192.168.x.x and assign to the Replay the address that it wanted to use to communicate with WiRNS.

Thanks

[Nomad2004]

I'm having the exact same problem, and I have recently reconfigured my network...

Rather than change everything on the network, I think I'll just reset the RTV to factory defaults and see if that clears it.

Glad to see that someone else was able to successfully troubleshoot this error.