Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[scan80269]

My DWA-160 revA adapter cannot connect to my DIR-655 router with the wireless network set to invisible (SSID broadcast disabled).  This happens only in conjunction with the DWA-160 XP driver (1.40, arusb_xp.sys 3.0.0.135, and older revisions).  The DWA-160 Vista driver has no problems working with my invisible network.  Here's what I have discovered:

* Windows XP + DWA-160 XP driver arusb_xp.sys + DIR-655 router with SSID
broadcast DISABLED: wireless connection FAILED

* Windows XP + DWA-160 XP driver arusb_xp.sys + DIR-655 router with SSID
broadcast ENABLED: wireless connection SUCCESSFUL

* Windows Vista + DWA-160 Vista driver arusb_lh.sys + DIR-655 router with
SSID broadcast DISABLED: wireless connection SUCCESSFUL

* Windows Vista + DWA-160 Vista driver arusb_lh.sys + DIR-655 router with
SSID broadcast ENABLED: wireless connection SUCCESSFUL

My DIR-655 is running 1.21 firmware, and I use WPA2-PSK AES encryption.

This suggests the DWA-160 hardware is fine, but there is an issue specifically with the DWA-160 XP driver (Atheros) working with invisible networks.  I always do wireless setup manually by entering the name of my wireless network to XP Wireless Zero Configuration, and this has always worked until I started using the DWA-160.  I also have other wireless clients such as DWA-556 (PCIe) and other brands that have absolutely no problems connecting to my invisible network with the client running XP or Vista.  The DWA-160 can connect when attached to a client running Vista, but with XP, the only way to get it to connect is to make my network visible (enable SSID broadcast).

I have exchanged email with D-Link tech support several times, but the issue remains.  I have tried many troubleshooting techniques such as disabling/enabling the adapter, uninstalling/re-installing the driver, but the only solution that works for the DWA-160 is to make the network visible at the router.  I have requested D-Link tech support to submit this problem as an XP driver issue back to their engineering department, but I cannot tell if they have agreed to do this.

At this point, I am restricting the use of my DWA-160 to clients running Vista, but I am eager for D-Link/Atheros to release an updated XP driver to fix this so I can use my DWA-160 with XP again.

[zambarossa]

To be honest, an invisible SSID doesn't buy you much. Wireless device companies advertise that as an added security measure but that is very misleading. Anyone can get a free sniffer off the web and see all the networks (the SSID is exchanged in the clear even when you set it to hidden). I have a sniffer running now and can see every AP in the vicinity even ones that hide the SSID. If you have WPA or WPA2 enabled and a strong key selected, you are all set and you can enable your SSID, no one will be able to connect to it, they just see its name. People who can get around your security can anyway very easily get your SSID. So I guess although this doesn't address your original concern, turning on the SSID broadcast will solve your issue. I have it on because my Nintendo Wii doesn't like hidden SSIDs.
Hope that helps.