I've been able to get my Replaytv 5504 working with channel guide information from SchedulesDirect via WIRNS successfully for nearly a year now...until recently.

I had to replace my router that stopped functioning not too long ago and set it up reserving static IP addresses for my RTV and the laptop that I'm using to run WIRNS. Not too long after doing this I turned on my RTV to record a show, pressed the channel guide button and noticed that there weren't any shows listed as before. I checked the computer upon which WIRNS is currently running and went to the index page and saw that the last successful net connect was over two weeks ago (I honestly don't remember if the date of the last successful net connect and the day I installed the new router are the same). I tried doing a manual net connect via WIRNS and 2-4-3 Zones command and it will get to the point where it says "Connecting..." on the bottom of the screen and stay there until it gives up several minutes later without downloading any information from the WIRNS loaded computer.

It's odd because I'm able to control the RTV with the WIRNS remote control feature without an issue and using the 'http://(RTV address)/Device_Descr.xml yields the information about the RTV. So I know there is connectivity between the computer and the RTV.

I've tried completely uninstalling WIRNS and deleting the old program folder on the hard drive of the computer and doing a clean reinstall of WIRNS. This did the trick and my RTV was working the way it should have up until a week and a half ago where I was running into the same situation as I've described before.

I've been able to get my Replaytv 5504 working with channel guide information from SchedulesDirect via WIRNS successfully for nearly a year now...until recently.

I had to replace my router that stopped functioning not too long ago and set it up reserving static IP addresses for my RTV and the laptop that I'm using to run WIRNS. Not too long after doing this I turned on my RTV to record a show, pressed the channel guide button and noticed that there weren't any shows listed as before. I checked the computer upon which WIRNS is currently running and went to the index page and saw that the last successful net connect was over two weeks ago (I honestly don't remember if the date of the last successful net connect and the day I installed the new router are the same). I tried doing a manual net connect via WIRNS and 2-4-3 Zones command and it will get to the point where it says "Connecting..." on the bottom of the screen and stay there until it gives up several minutes later without downloading any information from the WIRNS loaded computer.

It's odd because I'm able to control the RTV with the WIRNS remote control feature without an issue and using the 'http://(RTV address)/Device_Descr.xml yields the information about the RTV. So I know there is connectivity between the computer and the RTV.

I've tried completely uninstalling WIRNS and deleting the old program folder on the hard drive of the computer and doing a clean reinstall of WIRNS. This did the trick and my RTV was working the way it should have up until a week and a half ago where I was running into the same situation as I've described before.

I'm at a loss as to what's going on and can really use some help.

Thanks in advance!

The fact that you can access the Replays from WiRNS, shows that you set up "address reservation" properly for the Replays. Did you do so for the machine running WiRNS? If it has a different IP now, that's likely to be the problem. You need to assign the WiRNS machine the same IP as before. Then restart WiRNS and do a manual net connect on all Replays._________________--
Mark Lloyd
http://notstupid.us
Has a Replay 5xxx

"There are only 10 types of people in the world, those who understand binary and those who don't"

The fact that you can access the Replays from WiRNS, shows that you set up "address reservation" properly for the Replays. Did you do so for the machine running WiRNS? If it has a different IP now, that's likely to be the problem. You need to assign the WiRNS machine the same IP as before. Then restart WiRNS and do a manual net connect on all Replays.

I made sure to reserve addresses for both the RTV and the laptop. I double checked it and it is setup just fine so there isn't an issue there. This would have made the most sense as to why it worked initially but isn't working at the moment.

rmeden wrote:

Did the "subnet" change with the new router? For example: 192.168.x?

Can the WiRNS computer access the internet? (I bet no).

My guess is that the subnet changed and the reason WiRNS and the ReplayTV can still see each other is because they are using the old network addresses.

The subnet did change from 192.168.0.1 to 192.168.1.1 when I added the router. However, the latter subnet address is the same now as it was when I had the old router. I can access the internet with the WiRNS computer without an issue.

The subnet did change from 192.168.0.1 to 192.168.1.1 when I added the router. However, the latter subnet address is the same now as it was when I had the old router. I can access the internet with the WiRNS computer without an issue.

I take it you mean you set the new router's subnet to match the old router.

If you unplug the ReplayTV and do a ping, do you get a response? Maybe something else on the network has the IP.

I take it you mean you set the new router's subnet to match the old router.

If you unplug the ReplayTV and do a ping, do you get a response? Maybe something else on the network has the IP.

I pinged the ReplayTV with the ethernet cord connected and disconnected. I was able to ping successfully to the address associated with the ReplayTV when connected and the destination host was unreachable when I disconnected the ReplayTV from the network.

I even tried changing the IP address of the laptop running WiRNS to find out if that would do anything. When I did that and tried to manually setup the ReplayTV to the network using the new IP address for the laptop, it goes through the minute and a half and tells me that it could not reach the server even though when I go to the details of the attempt it says that it was able to reach the IP addresses associated with the laptop and the gateway.

I am having the exact same problem. I do a manual guide update and software shows guide update completed. When I configure my replay to net connect via wirns software the replay setup connects to service, will connect to network to get channel guide, sets the clock, now transfer data. After all of that there is no channel guide.
How can I tell if the guide did download from scheduled direct via WIRNS? It does say guide update completed with the correct date and time. When I go to tools, current channel guide there is no info only date and times with no info.
When I go into configuration and guide data my password and username is entered correctly.

I just found out that my replay did not net connect and my channel guide on my replay is blank. The fix that I suggested earlier does bring back my channel guide in WIRNS so it is connecting to Schedules Direct but when I do a net connect it does not transfer to my replay. My network and firewall is ok as I can control my replay with the remote control in tools.
What would be causing the program guide to not transfer to my replay?

I just found out that my replay did not net connect and my channel guide on my replay is blank. The fix that I suggested earlier does bring back my channel guide in WIRNS so it is connecting to Schedules Direct but when I do a net connect it does not transfer to my replay. My network and firewall is ok as I can control my replay with the remote control in tools.
What would be causing the program guide to not transfer to my replay?

I am still not able to update my guide data in my replay 5504. I am able to connect to Schedules Direct as the guide data is showing in WIRNS.
Only the clock is current on my replay but the channel guide shows no program information. It does show the name of the channels and time but program info. is blank. I am able to select and view any of the channels.

it shoudl look like this, it did not see ur replay so it fed the guide to nowhere. try readding the replay and make sure ur provider info is shown and the serial number too. conf>replays>edit then check info_________________my poop at srfrdanu1 4k*5k

I do have the serial number from my replay unit info entered when I edit my replay. The iP address 192.168.1.101 is also entered correctly.
Is this the problem why the guide is not transfered to my replay? If this is correct why can't wirns find my replay ser?

I found out that if i go into"current channel guide" in my wirns I can select a program click on schedule and the program will record. When I go to replay guide the program is recorded but there is no name or program information just like in the channel guide.

So actually the net connect is working but for some reason not sending the guide info to the replay. Could this be a problem with my Replay unit?

I have had something similar in my replays with an added problem. I run WIRNs through a wireless Win XP using SD and have had no problems until - and this is the kicker- I broke down and went HD with comcast. I had been using the Pace code from Perc on the small boxes on two of my replays, which was before DNNA went Kaput. I got the new HD box last week and found in another thread that the pace code works.

This replay did not get the install since the old motorola IR code was fine. I got the Pace code. When I changed back to auto then tried to change the DNS. I changed one of the DNS back to the WIRNs computer. It wouldn't take both changes but I could leave the DNS2 as the DNS for Comcast. I noticed that WIRNs was not talking to the replay or updating the guide.

I tried an old WIRNs I had on a WIN7 desktop that had a different static IP, but still no luck. The wireless returns lines like:

There is a config file that shows the DNS entries that WiRNS responds to.... laho.percdata.com should be added to that list if you want to go from Perc -> WiRNS. You can edit the file, but I think it also comes from a WiRNS update.