I'm fiddling with the network settings here and simply can't get WPA to work.
My WAP is a Linksys WRT54GL with dd-wrt.
If i run it with no security or wep64/128 then the Pronto gets an IP-address just fine, but if I go back to WPA which I would prefer to run the Pronto never gets an IP, and it doesn't give an error message either in the diagnostic window.
I've tried both AES and TKIP with the same result.

The only thing I change between the settings is the encryption mode and the passkey, the rest is identical (DHCP, channel number, SSID etc).
Any ideas on what I could try to get the Pronto to accept WPA?

Hi you may have issues with WPA, Pronto works much better with WEP.
There has been mixed results with WPA/WPA2-PSK. It seems to be very dependant on which WAP/WRT you use on how much sucsess you have.. We used to recomend a Linksys wireless router for this but unfortunally they are no longer available, sorry i can not remember the model number. I would surgest trying a TP-Link 941n if you can find one and give that a go.

Hi. I got a used 9400 And cant get connected to my wifi.

I have read through a lot och threads, until they started to repeat them selves.

I am suspecting a broken wifi on the remote, but says its MAC and tries to connect..., well that is what the remote displays anyway.


The network is a ADSL modem THOMSON ST780 with wifi and 4 port switch. To this I have a another switch, for more ethernet connections. I use DHCP, have almost 200 IP addresses to use, so no shortage there. 1 day until it releases the IP.

My SSID looks like this, TN_private_2D87F7. Use 802.11b/g, channel 3, I broadcast the SSID. Allow multicast, WAP-PSK:WPA, 10 character long password of capital letters och numbers.

Also tried open network, no password. Same SSID.


In PEP2.4.23.0 (under win7pro 64bit) I use timeout of 2 hours. Removed the Extender in Add Extenders menu (one is automatically added!) Use wireless & serial extenders and or... SSID, same as above (yes exactly the same). WPA encryption and my 10 character long password in passphrase. In Advance wifi I use default but have tried setting it to single access point and channel 3. Also tried Fixed IP but mostly DHCP.


My pronto also behaves weird of I off it (power switch). It wont come on (when I switch on) back right away, it seems to try but only succeeding after a while...
My latest try was to reload the firmware, to the same that was in there already, TSU9400Updater_V7.3.3-1.4.5. (Latest stable)(This was really scary as I know I might have hardware problems and the firmware might get stuck in the middle thus brick it but no pain no gain :) ).


The remote is just displaying: Connecting..., and a red cross over the signal strength icon.
But it did something when I tried no password, the connect text and icon disappeared for a blink of a eye but only to return.

What do you guys think? Have I missed something or is it prontos wifi not compatible or even broken?

/Regards.

Ps, I have had a battery replacement and now have excellent battery time.

What happens if you use Hex Key instead of passphrase? Sounds like you have bad wifi on the unit but won't rule out WPA issue at this time.

I use WEP128 and don't have issues with 9600 or 9800. I traded my 9400 long ago so I'm sort of flying blind here.

With reference to point 4a of the original post,

My router is configured to be used as a DHCP server from 192.168.0.2 - 192.168.0.254

So am I right in thinking that my TSU9600 and my RFX9600 should be assigned a static ip address which are after .254 ?

I personally would reduce my DHCP pool for starters as I'm sure you don't have 252 devices on your home network that need an IP address. :-P It's generally a good idea in my opinion to limit your DHCP pool leaving just enough breathing room for any guest devices which may need to get up on your home network from time to time. Any IP address range within your 192.168.0.2-192.168.0.254 is fine for your DHCP pool. Whatever you want. My DHCP pool only allows for 11 IP addresses, most of which are reserved for devices which don't offer the option to assign a static IP with a couple extra to spare for guests that stop by the house from time to time. Anything outside your DHCP pool is fair game as far as assigning a static IP. Keeping static IP's outside your DHCP pool prevents the possibility of an IP address conflict obviously.

I have never used WPA with my Pronto remotes unfortunately. Don't even use PEP v2 which is required for WPA. Still using PEP v1 exclusively. That being said, I'd highly recommend going with a dual band router that allows for running both WEP128 and WPA concurrently. The post found here details the router that I use. While your results may vary I've never encountered a single connection issue with my Pronto TSU9x00 remotes on WEP128.

And if you have a choice over using hex key vs passphrase, always choose hex key.

Thanks for the information & advice guys......

I will go through your tips to see if I can improve things with
my connectivity problem.

Was working fine,until I upgraded to fibre optic and they sent me
a new router to use.

Just needs a bit more tinkering I think :)

So just a small issue. I got an RFX9400 and its working. My TSU9400 is working. Everything is fine but once every 10-12 day I get a red X on the wireless signal icon and the pronto will not connect. I have to go to the basement and reset my router (Linksys WRT54G). Then it works again for another week or 2, etc. Not a huge deal except when it's not working and my wife can't turn anything on! Any ideas what to check for? All this started when I got the RFX9400. Every other device in the house works. I have every device in the house hard coded. No DHCP.

It sounds like you might be getting interferance from either a cordless DECT phone, or the WIFI has gone to sleep on the remote make sure it is set too 24 Hr.
Try using a different WiFi channel, if you have a DECT phone make sure it is set to a fixed channel and not hopping.

No phones in the house (just cell phones). Maybe a neighbor is zapping me? I'll check the wifi sleep setting and maybe try a higher channel on the router. Thanks for the suggestions.

Just wanted to add my experience with my TSU9600 and RFX9400. I tried every option posted in the first post of this thread, but still the connection got lost after the screen of the TSU9600 goes black. Not every time though, but after about 5 minutes of sleep. Very annoying bug, making this set-up useless.

But I found the solution (at least it worked for me!): The RFX9400 needs to be in DHCP mode. In a few other threads I read that static IP is the way to go (and maybe that is true for the TSU9600), but the RFX9400 works flawlessly in DHCP mode!!! No more "command failed" errors at last!

Hope that this helps others with similar problems.

This makes me wonder if you did not have a conflicting IP address on your network that was coming in and associating on the IP you had configured for RFX9400.

Also, just because you put the RFX9400 to a fixed IP setting, I have to also ask when you were in this configuration did you also setup PEP (V1 or V2) to specify a fixed IP address for your extender? I have used RFX9400 and RFX9600 in Fixed IP mode for years (extender configured for fixed mode) and also make sure that I specify the ip address in the extender settings of PEP as Fixed.

I use fixed IP addresses for all my TSU9600's (x3) and RFX9x00's (x5) as well, the configuration file for the remotes calling out those fixed IP addresses also. Additionally, to prevent any possibility of an IP address conflict the IP addresses used all fall outside of my DHCP pool, each of which are also reserved based on the MAC address of each remote/extender. No connection/network related issues with any of my Pronto gear to date going back to day one some 7 plus years ago now.