Greetings, It takes a lot, and I do mean a LOT, to get me to ask for help. And to get me to ask for help ion the internet, a heck of a lot more. As it stands, though, I'm at my wit's end. I've been having troubles with my computer (win7, x64) connecting to my AP (dlink WRT54g), using two different WiFi cards (Alfa Networks 1Watt, Belkin Wireless Basic; one at a time). I stay connected for a good period of time (a couple days without incident), but then the computer loses connection and cannot reestablish it. I can connect to my neighbor's unsecured WiFi AP's, , but not my own, with either adapter. I can connect to my AP with my other machine with either adapter. I have been able to temporarily 'fix' the issue by disabling/enabling the adapter several times, and deleting the Wireless Network save data, and treating it as a new network. However, this time, nothing will work. I have rebooted both the AP and computer, I have uninstalled both adapters, reinstalled and updated them, I have run the diagnostics. I can connect to any network, save for my own. The diagnostic reported that it couldn't identify the problem (Imagine that; the troubleshooter being useless, as usual...), and reported that it could not connect to the hidden network, 'dlink' (It's not a hidden network!) Report below: Windows Network Diagnostics Publisher details Issues found Windows can't connect to the hidden network "dlink"Windows can't connect to the hidden network "dlink"This network is marked as a "hidden" network and is either not in range of this computer or the wireless settings saved on this computer do not match the settings of the network. Detected Check your wireless network settings Not run Issues foundWindows can't connect to the hidden network "dlink" Detected This network is marked as a "hidden" network and is either not in range of this computer or the wireless settings saved on this computer do not match the settings of the network. Check your wireless network settings Not run Make sure your computer is in range of "dlink" and that the network settings match the wireless router or access point settings. Detection details Diagnostics Information (Network Adapter) Details about network adapter diagnosis: Network adapter Wireless Network Connection 4 driver information: Description . . . . . . . . . . : Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter Manufacturer . . . . . . . . . : Realtek Semiconductor Corp. Provider . . . . . . . . . . . : Realtek Semiconductor Corp. Version . . . . . . . . . . . : 6.1314.626.2009 Inf File Name . . . . . . . . . : C:\Windows\INF\oem29.inf Inf File Date . . . . . . . . . : Friday, June 26, 2009 7:22:50 AM Section Name . . . . . . . . . : RTL8187.ndi Hardware ID . . . . . . . . . . : usb\vid_0bda&pid_8187&rev_0100 Instance Status Flags . . . . . : 0x180600a Device Manager Status Code . . : 0 IfType . . . . . . . . . . . . : 71 Physical Media Type . . . . . . : 9 Diagnostics Information (Wireless Connectivity) Details about wireless connectivity diagnosis: Information for connection being diagnosed Interface GUID: 52451768-20f5-4188-9e87-9c1091b8d582 Interface name: Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter #2 Interface type: Native WiFi Profile: dlink SSID: dlink SSID length: 5 Connection mode: Infra Security: Yes Connect even if network is not broadcasting: NoConnection incident diagnosed Auto Configuration ID: 8 Connection ID: 16Connection status summary Connection started at: 2011-07-15 21:13:55-334 Profile match: Success Pre-Association: Success Association: Fail Security and Authentication: Not startedList of visible access point(s): 25 item(s) total, 25 item(s) displayed BSSID BSS Type PHY Signal(dB) Chnl/freq SSID-------------------------------------------------------------------------00-22-A4-85-41-69 Infra g -49 1 2WIRE20700-23-51-1E-63-E1 Infra g -77 1 2WIRE485B0-E7-54-65-93-51 Infra g -54 1 2WIRE87500-24-C8-6F-2E-C0 Infra g -63 1 NHES_GUEST30-46-9A-85-2D-7C Infra <unknown> -68 1 MandAsAC-81-12-4E-1C-60 Infra <unknown> -71 9 WiFiRSU_9200-26-F3-52-25-D8 Infra <unknown> -67 9 HOME-25D800-26-F3-52-25-D9 Infra <unknown> -79 9 (Unnamed Network)00-26-F3-52-25-DA Infra <unknown> -81 9 (Unnamed Network)00-26-F3-52-25-DB Infra <unknown> -73 9 (Unnamed Network)E0-91-F5-C0-90-EB Infra <unknown> -53 2 NETGEARC0-83-0A-DF-F0-01 Infra g -61 4 2WIRE19000-25-3C-45-4E-D1 Infra g -58 4 2WIRE66500-25-3C-45-F4-A9 Infra g -60 4 2WIRE5471C-AF-F7-CC-9D-51 Infra <unknown> -83 6 Navasota Rattlers00-14-BF-F9-AB-D9 Infra g -64 6 linksys00-11-93-2E-47-50 Infra g -59 8 axxessintertel34-EF-44-E4-64-E9 Infra g -58 8 2WIRE950C0-83-0A-BD-A4-41 Infra g -81 8 2WIRE11864-0F-28-19-F2-91 Infra g -60 10 MPatel3C-EA-4F-86-C9-61 Infra g -62 10 2WIRE14000-1C-F0-C2-07-03 Infra g -51 11 dlink3C-EA-4F-BC-F7-F1 Infra g -53 11 2WIRE7333C-EA-4F-64-14-A1 Infra g -52 11 2WIRE29900-25-3C-53-8C-B1 Infra g -52 11 2WIRE974Connection History Information for Auto Configuration ID 9 List of visible networks: 23 item(s) total, 23 item(s) displayed BSS Type PHY Security Signal(RSSI) Compatible SSID ------------------------------------------------------------------------------ Infra g Yes 92 Yes 2WIRE207 Infra g Yes 35 Yes 2WIRE485 Infra g Yes 82 Yes 2WIRE875 Infra g No 64 Yes NHES_GUEST Infra <unknown> Yes 53 Yes MandAs Infra <unknown> Yes 47 Yes WiFiRSU_92 Infra <unknown> Yes 55 Yes HOME-25D8 Infra <unknown> Yes 43 Yes (Unnamed Network) Infra <unknown> No 84 Yes NETGEAR Infra g Yes 68 Yes 2WIRE190 Infra g Yes 74 Yes 2WIRE665 Infra g Yes 69 Yes 2WIRE547 Infra <unknown> Yes 23 Yes Navasota Rattlers Infra g No 62 Yes linksys Infra g No 72 Yes axxessintertel Infra g Yes 73 Yes 2WIRE950 Infra g Yes 28 Yes 2WIRE118 Infra g Yes 70 Yes MPatel Infra g Yes 66 Yes 2WIRE140 Infra g Yes 88 Yes dlink Infra g Yes 84 Yes 2WIRE733 Infra g Yes 85 Yes 2WIRE299 Infra g Yes 86 Yes 2WIRE974 List of preferred networks: 2 item(s) Profile: NETGEAR SSID: NETGEAR SSID length: 7 Connection mode: Infra Security: No Set by group policy: No Connect even if network is not broadcasting: No Connectable: Yes Profile: dlink SSID: dlink SSID length: 5 Connection mode: Infra Security: Yes Set by group policy: No Connect even if network is not broadcasting: No Connectable: Yes Information for Connection ID 17 Connection started at: 2011-07-15 21:13:57-337 Auto Configuration ID: 9 Profile: NETGEAR SSID: NETGEAR SSID length: 7 Connection mode: Infra Security: No Pre-Association and Association Connectivity settings provided by hardware manufacturer (IHV): No Security settings provided by hardware manufacturer (IHV): No Profile matches network requirements: Success Pre-association status: Success Association status: Success Last AP: e0-91-f5-c0-90-eb Security and Authentication Configured security type: Open Configured encryption type: None 802.1X protocol: No Key exchange initiated: Yes Unicast key received: No Multicast key received: No Number of security packets received: 0 Number of security packets sent: 0 Security attempt status: Success Connectivity Packet statistics Ndis Rx: 20 Ndis Tx: 92 Unicast decrypt success: 20 Multicast decrypt success: 0 Unicast decrypt failure: 50 Multicast decrypt failure: 0 Rx success: 155 Rx failure: 0 Tx success: 114 Tx failure: 0 Tx retry: 0 Tx multiple retry: 0 Tx max lifetime exceeded: 0 Tx ACK failure: 0 Roaming history: 0 item(s) Information for Auto Configuration ID 8 List of visible networks: 19 item(s) total, 19 item(s) displayed BSS Type PHY Security Signal(RSSI) Compatible SSID ------------------------------------------------------------------------------ Infra <unknown> No 85 Yes NETGEAR Infra g Yes 92 Yes 2WIRE207 Infra g Yes 82 Yes 2WIRE875 Infra <unknown> Yes 35 Yes linksys Infra <unknown> Yes 37 Yes belkin.498 Infra g Yes 30 Yes 2WIRE485 Infra g Yes 42 Yes 2WIRE058 Infra <unknown> Yes 41 Yes WiFiRSU_92 Infra g Yes 85 Yes 2WIRE299 Infra <unknown> Yes 53 Yes HOME-25D8 Infra g Yes 82 Yes dlink Infra g Yes 84 Yes 2WIRE733 Infra g Yes 85 Yes 2WIRE974 Infra <unknown> No 60 Yes RepublicHollowTree2 Infra g Yes 67 Yes 2WIRE547 Infra g Yes 68 Yes 2WIRE190 Infra g No 62 Yes linksys Infra g No 72 Yes axxessintertel Infra g Yes 73 Yes 2WIRE950 List of preferred networks: 2 item(s) Profile: NETGEAR SSID: NETGEAR SSID length: 7 Connection mode: Infra Security: No Set by group policy: No Connect even if network is not broadcasting: No Connectable: Yes Profile: dlink SSID: dlink SSID length: 5 Connection mode: Infra Security: Yes Set by group policy: No Connect even if network is not broadcasting: No Connectable: No Reason: 0x00028006 Information for Connection ID 16 Connection started at: 2011-07-15 21:13:55-334 Auto Configuration ID: 8 Profile: dlink SSID: dlink SSID length: 5 Connection mode: Infra Security: Yes Pre-Association and Association Connectivity settings provided by hardware manufacturer (IHV): No Security settings provided by hardware manufacturer (IHV): No Profile matches network requirements: Success Pre-association status: Success Association status: Fail 0x00038002 Association reason code: 0x00000002 Information for Connection ID 15 Connection started at: 2011-07-15 20:59:18-833 Auto Configuration ID: 8 Profile: NETGEAR SSID: NETGEAR SSID length: 7 Connection mode: Infra Security: No Pre-Association and Association Connectivity settings provided by hardware manufacturer (IHV): No Security settings provided by hardware manufacturer (IHV): No Profile matches network requirements: Success Pre-association status: Success Association status: Success Last AP: e0-91-f5-c0-90-eb Security and Authentication Configured security type: Open Configured encryption type: None 802.1X protocol: No Key exchange initiated: Yes Unicast key received: No Multicast key received: No Number of security packets received: 0 Number of security packets sent: 0 Security attempt status: Success Connectivity Packet statistics Ndis Rx: 0 Ndis Tx: 0 Unicast decrypt success: 135 Multicast decrypt success: 0 Unicast decrypt failure: 50 Multicast decrypt failure: 0 Rx success: 1190 Rx failure: 0 Tx success: 44 Tx failure: 0 Tx retry: 0 Tx multiple retry: 0 Tx max lifetime exceeded: 0 Tx ACK failure: 0 Roaming history: 1 item(s) Times: 2011-07-15 21:13:55-333 Roamed from BSSID: 00-00-00-00-00-00 Reason: 0x00010001 Disconnected from BSSID: 00-00-00-00-00-00 Reason: 0x00000101 Information for Connection ID 14 Connection started at: 201 Diagnostics Information (Wireless Connectivity) Details about wireless connectivity diagnosis: For complete information about this session see the wireless connectivity information event.Helper Class: Auto Configuration Initialize status: SuccessInformation for connection being diagnosed Interface GUID: 52451768-20f5-4188-9e87-9c1091b8d582 Interface name: Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter #2 Interface type: Native WiFi Profile: dlink SSID: dlink SSID length: 5 Connection mode: Infra Security: Yes Connect even if network is not broadcasting: NoResult of diagnosis: Problem found Issue referred to: RNWF MSM Helper ClassRoot cause:Windows could not connect to "dlink"You can try to connect again.Repair option:Reset your wireless network adapterThis will disable and then enable the network adapter "Wireless Network Connection 4" on this computer. Network Diagnostics Log File Name: 87C22111-E519-46B4-8DAC-EA16148A55BB.Diagnose.Admin.0.etl Collection information Computer Name: KRN4WIN7X64ULT Windows Version: 6.1 Architecture: amd64 Time: Friday, July 15, 2011 9:14:00 PM Publisher details Windows Network Diagnostics Detects problems with network connectivity. Package Version: 1.0 Publisher: Microsoft Windows If I may draw your attention to the part: Connection started at: 2011-07-15 21:13:55-334 Profile match: Success Pre-Association: Success Association: Fail Security and Authentication: Not started Does anyone know what this means/what this is/how to fix it? I've seen a lot of similar questions all over, and no answers that fit my situation.

I did look at: http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/fixing-wireless-hidden-network-problem-on-windows/7a893bef-1f1a-4f5e-b6a2-cc4fc16b361a But changing the AP from WEP to WPA is not an option. We have devices that require WEP, and quite honestly, I shouldn't have to go buy new equipment to work around a bug in Microsoft's operating system.

you have a Linksys WRT54G that you gave a SSID name of "dlink"? dlink is one of the default names and that alone can cause issues. you should always use a unique name and never one of the defaults. You posted a dump of the available wireless in your environment and there might be someone else with a hidden network with an SSID of "dlink". The WRT54G is old, there were a large number of hardware revisions. You need to make certain you have applied the latest available firmware. WEP is so insecure and easily hacked that the newest 802.11n standard makes support for it optional. Different vendors treated this differently in their drivers for NIC cards. Intel posted this statement: http://www.intel.com/support/wireless/wlan/4965agn/sb/cs-025643.htm WEP can be broken in less than 60 seconds. On Sat, 16 Jul 2011 02:26:20 +0000, CrysisMK2 wrote: > > >I did look at: > >http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/fixing-wireless-hidden-network-problem-on-windows/7a893bef-1f1a-4f5e-b6a2-cc4fc16b361a > >But changing the AP from WEP to WPA is not an option. We have devices that require WEP, and quite honestly, I shouldn't have to go buy new equipment to work around a bug in Microsoft's operating system. Barb Bowman http://www.digitalmediaphile.com

Visit Linksys support and confirm that you have the latest firmware revision for the router\AP. Delete all of the connections saved for wireless and then from the Network Center, create a new connection. Are you copying and pasting the WEP key? You may just have a typo error if you are inputting it manually.

I know WEP can be hacked, I use BackTrack5 for pentesting, and know all about 802.11 radio analysis. I have mac address filtering enabled, and I wrote a desktop widget that watches connections and data volume moving on my network, to keep people out. I have the latest firmware. Changing from WEP is not an option. I already stated that I was able to get it to work in the past by deleting the network data, but it doesn't work anymore. Also, it's a passphrase, so yes, I'm entering it correctly. The connection fails on Association, not Authentication.

did you change the SSID name from dlink to something unique? that is the only other advice I can offer. Best of luck. On Sat, 16 Jul 2011 14:36:35 +0000, CrysisMK2 wrote: > > >I know WEP can be hacked, I use BackTrack5 for pentesting, and know all about 802.11 radio analysis. I have mac address filtering enabled, and I wrote a desktop widget that watches connections and data volume moving on my network, to keep people out. I have the latest firmware. Changing from WEP is not an option. > >I already stated that I was able to get it to work in the past by deleting the network data, but it doesn't work anymore. Also, it's a passphrase, so yes, I'm entering it correctly. The connection fails on Association, not Authentication. Barb Bowman http://www.digitalmediaphile.com

Ok, so in the properties of the troublesome network connection, security tab, for WEP it should be: Security type - No authentication (open) Encryption type- WEP Network security key- your passphrase