Unable to connect to company wireless network after Win7 upgrade

Anonymous
2009-11-06T21:58:16+00:00

My company network does not broadcast the SSID, so on Vista I used to manually setup the connection.  However with Win7 64 I keep getting an error that "An unexpected error has occurred"

Dell xpsM1330

Intel WiFi Link 4965AGN

Any help would be appreciated.

Windows for home | Previous Windows versions | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2010-10-20T22:17:06+00:00

Ok, let's see if we can keep this active and get to a fix...

Got an MS POC to give me some info that may help....

I've experienced what many above have, that while I can connect to most wireless networks, including my home wpa2, any time I tried to make a connection my corporate wpa2-enterprise network, no go, and had the errors in the event log. also similar failures whenever I'd try to create any wireless profile manually using wpa-enterprise or wpa2-enterprise.

Note mine was also a machine that got USMT data migrated, and I have a feeling it was responsible for migrating the keys below...

So here was the final fix, and maybe you guys can verify if it's the only thing needed as I'd tried various other things to no avail, but this was the "last" change I made that got things working...

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RasMan\PPP\EAP

under here are a number of subkeys with different numeric values....

while I can't tell you specifically what to look for, in my case I noted there was one key pointing at what I'd expect, a ras related key in the windows\system32 dir. however, I also had three other keys pointing to files related to Symantec, which I did not have on my newly built machine.

So I exported keys from a newly built machine, that actually had symantec. it had four keys under EAP, but only one, the last one, was related to Symantec, all others pointed to files in system32.

I imported those keys into my broken machine, deleted the one key that was related to symantec, and without even having to reboot...all was fixed...

so....here's my suggestion, and I hope if this works everyone can feedback so we have more info on if it's the order of the keys or just the presence of bad entries...but I would suggest, starting off by looking at your keys under EAP, and seeing if there's anything referencing dll files that may not exist on your machine.

if you do have these keys, either delete the key, or try to put the file back in place thats being referenced, assuming it's missing.

we'll be doing some more testing internally, so I'll feed back if we have any additional findings.

good luck.

Was this answer helpful?

10+ people found this answer helpful.
0 comments No comments

49 additional answers

Sort by: Oldest
  1. Anonymous
    2009-11-07T21:19:22+00:00

    Hi jestevenson,

    Thank you for posting in Microsoft Answers Community Forums.

    Step 1:

    I would suggest you to please reconfigure your Router by running the setup wizard from CD/DVD which came along with it to eliminate any mismatch between your Network Connection and the Router.

    If you can access the router setup pages I suggest you to get the network settings from you Company Network Administrator.

    Next, delete the present network settings and set up again with new settings you recently obtained.

    Step 2:

    To work around this problem, reregister the Netshell.dll file. To do so, follow these steps:

    1. Click Start, and then click Run.
    2. In the Open box, type regsvr32 %systemroot%\system32\netshell.dll, and then click OK.
    3. In the RegSvr32 dialog box, click OK.

    Test to see if you can open the properties of the network connection in the Network Connections folder.

    If the issue is resolved, you do not have to follow the remaining steps in this article. If the issue persists, and you receive the error message that is mentioned in the “Symptoms” section of this article, follow these steps:

    1. Click Start, and then click Run.
    2. In the Open box, type regsvr32 %systemroot%\system32\ole32.dll, and then click OK.
    3. In the RegSvr32 dialog box, click OK.
    4. Restart the computer.

    Hope this information helped you. 

    Regards,

    Yaaser - Microsoft Support Engineer

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2009-11-16T16:25:26+00:00

    Yasser,

    Thank you for the response.  Unfortunately this is a corporate network so I am not able to access the router setup pages.  The official OS that we are supposed to be running is XP so I don't get much IT support.  I had been running Vista previously and was able to connect no problem after updating to SP2.  However once I moved to Win7 I have not been able to connect via wireless.

    I followed the procedure that you outlined in step 2.  I still get the same error.

    When trying to connect I do the following

    • go to "Network and Sharing Center"
    • Click setup a new connection or network
    • select Manually connect to a wireless network
    • enter in the SSID, security type and encryption time, check the boxes to connect automatically and connect even if not broadcasting
    • click next
    • Right away I get "An unexpected error occurred".  i.e. it is not even trying anything.

    However after doing what you described I do see the SSID of my company's network in the available networks list.  The first time I try to connect it states that it is taking a unexpected amount of time to connect and then eventually gives up, on subsequent attempts it just says "Windows was unable to connect to <name>" where <name> is the SSID of the network.

    Another thing I tried was to go into the "Manage wireless networks" window.

    In here if I try the same steps as above I get the same error.  However if I set it up as a WEP network just to get it added and then go back in and try to adjust the properties I can see another problem.  Basically I go into the properties, select the security tab, then change the security type to WPA2-Enterprise, encryption type to AES, however the "Choose a network authentication method:" dropdown is blank and when I click OK I get an error that states "Error Saving Wireless Profile.  Windows has encountered an error saving the wireless profile.  Specific error.  The profile has an invalid length field."

    Something seems to be messed up with setting up WPA networks.

    Regards,

    John

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2009-11-20T05:08:36+00:00

    Jestevenson,

    The majority of connection problems within Windows 7 have been solved by installing the latest driver for the network adapter obtained from the manufacturer.  Try to download Windows 7 compatible drivers if the manufacturer provides them. If not, try Windows Vista drivers and contact your OEM for any update on the driver.  

    Make use of the Compatibility Center and Upgrade Advisor to see if your hardware is compatible or requires a download:

    Check compatibility for thousands of devices and software, get downloads and leave feedback

    o     5,000 software programs and 10,000 devices listed at launch and growing

    o     Check compatibility for both 32-bit and 64-bit Windows 7

    o     Easily find products that have earned the “Compatible with Windows 7” logo

    o     Download drivers and software updates from partner websites

    o     Vote and leave feedback on compatibility

    o     Read the FAQ’sfor more details


    Cody C

    Microsoft Answers Support Engineer

    Visit our Microsoft Answers Feedback Forum and let us know what you think.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2009-11-23T20:59:41+00:00

    Cody,

    My wireless card is an Intel 4965AGN.  I installed what I believe the latest drivers are from Intel.  V13.0.0.107 (9/15/2009).  Windows updates does not find a newer driver (nor does checking directly from the driver properties.  I have also run the automatic driver update utility from intel: http://www.intel.com/support/detect.htm  It tells me that my driver is current.

    I am able to connect to non-WPA networks fine.  Just my corporate WPA2 network is a problem.

    When I run the Upgrade Advisor it gives me the following information (green checkmark)

    Intel(R) Wireless WiFi Link 4965AGN

    Intel Corporation

    Regards,

    John

    Compatible

    This device is compatible with Windows 7.

    Was this answer helpful?

    0 comments No comments