Cisco 1252AP and Intel Proset problems

[mrsentraser]

American Honda required us to install a new wireless network for our diagnostic equipment to communicate over. We got 2 Cisco 1252AP's, but are currently only using the 1 with the other one setup identical and only to be used it a failure of the primary. Along with the two APs, we also purchased two Panasonic Toughbooks to use as diagnostic tablets. After setting up the AP's and testing with my company laptop (Toshiba running Vista sp2) and having no issues connecting to the wireless and communicating on the internet I assumed everything was working ok. We setup both Toughbooks connecting to a linksys in our office and everything is working fine. Brought the Toughbooks down to Honda and they will associate to the AP, but will not pull an IP address from our firewall. Toshiba laptop connects fine still as does my android phone. I manually assigned an ip address in the 2nd toughbook and I could ping the ap. I attempted to ping the switch that our Ap is connected to, but it timed out. I did a tracert to the firewall and after a really long first hop, it began to communicate and I coule ping any device on the network. I changed the adapter over to DHCP and removed all the static ip information. I then restarted the laptop and now it's pulling an IP address just fine from DHCP and works like it should. I thought i figured it out, so I tried the same with Toughbook 1. It's not working though. Still fails to get an IP from DHCP, and with a manual address can't ping the firewall. It can ping the AP and both clients on the AP, but can't ping the firewall or even the switch connected to the AP. I'm stuck here, any suggestions from you guys would be appreciated.

 

[spidey07]

Make sure windows zero config service is fully stopped and not set to run at startup. You can have problems when that's running and you're trying to use a wireless client utility.

 

[Cooky]

Is this autonomous or LWAPP/CAPWAP?
Which radio frequencies are enabled on the AP? 2.4 or 5Ghz?

First make sure you have a somewhat clean airspace.
Then ensure there's enough DHCP leases.
After you try everything else, debug from WLC or AP itself to see what's going on.

 

[mrsentraser]

It's autonomous, no need for a controller.
Radio is set to 2.4 Ghz

Air space is clean, it will actually allow 2 devices to authenticate and pull dhcp addresses. Then anything after just authenticates and times out getting an address. There are PLENTY of DHCP leases left... i'll have to try to debug.

 

[RadiclDreamer]

Post scrubbed configs?