It does help. I presume in the System Properties, you have the network as "pronto". For WEP128, did you supply passphrase or key? If key, then ensure you use Key#1 supplied by linksys.

I would try G-Only and no mixed and also ensure you have latest firmware on router from Linksys.

If all of these fail, then I'd consider swapping the pronto.

FYI, if you are in the states. Email me offline (address on profile) I'd be willing to call you up and walk you through this just to ensure things are what they should be (I'm in Dallas). Prior to doing so, please email me screen prints of 9600 wireless settings page and the appropriate screens from linksys router/WAP.

Lyndel

I thought I would add to this thread as I seem to be having the same issue. I just purchased a Pronto TSU9400 (running firmware v4.0.17) to replace my TSU3000 whose screen has finally lost most of it's contrast.

The wireless router is an Apple Time Capsule, which is essentially an Airport Extreme with a hard drive built-in for backups. I set the wireless security to WEP with a 128-bit key (13-character ASCII/26 character Hexadecimal). The router doesn't support 64-bit WEP.

HEX Key: 34312d28556b7461526e442f4b

My Dell laptop running XP is able to connect to the wireless very quickly using either key, so I've ruled out any problem with the network itself.

I set the wireless settings for the 9400 to use the same SSID and WEP128 encryption. The IP Settings are set to DHCP.

I've tried using both the passphrase and the HEX key options using the appropriate key. The pronto seems to see the network, but it will not obtain an IP address. The diagnostics on the 9400 show multiple error 0551 entries:

"WiFi interface has no IP address"

The network icon shows a red X and the title displays "Connecting..."

Interestingly enough, when I disable the security on the wireless router and the 9400, the pronto connects perfectly fine. But after trying many variations using WEP (including multiple different keys), it still will not connect using WEP.

If anyone has any ideas please advise.

Did Serky and EK1 ever figure out there issues? I have just bought a TSU9400 and an RFX9400 for the same reason as Serky (to control my HAI omni pro). Turns out that I probably didn't need the RFX and I wished I would have read this thread earlier. Regardless, I am having the same issues and it's pretty frustrating. I have tried every signifcant permutation of setting on the AP and Pronto to make the Pronto connect, but no joy. Depending on which variant I use, I am getting a combination of the 'no ip address' and no errors at all when I check the diag panel. Here is my data, and I hope someone can find what I am doing wrong

Equipment:
TSU9400 w/firmware 5.0.6
RFX9400 but not sure that matters here
LinkSys AP Model WAP4400N
Router is a Cortexa home control system with built in router

AP Settings I have Tried:
Security: none, WEP64 (key 5122516452) - WEP64 is my normal
Wireless Mode: B/G/N mixed, B/G Mixed, G only
SSID: BELT
SSID Broadcast is ON

Pronto Settings I have tried via PEP 2.0:
Network Options: Wireless checked
Use Control Panel: with Wireless and Serial Extenders...
SSID: BELT
Security: matched to router - none or WEP64 with same key as above - 5122516452
IP Assignment: Tried both DHCP and Fixed at 192.168.10.243 (pinged this on my network to make sure nothing was there)
Subnet: 255.255.255.0 - same as router setting
Gateway: set to my router address: 192.168.10.1 and tried it with all zeros
DNS: set to my routers DNS setting and tried with it set to all 0's

What I have found is that I basically get no errors in the diag panel unless I choose DHCP then I have the 'no ip address' error. I think that might have come from not having the Gateway IP set in that iteration.

This is pretty straight forward but doesn't work. The simplest settings of no security, fixed (known good) IP, matched SSID, G-only, correct gateway/subnet don't work.

Any thoughts???

I don't know if this helps or not, but did you enter the WEP64 security key into the Pronto using HEX or Passphrase? The key you listed is a WEP64 10 hex digit key, and some have reported this as an issue with certain access points.

[Link: remotecentral.com]

You should not need an extender. Although I have one in my system, the 9600 connects directly with your network (G mode) and through your network connects to the HAI controller. I have my TSU9600 setup and connected to my HAI Omnipro II. Connection details:

In PEP V1.1, System Properties, enable wireless on pronto control panel, select "with Wireless... in network mode", WIFI settings, SSID (that you have assigned on your wireless router, I'm using WEP128 for Encryption, select the HEX Key and enter the HEX Key from your router (if you are using WEP). Select IP setting of DHCP. This should get your 9600 connected to your network.

Integrate the module from the ProntoPhillips site for the 9600. In V1.1 this would use merge. In V2, you just open the file and then copy/paste into your own file to add. This should add a Home and HAI Controller activity. In the parameters page on the HAI controller activity, you must enter the IP address of the HAI controller. The default is 192.168.0.101 (this can be changed), port number (default is 4369) and keys you must get from the hai controller. Each one (especially the keys) are unique to your panel and assigned at the factory. You can get these from the control panel or from the PC access software. Assume you have an ethernet wire coming from your router to the HAI controller! If you use PC Access to configure your HAI controller, then you probably have all of this setup. Hope this helps. SJ

I entered as both passphrase and hexkey but I believe hexkey is the correct method and the one I have in there now.

I am having the same problem on my Pronto 9600 I am showing my correct IP MAC and SSID on my Pronto Info page but when I try to connect the HAi button I get error not connected when I hit the issue cmd I get "Not connected check AES Key or Communication link, I am using WEP64 I have tried both passphrase & the Hexkey and my IP setting of DHCP, doubled checked parameters page on the HAI controller activity all is as it should be. Does this seem to be a common problem are there any patches or fixes?

Thanks,
Bob