Problem connecting iPAQ 22xx

[MTNGOAT]

Greetings,

I’m having difficulty connecting an iPAQ Pocket PC (22xx) to my wireless network. I have a D-Link 624 router configured for WEP and SSID broadcasting disabled. A desktop PC connects just fine to this network.

The iPAQ is running Windows 2003 and using a D-Link CF card model DCF-660W. D-The default driver is certified for the 2002 OS, but D-Link has a beta driver for the 2003 OS. I’m not using the beta driver because the standard driver works and D-Link recommends using the default driver. Using this iPAQ I have successfully connected to several open networks and another WEP enabled network, so I know the driver does in fact work. I have double, triple and quadruple checked the WEP key and it is correct.

When I attempt to access my network (I’m using DHCP enabled on both the router and the clients) my router status shows the iPAQ’s attempt to connect, but an IP address is never assigned. Another weird thing, is if I disable WEP on the iPAQ it sees the MAC of the router and shows correct status for channel, signal level, etc., but as soon as I enable WEP on the iPAQ it drops all status.

Thanks in advance – this is a great forum!

[M/Q]

Welcome to the forum. One question, how are you entering the WEP key? If you are using passphrases, don't. Determine what the Hex key is for the passphrase you like and then enter in the hex number instead in both the router and iPaq. Typically that will be the problem. Curious what brand/model wireless adaptor does the PC have?

Also enable SSID broadcasting, that does nothing to protect your network and if anything increases the management overhead to where you may lose some bandwidth. When WEP is enabled, it will be virtually impossible for any one to crack it and get any information from you.

[MTNGOAT]

Thanks for the reply. I am using a hex key and the wireless card in the PC is also a D-Link. I have a second PC, a laptop, using a Linksys PCMCIA and that connects to the router just fine. I'll try turning the SSID broadcast on and see if that makes a difference.

[MTNGOAT]

I tried enabling SSID broadcast, but the result was exactly as previously stated. Instead of recognizing just the MAC address of the router/AP my iPAQ sees the SSID too. If I enable WEP on the iPAQ I lose all connection status, but if I disable WEP (on the iPAQ only) I get all connection status, but no IP assigned by DHCP and hence no connectivity.

[M/Q]

Does that apply to all encryption lengths? Have you tried 64b per chance?

And I am slow, so please bear with me, are you saying that you enter the encryption key using hex in all the nodes? It is usually the reason for the problem you have indicated. But you also mention that most of the components are of the same vendor, so it is not as relevant.

Have you tried some of the iPaq forums, as they may have more specific dealings with this issue?

[MTNGOAT]

I haven't tried 64 bit hex, only 128.

Yes, I did enter the same hex key into all nodes.

Next stop will be the iPAQ forum, but I've been reading this one for past few weeks and have found it ver informative, so I thought I'd try here first.

Thanks!

[M/Q]

Sorry, sometimes it is not in the realm or expertise. I am not afraid to try and help, and if I feel that you might have better luck elsewhere, it is kind of helping as well. So don't give up on us, this is a great forum with a lot of knowledgeable people here. I also would appreciate hearing if you figure out the problem.

[MTNGOAT]

Update: I've spoke to D-Link Tech Support and they confirmed that using the same rev. router/AP and CF Wireless card that I have, they were unable to connect using 128 bit WEP encryption. They claim the reason for this is 128 bit WEP is not a ratified/agreed upon standard, which is news to me. They claim it will work with 64 bit encryption, but couldn't get it to work after a brief try. So I guess I don't have any hope of enabling WPA-PSK.

[M/Q]

That is true as 128bit is not Wi-Fi approved. And that is why I kept asking about the hex key because any encryption is suspect as to being compatible. There is quite a flap going on right now as third party types are checking compatibility and are finding that it is not as good as expected.