I am having difficulties to get a number of Nomads to work on site, but work fine in the office…. see below

PDA: Nomad 800LE
Firmware: 1.04
OS: Windows Mobile Classic 6
Radio/Wifi/WLAN Driver 2.1

In Office: One Cisco AP with single vlan using WPA-PSK (TKIP) no EAP, no Radius
Site Setup: Multi (roaming) Cisco 1200 AP, vlans, radius server. Using WPA-PSK (TKIP) no EAP.

Info: My laptop and a Symbol PDA Mobile (5.0) communicate fine on the site network.
Cisco firmware versions on and off site are the same.

Symptoms:
Using the new driver on the Trimble V1.2 appeared connected to the Network_1 SSID but was actually NOT conencted at all!

Before the WLAN V1.2 upgrade the PDA used to oscillate between available, connecting, and connected and then go back to available….for ever. This cycle was continuously repeated.

Any light on the above very much appreciated.

The post from yesterday was posted as we were transitioning to another web server, so I reposted it below, and I you will not need to register again:

How many Nomads have been tested? 2
Have any other Windows mobile 6 devices been tested? No
If you factory default the AP and the Nomad, does the problem persist? Not physically possible as the site AP are our property.
Have you tested any other Access Points? Yes
Does the Nomad connect to a common Wi-fi hotspot? Yes
How did you determine that the Nomad was not connected even though it appeared connected? Using PING utility from the PDA.
Have you tried using the SSID lock to lock on to the SSID? Yes
Before installing the WLAN Driver update, were you ever able to connect to the AP? No
After installing the WLAN Driver update, were you ever able to connect to the AP? No

These types of WLAN issues are sometimes hard to diagnose. It does not appear to be an issue with the Nomad hardware if it is able to connect to other APs. In order to fully understand why the Nomad will not connect, the AP would need to be reset back to default settings. I have seen many times where it is some obscure setting on the AP that is causing the Nomad not to connect, even if other devices are connecting. The other devices have a different operating system and they may have a different WLAN module, driver and supplicant. You may also try to do a factory reset on the Nomad to see if this helps, but this is does erase everything except the OS, so you will need to back everything up. To perform a factory reset on the Nomad, Hold down the Power key and press the right soft key (---) to display a countdown. Continue to hold down both keys until it counts down to zero, followed by a brief appearance of the boot screen. Continue to hold both keys down until a blue screen with an eraser appears. Let up on the buttons and a message will display: WARNING: This operation will clear the persistent store including all user data, application, and settings! Press Enter to proceed, or Press any other key to cancel.

Many thanks for you recommendations Conniec; we have tried the PDA with Factory defaults but to no avail.

But recently we have managed to recreate similar conditions in the office to that on site, on our test AP; here are the log records from the AP.

Laptop and Symbol PDA Log
Interface Dot11Radio0, Station 0016.d368.896a Associated KEY_MGMT [WPA PSK]

No other Authentication is generated and the Laptops and Symbol PDA works fine...

Nomad PDA-1 Log
Interface Dot11Radio0, Station MRVL-CW 001a.6b8e.59ab Associated KEY_MGMT [WPA PSK]
PDA Makes a good connection then 1 second later. The connection is broken with..
Interface Dot11Radio0, Deauthenticating Station 001a.6b8e.59ab Reason: Sending station has left the BSS
Station 001a.6b8e.59ab Authentication failed
Station 001a.6b8e.59ab Authentication failed

Why the connection is deauthenticating is probably a big clue?

Please help.

Davinder

Thank you for the additional information. We will be looking into this issue and will contact you through the traditional support channels.

Hi

Just wondering if there was an answer on this issue as I am experiencing the same problem.

12 Nomad devices connecting to WPA2-PSK (TKIP). Either they connect and then lose the connection (go back to Available) or sit on Connecting for ages and never actually connect.

Hoping you can help
Thanks
Greg

Hi

Can anybody help me with this issue? I haven't heard back as yet...

I am a software provider and 5 clients using over 80 Nomads between them and they are all experiencing this issue. They are growing increasingly concerned and are considering returning their Nomads to us and replacing them with new devices, such at the Getac.

Surely other people have experienced this issue and can provided assistance??

Thanks
Greg