Wireless PC Card (LM352) Connection but no Ping

  • Thread starter Thread starter Darren Powell
  • Start date Start date
D

Darren Powell

We are currently experiencing difficulty pinging across a
wireless link using a Cisco LM352. We have ruled out most
possibilities of error and need some assistance.

We have tested the hardware by installing a full blown XP
Pro installation on the target embedded PC and installed
the LM352 using the downloaded drivers from Cisco. The
Cisco utilities are not needed and only complicate
things. The SSID is set, static IP, and AdHoc networking
(No Infrastructure). The LAN connection is disabled to
force the routing through the wireless card. These
settings allow for communication to a laptop with the
same setup.

We then move to XP embedded. We have created a component
from the same XP driver downloaded from Cisco. First to
test our TCP/IP settings, a ping test is conducted
between a wired PC and the target PC. Both directions are
successful. The wired connection is then disabled. The
same settings are applied as stated above. No exceptions.
The radios connect. The test laptop sees the correct SSID
and the signal strength is excellent. But pinging is
unsuccessful in either direction. This leads us to
believe it is a networking issue, that we have not
included all the needed components.

By the way: the registry looks the same as with the full
blown XP Pro, the route table looks correct, and ipconfig
shows the correct settings for the IP address.

We have exploded our target size by adding anything that
we think is necessary for the wireless TCP/IP connection.
But obviously we are missing something. Any ideas,
anything would be helpful. A big THANK YOU for any help
you may provide.

Darren Powell
Space & Naval Warfare Systems Center - San Diego
(e-mail address removed)
 
Darren,
It's either a missing dependency for the wireless feature, a missing
dependency for networking or it's a missing dependency in the Cisco package
you componentized.

Here's a basic test - go to www.xpefiles.com, get the slx called vampire.slx
for troubleshooting purposes only. It'll add a dependency on most windows
features and class installers in the database, the runtime will be huge.
Import your pmq into that SLX, add your Cisco specific components, rebuild
and deploy your runtime. If your wireless connectivity still fails then it's
most likely your Cisco package at fault. If it works then you know there was
a missing dependency in the original configuration that has since been
satisfied. BTW, i think i saw a Cisco component up there a long time ago,
try comparing the SLD to yours if it's still there.

You can monitor your system using free tools form www.sysinternals.com like
RegMon and FileMon. Run these when the machine is reproducing your issue.
Sifting through the logs you may find tons of errors related to missing
files or registry keys that are related to your wireless problem.

Lastly, while I don't know much about WZC, there have been some posts in the
past to the newsgroup on wireless troubleshooting maybe you can find some
info there as well. Check this link for "Wireless" posts in the Google
archives:
http://groups.google.com/groups?hl=...a=group=microsoft.public.windowsxp.embedded.*

Andy
 
Back
Top