Problem with Cisco 340 AP

Hello,

I am having a strange problem with a Cisco Aironet 340 Access Point. I have
a bunch of 340 and 350 PCI & PC Card clients and one new 802.11 a/b/g
client. This network is connected to the Internet via a Linksys BEFSR41
router & a cable modem. The Linksys router provides DHCP. All the 340 and
350 clients are using a driver that is labeled as being from Microsoft.
These machines work fine acquiring DHCP and authenticating to the AP. When I
try to upgrade these drivers to the latest from Cisco I am no longer able to
get DHCP but I am able to authenticate to the AP. The AP is assigned
192.168.1.2, the Linksys router is assigned 192.168.1.1. If I manually
assign a address to the client I am able to ping the AP and anything above
the AP, but not the router. I am trying to integrate a new client with a
Cisco 802.11 a/b/g card and am having the same problem and I have no driver
alternative.

The AP has the latest firmware. The AP is configured to see 192.168.1.1 as a
gateway. I do not have it configured to accept DHCP, it has a static
address. Is this where my problem is? If I allow it to be configured to
receive DHCP will it pass this along to the clients? Or am I missing
something else here? Do I need to set up a route between the AP and the
router? Any help would be appreciated.

On Sun, 04 Apr 2004 21:47:41 GMT, "dteah" <dteah+@+nospam*yahoo;;.com;;> wrote:

~ Hello,
~
~ I am having a strange problem with a Cisco Aironet 340 Access Point. I have
~ a bunch of 340 and 350 PCI & PC Card clients and one new 802.11 a/b/g
~ client. This network is connected to the Internet via a Linksys BEFSR41
~ router & a cable modem. The Linksys router provides DHCP. All the 340 and
~ 350 clients are using a driver that is labeled as being from Microsoft.
~ These machines work fine acquiring DHCP and authenticating to the AP. When I
~ try to upgrade these drivers to the latest from Cisco I am no longer able to
~ get DHCP but I am able to authenticate to the AP. The AP is assigned
~ 192.168.1.2, the Linksys router is assigned 192.168.1.1. If I manually
~ assign a address to the client I am able to ping the AP and anything above
~ the AP, but not the router. I am trying to integrate a new client with a
~ Cisco 802.11 a/b/g card and am having the same problem and I have no driver
~ alternative.

Just a guess - do you have Ethernet Encapsulation Transform set to
802.1h? If so, do things work better if you switch to RFC1042?

Setup -> AP Radio Advanced

~ The AP has the latest firmware. The AP is configured to see 192.168.1.1 as a
~ gateway. I do not have it configured to accept DHCP, it has a static
~ address. Is this where my problem is? If I allow it to be configured to
~ receive DHCP will it pass this along to the clients? Or am I missing
~ something else here? Do I need to set up a route between the AP and the
~ router? Any help would be appreciated.

None of the above should be necessary for your wireless clients to
get DHCP addresses from the router.

Aaron

Thanks for the response. Turns out the AP did want to be configured to
accept DHCP. Seems strange to me, the AP has had a static address over four
years now and the 340/350 clients have had no problem with DHCP. I changed
the AP config to accept DHCP and now the a/b/g clients work.

It is funny though, they both have the same firmware and drivers and are
running on identical hardware, but the AP only recognizes one of them as a
CIsco part, it thinks the other is non Cisco 802.11 hardware. Not a big
deal, I'm happy as long as the client can connect, but it is pretty unusual.
"Aaron Leonard" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> On Sun, 04 Apr 2004 21:47:41 GMT, "dteah" <dteah+@+nospam*yahoo;;.com;;>
wrote:
>
> ~ Hello,
> ~
> ~ I am having a strange problem with a Cisco Aironet 340 Access Point. I
have
> ~ a bunch of 340 and 350 PCI & PC Card clients and one new 802.11 a/b/g
> ~ client. This network is connected to the Internet via a Linksys BEFSR41
> ~ router & a cable modem. The Linksys router provides DHCP. All the 340
and
> ~ 350 clients are using a driver that is labeled as being from Microsoft.
> ~ These machines work fine acquiring DHCP and authenticating to the AP.
When I
> ~ try to upgrade these drivers to the latest from Cisco I am no longer
able to
> ~ get DHCP but I am able to authenticate to the AP. The AP is assigned
> ~ 192.168.1.2, the Linksys router is assigned 192.168.1.1. If I manually
> ~ assign a address to the client I am able to ping the AP and anything
above
> ~ the AP, but not the router. I am trying to integrate a new client with a
> ~ Cisco 802.11 a/b/g card and am having the same problem and I have no
driver
> ~ alternative.
>
> Just a guess - do you have Ethernet Encapsulation Transform set to
> 802.1h? If so, do things work better if you switch to RFC1042?
>
> Setup -> AP Radio Advanced
>
> ~ The AP has the latest firmware. The AP is configured to see 192.168.1.1
as a
> ~ gateway. I do not have it configured to accept DHCP, it has a static
> ~ address. Is this where my problem is? If I allow it to be configured to
> ~ receive DHCP will it pass this along to the clients? Or am I missing
> ~ something else here? Do I need to set up a route between the AP and the
> ~ router? Any help would be appreciated.
>
> None of the above should be necessary for your wireless clients to
> get DHCP addresses from the router.
>
> Aaron

On Fri, 09 Apr 2004 04:45:38 GMT, "dteah" <dteah+@+nospam*yahoo;;.com;;> wrote:

~ Thanks for the response. Turns out the AP did want to be configured to
~ accept DHCP. Seems strange to me, the AP has had a static address over four
~ years now and the 340/350 clients have had no problem with DHCP. I changed
~ the AP config to accept DHCP and now the a/b/g clients work.

Well, I don't know why that should be, unless something like this might
have happened:

- some other node on your LAN popped up using the same IP address that
had been statically configured on the AP340

- your LAN was renumbered into a different subnet

~ It is funny though, they both have the same firmware and drivers and are
~ running on identical hardware, but the AP only recognizes one of them as a
~ CIsco part, it thinks the other is non Cisco 802.11 hardware. Not a big
~ deal, I'm happy as long as the client can connect, but it is pretty unusual.

Hm, this does sound peculiar. I hooked up my new CB21AG to my AP340
yesterday, and the AP had no problem recognizing it ... note that my AP
is running the latest VXworks, 12.04. There are compatibility problems
between VXworks APs and the CB21AG in earlier releases of VXworks ...
you can get 12.04 at http://www.cisco.com/pcgi-bin/Softwa.../wlplanner.cgi .

Aaron

---

~ "Aaron Leonard" <(E-Mail Removed)> wrote in message
~ news(E-Mail Removed)...
~ > On Sun, 04 Apr 2004 21:47:41 GMT, "dteah" <dteah+@+nospam*yahoo;;.com;;>
~ wrote:
~ >
~ > ~ Hello,
~ > ~
~ > ~ I am having a strange problem with a Cisco Aironet 340 Access Point. I
~ have
~ > ~ a bunch of 340 and 350 PCI & PC Card clients and one new 802.11 a/b/g
~ > ~ client. This network is connected to the Internet via a Linksys BEFSR41
~ > ~ router & a cable modem. The Linksys router provides DHCP. All the 340
~ and
~ > ~ 350 clients are using a driver that is labeled as being from Microsoft.
~ > ~ These machines work fine acquiring DHCP and authenticating to the AP.
~ When I
~ > ~ try to upgrade these drivers to the latest from Cisco I am no longer
~ able to
~ > ~ get DHCP but I am able to authenticate to the AP. The AP is assigned
~ > ~ 192.168.1.2, the Linksys router is assigned 192.168.1.1. If I manually
~ > ~ assign a address to the client I am able to ping the AP and anything
~ above
~ > ~ the AP, but not the router. I am trying to integrate a new client with a
~ > ~ Cisco 802.11 a/b/g card and am having the same problem and I have no
~ driver
~ > ~ alternative.
~ >
~ > Just a guess - do you have Ethernet Encapsulation Transform set to
~ > 802.1h? If so, do things work better if you switch to RFC1042?
~ >
~ > Setup -> AP Radio Advanced
~ >
~ > ~ The AP has the latest firmware. The AP is configured to see 192.168.1.1
~ as a
~ > ~ gateway. I do not have it configured to accept DHCP, it has a static
~ > ~ address. Is this where my problem is? If I allow it to be configured to
~ > ~ receive DHCP will it pass this along to the clients? Or am I missing
~ > ~ something else here? Do I need to set up a route between the AP and the
~ > ~ router? Any help would be appreciated.
~ >
~ > None of the above should be necessary for your wireless clients to
~ > get DHCP addresses from the router.
~ >
~ > Aaron
~