Hello - I have the TSU9600 and the RFX9600. All of my components are in another room from my tv. I use the remote and RFX to operate them. However, I frequently have an annoying problem - at times the internet icon on the top right corner of the remote screen will have an X through it and the remote will not function. What is causing this? Obviously the remote disconnects from my wireless internet - but why? I am using Verizon FIOS for internet with an ActionTech wireless router/modem model #MI424WR. I came home from work tonight and my wife was pi$$ed because she couldn't turn the channel all night because of the X. I came home and it connected and worked but then Xed out on me after awhile. In my pronto settings I have the remote using DHCP.

Thanks for any help!

Sounds like your range is not as good as it could be. Do you have a WAP in the room? How far are you from the router?

This may also have an affect (at least it did at one time with me on a Linksys router). If there are multiple DHCP devices on the network (including PCs), they could be competing for the same IP address.

The router is in the next room with the components - about 20 to 30 feet away so I do not think distance is the issue. I do have 2 PCs and the RFX9600 working off of the router via DHCP - the two PCs are wireless and the RFX9600 is hard wired. I also have a Denon receiver hooked up to it via hardwire that is DHCP - my Fireball is the only device that I fixed the internet address on and that is hooked up via hardwire.

So it may be a conflict with IP address - sounds like I should fix the remote at a high number. If that doesn't fix it then the router may be crap - wouldn't suprise me as I have read various forums where people have had issues with the ActionTech router that verizon uses.

Setup the RFX9600 with fixed IP. There's no reason not to plus it is IMO, a bit more reliable this way. There's no 24 hour DHCP lease to manage.

When you do this, there's nothing special you will have to do in the editor to change your config to access the extender.

I'd leave the remote as-is and change the 9600 first. Don't resort to fixed IP on the remote unless you absolutely have to. A case where you would not want to do this is if you have 2 TSU9600's that use the same config. You have to maintain two configs when NOT using DHCP.

A general comment. As usual my buddy Lyndel is correct. I run three 9600's all with the same Config so I do use DHCP for the 9600's. Every other TCPIP communicating device except for the laptops which have both, use static IP adresses. I have about 40 devices that communicate over IP (Mostly TCPIP but some UDP) on the House LAN. Technically there should be no issue between a fixed IP and DHCP, but unfortunately some DHCP implementations are not quite what they should be.

I would be interested in hearing about the various kinds of problems that users are seeing with regard to the Pronto and TCPIP. Just a description of the problem, not technical if not so inclined. Perhaps someone who knows how can start a sticky thread

jowens36,

The DHCP server in your modem/router has a reputation ... it can be a lot of trouble. It seems to work OK for simple networks, but the Pronto requires more service than computers. Make sure that you are using the latest firmware.

If you don't want to update the firmware, disconnect your network, turn off the moden's wireless and connect one output port to the WAN input port of a decent router and use the new router for your network. I usually have good results with the Linksys WRT54G. Some of the earlier routers, particularly the wired models, can cause similar problems to the ActionTech.

It's a little early to claim complete victory, but the latest ActionTech firware seems to have cured the issue.

I had no luck with the new firm ware on the verizon website. So I took an old NetGear WGR614 wireless router that I had in the house and hooked it up to a free LAN port on the Actiontech. I disabled wireless on the Actiontech and got it working on the NetGear. I rehooked up all of the wireless computers and they are working on the internet. I setup up the remote to work DHCP. I turned on the remote and it worked for awhile with no problems. After awhile the red X comes up on it for the internet icon. If I play around with the remote/turn it off and on it will work again after awhile. I tried setting the remote to static IP of 192.168.1.54 Subnetmask of 255.255.255.0 and Default Gateway of 192.168.1.1 - when I did this just the red X pops up on the remote and I never get a connection. I am a rookie at messing with these settings - am I do anything wrong or is the Actiontech router just a piece of garbage?

Thanks!

Does it work reliably with encryption turned off?

jowens36,

It is difficult to troubleshoot this issue. I had one installation with two TSU9600's, one worked well and the other had problems similar toyours. Ultimately we exchanged the problem unit.

If you are using MAC address filtering on your wireless link, make sure that the TSU9600 is included in the list. In one installation we discovered that a TSU9600 will sometimes work and sometimes will not work on an AirtPort Extreme when the 9600 is left off the MAC address list. We wasted a lot of time on that installation because we assumed that the 9600 was on the MAC address list because the unit sometimes worked.

Hooking up your Netgear as you have is asking for trouble if you are not very careful. I recommend hooking the NetGear's WAN port to a network port on the ActionTec and moving all of the previous connections from the ActionTec to the Netgear's LAN ports. (and, as you have done, turn off the ActionTec's wireless.)