I have an unusual problem which just began after a recent re-formatting of my Windows XP Home machine. My ZoomAir 4105 wlan card will only receive and transmit Ad-Hoc LAN traffic if my dial-up adapter is connected or connecting to my service provider. Below is an example of how this problem is affecting me: 1) I use SAMBA to communicate between my Windows XP Home desktop (ZoomAir 4105) and my Linux laptop. 2) I bring my Linux wlan interface up and configure it for the proper Ad-Hoc settings. 3) At this point the ZoomAir PRISM Connection manager shows excellent link quality and singal strength . 4) I then start a ping stream to my ZoomAir interface (192.168.0.1) from my laptop and watch the packets not make their way through on both the PRISM manager and the Linux console. 5) Then I double click my dial-up adapter on my Windows machine, all of the sudden I see Ad-Hoc traffic on the PRISM manager and my pings from the laptop start getting through. 6) As soon as I disable the dialup connection, my Ad-Hoc wlan traffic ceases again although the PRISM service shows "Running" in the Windows service editor. (I have confirmed the presence or absence of packets with Ethereal) The machine is up-to-date with Microsoft service packs and critical updates. The installation is minimum as I just reformated it again earlier today. My dialup adapter's driver is current. QOS is disabled. I followed the ZoomAir 4105 PCI/PCMCIA installation directions from the website. The ZoomAir 4105 worked perfectly as I wanted it too, until the reformat. I just can not seem to grasp the software relationship between my dialup adapter and my wlan card in Windows. Not a programmer here, so I'm hoping that you guys might have some ideas. Again, somehow my dialup adapter is directly affecting whether packets make it through Windows and to the ZoomAir application. Same goes for outward bound packets from the ZoomAir application through Windows and to out the interface.