So I have set up an Apple network with an Airport Extreme (5th Generation) as the base unit and the newest Airport Express version which is used to wirelessly extend the network in the deeper areas of my home. In that deeper area, I have an older HP Windows Vista PC that has been on the network using an original version (non-revved) DWA-130 Wireless N adapter I bought several years back. When I recently set up the Apple network, this specific PC worked well enough (about 80% connectivity on 2.4 GHz with the Apple network. The Wireless Connection Manager showed my home network SSID name to assess connectivity, etc, just like all the other PCs in the home.
Well, I had a newer version DWA-130 (Rev E) sitting around and decided to remove my old driver for the DWA-130 and install the newer Rev E driver and use the new DWA-130 Wireless N unit in my powered USB hub. All installed and worked well. I am getting excellent signal (all bars now at 100%). However a few flaky things are occurring that maybe someone on this forum can aid in my perplexity.
When I bring up the Wireless Connection Manager, there are two entries with my SSID. One related to my Airport Extreme (72%) and the other related to my Airport Express (100%). However, no matter which one I select and connect to, it always shows the 100 % item as the connected one. Great, no biggie. However, I didn't have this before with the older DWA-130. The next weird thing is that if I do a right click on the Windows wireless network icon in the task tray and view the networks in my area, my network for that PC just shows as a generic D-Link Wireless network, and does not show my actual SSID. However, if I hover over that icon in the task tray, it shows that it is connected to my actual SSID. What gives with this? Finally, I use the PC version of the Airport Utility to see and manage my Apple Airport devices. Now when I bring this program up, it cannot detect either my Airport Extreme or Airport Express units. Note that on all my other PCs and Macs in the home, all is working well, as expected. The only thing that has changed on that problematic PC is a new driver and unit for the DWA-130. I am planning on installing the DWA-130 Rev E 2010 driver version later today to see if this fixes any of these problems with an Apple network integration.
In the meantime, does anyone got any ideas? I uninstalled the new DWA-130 driver and reinstalled. I re-set up the Apple home network. Nothing has changed things. Again, my connectivity is great and working, but wondering why I am seeing the type weirdness that I describe. Thanks in advance.