T-Mobile Confirmed, h6315 Secure Wi-Fi doesn't work

[gregkeene]

I couldn't get my 6315 to connect to my home network using WEP. I have a few other laptops, a 2215/Socket Card and a 4155 that all connect just fine.

I'm using a 128-bit WEP key (I manually input it -- and yes I checked to be sure I input the correct key). The h6315 displays Connecting for a while and then goes back to Available.

If I turn WEP off (on the access point) and leave the network open, the h6315 connects fine (although it connects a bit slower than my other devices).

So, I contacted T-Mobile, and guess what. Tier-2 support at T-Mobile confirmed that both WEP and WPA don't work on the h6315. I didn't ask about 802.1x. They told me they were going to do more research and contact me by Monday with details about what can/is going to be done. But for now, an open network is the only option. Where in the world were the beta testers. Did anyone even look at this?

Unbelievable!

If they don't have a solution, mine h6315 going back.

Greg

[robcorn]

Greg, I'm using a Linksys WRT54G router (802.11b and g) with 64 bit, 10 hex digit WEP encryption. I also manually input my key into my 6315 and I can connect flawlessly to my router. Have you tried any other WEP settings other than 128 bit?

I think the Tier2 support at Tmo doesn't know what they're talking about, because half of them haven't even been to training on the 6315 yet, so believe what they tell you with a grain of salt.

PM me if you have questions on how I have my WEP set up on my router. Hope this helps.

[ts937km]

I've been beating my head against the wall also. Finally turned my home access point to WPA. I wasn't about to use WEP with my SSID showing....

I'll let you know if my HP contact comes up with something.

My bluetooth also has problems initializing sometimes. Does yours?

[mesposito2]

I couldn't get my 6315 to connect to my home network using WEP. I have a few other laptops, a 2215/Socket Card and a 4155 that all connect just fine.

...

Unbelievable!

If they don't have a solution, mine h6315 going back.

Greg

I'm using WEP just fine. Don't remember if it is 64 or 128bit. Don't return the device yet. I also don't think they know what they're talking about. T-Mobile doesn't have anything to do with the 802.11 drivers anyway.

[digitaldodd]

I am able to connect with 128-bit WEP to my Netgear MR814. The one thing that I did have to change was to turn off the access control feature where you specify the allowable MAC addresses that can connect. I couldn't get the Netgear to accept the MAC address for the ipaq, so I turned it off and then it connected fine.

[Wojo]

Having a few connection issues with mine but I can connect to my AP with 128 WEP and SSID Broadcasting off. I took some work but it now connects to my AP flawlessly and instantly. Take a look at my post in the Phone Edition Forum "iPAQ 6315 and WiFi issues".

http://www.pocketpcthoughts.com/forums/viewtopic.php?t=31670&sid=fea867126b0fd3ebd981a32f8488450b

wojo

[ts937km]

The bad thing is a lot of the solutions assume you can turn off and on your access points and reconfig them. When you are dealing in the corporate world where a lot of these phones are going to be you can't just turn off and on the access point and play with mac filtering etc.

Tmobile/HP has an issue with the units (tried 3 now) and 3 different brands of access points including commercial grade units from Cisco. Ipaq 4150 series and 5000 series along with Dell and HP laptops have no problems getting into the access points with WEP 128bit settings. So to me it's an IPAQ 6315 issue.

[gregkeene]

I've seen enough on a couple of forums I do think there's something here. Either access points, settings, or problems with some/many 6315s.

At first I thought it might be my D-Link access points (some others have mentioned D-Link when they have problems. However, I brought a Linksys into the mix and I notice the exact same problems using WEP.

My Devices
- D-Link DI-824VUP
- D-Link DI-624
- Linksys WAP55AG

All have the latest firmware.
On the DI-624, I have turned off 'turbo' mode just to be safe.

My Access Point settings are:
Channel 6
WEP 128-bit, shared key 1
Broadcast SSID

My 6315 settings are:
Authentication: Shared
Data Encryption: WEP
Network Key (manually input at the device)
Key index: 1

Symptom is still that it sees the network and when I select and click 'Connect' it displays connecting, then after a while that switches back to Available. It never does connect. All my other devices (Pocket PCs & Laptops are working just fine).

I'm going to go to a Starbucks and see how the device fares. I'm sure it'll be fine because no security. We'll see.

Anyone have any ideas or see similar problems?

Regards,

Greg

[Wojo]

The bad thing is a lot of the solutions assume you can turn off and on your access points and reconfig them. When you are dealing in the corporate world where a lot of these phones are going to be you can't just turn off and on the access point and play with mac filtering etc.

Tmobile/HP has an issue with the units (tried 3 now) and 3 different brands of access points including commercial grade units from Cisco. Ipaq 4150 series and 5000 series along with Dell and HP laptops have no problems getting into the access points with WEP 128bit settings. So to me it's an IPAQ 6315 issue.


You're right. I've been having issues all day with my 6315. The first day I didn't have a single issue after configuring the MAC addressing. Now I'm back to the original issue of fast connect and disconnect.

I'm wondering how many users have B access points and how many have G access points. I've run into a couple of situations with clients that had older B cards that would not connect to a G AP/Router. Even when the router is configured for dual mode.

Wojo

[MountDan]

I have had no problems connecting to my work D-Link B/G, home D-Link B and Starbucks WiFi. My work and home access points both use 128 WEP. I have also used pocketWinc by Cirond (www.cirond.com) to identify WiFi connections and have been able to connect to a couple NON-WEP protected access points.

[lgingell]

I've been using 64-bit WEP OK. (10 digit key) to a Netgear b/super-g
I used 128bit also, and that worked. Seemed a bit fiddly to get it going, but it did work.

..lance