T40 with Aironet MPI350 mini PCI Wireless hangs on IP

[bdixon]

I have purchased a lease return T40, with XP and the Cisco Aironet MPI350 mini PCI wireless card. The card sees the network, will connect but fails to get an IP address. This behavior is repeated at home where my T60 works, at coffee shops without WEP security and at work with LEAP security.

I gave it to my wife for Christmas and now after about a month of working with it and a replacement Aironet MPI350 card, I am comming to this Forum which has other posts with similar symptoms but I have not tracked down a solution.

My own feeling it this is SW / Configuration issue based on the hardware being replaced. I suspect the lease machine worked fine and the hardfile was re-formatted and XP loaded and the latest Drivers / Firmware are not compatible with this "older" Cisco card . I am interested in any help , inparticular, anyone with a T40 running XP Service Pack2 and the Cisco Aironet MPI350 mini PCI wireless card to find out what Driver / Firmware combination works.
Also what application is controlling the Wireless and if everything else needs to be uninstalled.

Thanks in advance, Bob

[bdixon]

Here is some more info.

When running Access Connections I get through the stage steps till "renewing IP address" or " waiting for IP configuration " .

So all the time with various locations I am able to get to the "Association stage" . At this point I believe there is a pbysical connection with the authentication done if WEP or LEAP.

Once associated all attempts to ping a know IP address fail with an error like " target unreachable" This is even the case at home where the Linksys default gateway of 192.168.1.1 will respond to pings from my T60.

The Ethernet port with a cable between the T40 and the Linksys wireless router at home works fine.

XP is running Service Pack2.

I have noticed what seems to be some interaction between the T60 transmitter being on and the T40 behavior at home and visa versa but tried shutting the T60 off with no improvement.

It is almost like the T40 doesn't know TCPIP is supposed to go through the Wireless device ever , but will go through the Ethernet device. On that score , windows seems to setup some type of "bridge" between the Ethernet port and the Linksys that allows the Ethernet port to work and the Web to
work . Is there some equivalent " bridge" function required for the Wireless devide to connect out to the Web , ping etc ?

One last point. I have tried having Access Connections , XP and the Cisco utility be in control and get similar results with all. I have seen some treads that indicate there are problems unless all are uninstalled but one. This may be true , but my T60 running XP Service Pack2 has Access Connections and the XP software running.