Cannot get connect to wireless all of a sudden

[Travis570]

I have a Pavilion dm4-2165dx with Windows 7 64 bit.  I have not made any changes to the laptop or the network.  All of a sudden today I could not connect to my home wireless connection eventhough all of the other machines in my house can still connect without a problem.  

My wireless connection light is on and it is blue.  

I can still conect to the internet through wired ethernet into my router.  

I have tried all of the trouble shooters.  

I tried a windows roll back and that didn't work either.  

The wireless drivers that are listed in device manager are:

Intel(r) Wifi Link 1000 BGN 14.1.1.3

Microsoft Virtual Wifi Miniport Adapter 6.1.7600.16385

Microsoft Virtual Wifi Miniport Adapter 2 6.1.7600.16385

Thank you in advance for any help that you can give me.  

[Paul_Tikkanen]

Hi:

See if installing the latest network driver from Intel fixes the issue.

You want the second one listed (driver only 64 bit).

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21244&ProdId=3141&lang=eng&OSVersion=...

Paul

[Travis570]

Thanks Paul.  I tried that and restarted my machine and it's still not working.  I did verify that the driver is now the current version.

[Travis570]

Here's my troubleshooting log if this helps:

Windows Network Diagnostics

Publisher details

Issues found

Problem with wireless adapter or access point

Problem with wireless adapter or access point

Detected

Investigate router or access point issues

Failed

Reset the wireless adapter

Completed

Refer to Windows Help and Support for more information about wireless connectivity problems

Completed

Issues found

Detection details

6

Problem with wireless adapter or access point

Detected

Investigate router or access point issues

Failed

If you're connected to a hotspot or domain network, contact the network administrator. Otherwise: 1. Unplug or turn off the device. 2. After all the lights on the device are off, wait at least 10 seconds. 3. Turn the device back on or plug it back into the power outlet. To restart a router or access point that has a built-in battery, press and quickly release the Reset button.

Reset the wireless adapter

Completed

Network Diagnostics Log

File Name: 351C38BD-5C67-4D32-8CE9-13494B7D4023.Repair.1.etlRefer to Windows Help and Support for more information about wireless connectivity problems

Completed

Windows cannot resolve your wireless connectivity issue.

Detection details

Diagnostics Information (Network Adapter)

Details about network adapter diagnosis: 

Network adapter Wireless Network Connection driver information:

   Description . . . . . . . . . . : Intel(R) Centrino(R) Wireless-N 1000
   Manufacturer  . . . . . . . . . : Intel Corporation
   Provider  . . . . . . . . . . . : Intel
   Version   . . . . . . . . . . . : 14.1.1.3
   Inf File Name . . . . . . . . . : C:\Windows\INF\oem2.inf
   Inf File Date . . . . . . . . . : Sunday, May 01, 2011  12:00:24 PM
   Section Name  . . . . . . . . . : Install_MPCIEX_Lenovo_1000_HMC_BGN_WIN7_64
   Hardware ID . . . . . . . . . . : pci\ven_8086&dev_0084&subsys_13158086
   Instance Status Flags . . . . . : 0x180200a
   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: 4aace649-06a4-4819-be33-cd9784c7d6b9
 Interface name: Intel(R) Centrino(R) Wireless-N 1000
 Interface type: Native WiFi
 Profile: Discovery connection
 SSID: QGBL3
 SSID length: 5
 Connection mode: Infra
 Security: Yes
 Connect even if network is not broadcasting: No

Connection incident diagnosed
 Auto Configuration ID: 1
 Connection ID: 5

Connection status summary
 Connection started at: 2012-06-16 20:40:55-060
 Profile match: Success
 Pre-Association: Success
 Association: Success
 Security and Authentication: Fail

List of visible access point(s): 4 item(s) total, 4 item(s) displayed
        BSSID		BSS Type PHY	Signal(dB)	Chnl/freq    SSID
-------------------------------------------------------------------------
00-26-62-5C-10-4F	Infra	 <unknown>	-38		6	 QGBL3
00-21-E9-B7-1E-5B	Infra	 <unknown>	-83		9	 Casa Jorge
00-25-9C-3B-2E-4E	Infra	 <unknown>	-89		6	 feinberg
00-7F-28-05-FE-BC	Infra	 <unknown>	-86		11	 X65L2

Connection History

 Information for Auto Configuration ID 2

  List of visible networks: 4 item(s) total, 4 item(s) displayed
  BSS Type PHY	Security	Signal(RSSI)	Compatible	SSID
  ------------------------------------------------------------------------------
  Infra	 <unknown>	Yes		99	Yes		QGBL3
  Infra	 <unknown>	Yes		28	Yes		Casa Jorge
  Infra	 <unknown>	Yes		18	Yes		feinberg
  Infra	 <unknown>	Yes		23	Yes		X65L2

  List of preferred networks: 0 item(s)

 Information for Auto Configuration ID 1

  List of visible networks: 4 item(s) total, 4 item(s) displayed
  BSS Type PHY	Security	Signal(RSSI)	Compatible	SSID
  ------------------------------------------------------------------------------
  Infra	 <unknown>	Yes		99	Yes		QGBL3
  Infra	 <unknown>	Yes		38	Yes		Casa Jorge
  Infra	 <unknown>	Yes		18	Yes		feinberg
  Infra	 <unknown>	Yes		23	Yes		X65L2

  List of preferred networks: 0 item(s)

 Information for Connection ID 5
 Connection started at: 2012-06-16 20:40:55-060
  Auto Configuration ID: 1
  Profile: Discovery connection
  SSID: QGBL3
  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: Success
    Last AP:  00-26-62-5c-10-4f
  Security and Authentication
   Configured security type: Open
   Configured encryption type: WEP
   802.1X protocol: Yes
    Authentication mode: Invalid (5)
    Number of 802.1X restarts: 0
    Number of 802.1X failures: 0
   Key exchange initiated: No
   Number of security packets received: 0
   Number of security packets sent: 0
   Security attempt status: Fail 0x0003800b

 Information for Connection ID 4
 Connection started at: 2012-06-16 20:40:53-390
  Auto Configuration ID: 1
  Profile: Discovery connection
  SSID: QGBL3
  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 3
 Connection started at: 2012-06-16 20:40:51-701
  Auto Configuration ID: 1
  Profile: Discovery connection
  SSID: QGBL3
  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 2
 Connection started at: 2012-06-16 20:40:40-356
  Auto Configuration ID: 1
  Profile: Discovery connection
  SSID: QGBL3
  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: Success
    Last AP:  00-26-62-5c-10-4f
  Security and Authentication
   Configured security type: Open
   Configured encryption type: WEP
   802.1X protocol: Yes
    Authentication mode: Invalid (5)
    Number of 802.1X restarts: 2
    Number of 802.1X failures: 0
   Key exchange initiated: No
   Number of security packets received: 0
   Number of security packets sent: 3
   Security attempt status: Fail 0x0003800b

 Information for Connection ID 1
 Connection started at: 2012-06-16 20:40:30-169
  Auto Configuration ID: 1
  Profile: Discovery connection
  SSID: QGBL3
  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: Success
    Last AP:  00-26-62-5c-10-4f
  Security and Authentication
   Configured security type: Open
   Configured encryption type: WEP
   802.1X protocol: Yes
    Authentication mode: Invalid (5)
    Number of 802.1X restarts: 0
    Number of 802.1X failures: 0
   Key exchange initiated: No
   Number of security packets received: 0
   Number of security packets sent: 0
   Security attempt status: Fail 0x0003800b

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: Success

Information for connection being diagnosed
 Interface GUID: 4aace649-06a4-4819-be33-cd9784c7d6b9
 Interface name: Intel(R) Centrino(R) Wireless-N 1000
 Interface type: Native WiFi
 Profile: Discovery connection
 SSID: QGBL3
 SSID length: 5
 Connection mode: Infra
 Security: Yes
 Connect even if network is not broadcasting: No

Result of diagnosis: Problem found
 Issue referred to: L2Sec Helper Class

Root cause:
Windows could not connect to "QGBL3"
You can try to connect again.

Repair option:
Try connecting to "QGBL3" again, or connect to a different network
If you still can't connect to the network and you are the administrator, turn off your wireless router or access point, wait at least 10 seconds, turn it back on, and then try connecting again.

Diagnostics Information (L2sec Helper Class)

Details about L2Sec Helper Class diagnosis: 

For complete information about this session see the Wireless Diagnostic Informational Event.

Helper Class: Layer2 Security
 Initialize Status: Success

Result of diagnosis: There may be a problem

Information for connection being diagnosed
 Interface GUID: {4aace649-06a4-4819-be33-cd9784c7d6b9}
 Interface name: Intel(R) Centrino(R) Wireless-N 1000
 Interface type: Native WiFi
 Profile: Discovery connection
 SSID: QGBL3
 SSID length: 5
 Connection mode: Infra
 Security enabled: Yes
 Connection ID: 5
 Security settings provided by hardware manufacturer (IHV): No
 Profile matches network requirements: Yes
 Pre-Association and association status: Success
 Security and Authentication:
  Configured security type: Open
  Configured Encryption type: WEP
  Security connect status: Fail 0x0003800b
  Number of security packets received: 0
  Number of security packets sent: 0
  802.1X protocol: Yes
   Authentication Identity: Invalid
   IAS Server engaged: No
   EAP Method supported by IAS Server: Unknown
   EAP type: 0
   EAP Error: None
   Number of 802.1X restarts: 0
   Number of 802.1X failures: 0
   802.1X status: Fail 0x00000000
  Key exchange initiated: No
   Unicast keys received: No
   Multicast keys received: No

Network Diagnostics Log

File Name: 351C38BD-5C67-4D32-8CE9-13494B7D4023.Diagnose.0.etl

Other Networking Configuration and Logs

File Name: NetworkConfiguration.cabCollection information Computer Name: HARRYLAPTOP-HP Windows Version:

6.1

Architecture:

amd64

Time:

Saturday, June 16, 2012 8:41:10 PM

[Paul_Tikkanen]

Did you try deleting your wireless connection, uninstalling the adapter in the device manager, rebooting and reinstalling the driver?

That is about the only other thing I can think of.

I noticed you don't have the network card set to connect if the SSID is not being broadcast, so I assume your SSID is being broadcasted, correct?

Because if your SSID is not being broadcasted, that is probably the issue.

Paul

[Travis570 · Accepted solution]

The solution to my problem was to reset my router.  At first I did not think that was the correct solution because all of my other devices could still connect to the wireless router without a problem.  

Thank you for all of your help.  I really appreciated it.

[Paul_Tikkanen]

You're very welcome.

Glad you got it sorted out.

Resetting the router would have been the last thing I did too, if every other wireless device was connecting to it.

Good thinking!

Paul

[Rod314]

I purchased 2 identical Pavilion d6 laptops for my two sons. After the initial 2 weeks of good connection to my home router (netgear) and a further 2 weeks working fine at a different location this time with a BT HUB both units started misbehaving when we returned home. One would only connect intermittently and the other about 50% of the time but with a very slow connection. I tried many of the suggestions on the various threads including updating both drivers (even though the Windows 7 tool in Device Manager said they did not need updating). Finally I found a thread suggesting that the Intel wireless boards in these units prefer to connect via WAP (my router was set up with a WEP radio config as I have several other older PC's in the house which all work fine). Once I added an additional WAP access point to my router I deleted the original wireless configs in both units and added the new WAP enabled access points. All seems to be working OK now. A long slog but seems to have got there in the end

[Paul_Tikkanen]

Thanks for sharing.

Glad you were able to reconnect your notebooks.

You will find that no N type wireless device will connect at its advertised connection speed with any other kind of security enabled but WPA2-Personal AES.

I found that out inadvertently when I hooked my first wireless N device to my wireless N router, which I had set WEP security like you did.  Based on how I set up my old G router.

I couldn't understand why it would only connect at 54 MBPS.

Then I changed it to WPA2-Personal TKIP (because I remembered that TKIP was how we had to connect our wireless notebooks at work), so I figured that was the best way, since they were doing it that way at work.

Still wouldn't connect at more than 54 MBPS!

Then I did some reading and found that AES replaced TKIP as a more secure encryption method.

When I changed the security setting to WPA2-Personal-AES, my wireless N card then connected at the wireless N speed I thought it should get.

[Rod314]

Thanks for this confirmation. A couple of final thoughts esp for anyone else with similar problems searching these threads;

1. I still cannot figure out why when we first used the two units they appeared to work fine even when connected via the original WEP setting (including having to download the gazillion Windows updates first time around ;-). It seems to be somehow connected with the proliferation of BT Openzone hubs in out street - is it possible that a new one as recently come on line that is intefering with the HP wireless cards when in WEP mode (but not my other pc's or MAC)?
2. Many new purchasers of HP laptops will undoubtedly be trying to connect them to existing older style routers at home (esp if they have legacy Win XP and phone devices) - it would be great if the information on using WAP + AES was better promoted both through the sales channel (PC World here in the UK) and HP during setup - something to think about

Much relieved - I can get some sleep tonight!