I've been having continuing problems with Windows 7 apparently trashing the network (as shown in Wireless Event Viewer) and then disconnecting. The Wireless Event Viewer entry is "Security mismatch with 11n. 11n is not in operation." I guess Windows 7 is resetting the cable gateway. I have to unplug power, wait, and then plug it back in.
What does "Security mismatch with 11n" mean? How do I troubleshoot it? The driver has about 1-million settings, but no help. Is there documentation anywhere?
I am able to connect to the Internet, and to my cable gateway (as administrator), and to my LAN server most of the time. Then, for no apparent reason, Windows 7 starts thrashing the network. I can't imagine to what security the Wireless Event Viewer is referring.
I'm an electrical engineer. While I lived & worked in San Jose, among other things, I designed wireless network hardware.
There could be many reasons as to why you would get this error message. We understand you are using Winodws 7*, correct?
Is your computer a laptop or a desktop?
What Intel(R) Wireless Adapter do you have installed?
Is this adapter the original one installed by factory?
When you say you connect most of the time, you mean that sometimes you can't connect at all?
Under what cisrcumstances you noticed you can't connect?
Does this happen only with your home network or any other regardless?
Thanks for your reply...
Windows 7 Home Premium 64-bit. I had no problems when I ran WinXP.
Lenovo V570 laptop.
WiFi Adapter: Centrino 6150, factory installed.
I can connect. When I do, I run Intel Wireless Event Viewer before anything else. Then I launch Total Commander, TextPad, & my Linux Virtual Machine (VBox). I contact the Internet in the VM. I don't allow Windows on the net -- too dangerous -- except for online banking and Windows updates. All else I keep in the VM.
Intel Wireless Event Viewer will go along for hours without showing anything at all -- no entries. Then, for no apparent reason, it will start thrashing the network, adding 8 or 9 Event entries every 3 seconds. Eventually, I lose connectivity and must reset my cable modem. My ISP is not the trouble. Renewing my IP lease is not the trouble. The trouble seems to be coming from inside Windows. I think there's some sort of conflict between the Intel Proset and Windows.
I use my laptop only at home.
I chatted with an Intel tech. I then downloaded the new version of Intel Driver Update Utility and ran it -- it is v.2.2 and mine was v.2.0 -- apparently, the Intel Driver Update Utility doesn't keep itself updated.
I reloaded everything that the Intel Driver Update Utility downloaded. My existing drivers were up to date (no change), but I overloaded them anyway.
So far so good. It's been a few hours and the Wireless Event Viewer has nothing to say. That's good.
I notice that security now defaults to WPA2 Personal. I used to have Intel - WPA2/PSK - 802.11w. I'm glad there are choices. I wish there was 'Help' so I could read about what the choices mean and how to use them.
Everything was happiness for a couple of days. There were no entries in Wireless Event Viewer. I got no network notices from the task tray.
But now the pattern of errors is starting all over again.
Is anyone interested in helping me?
I had Wireless Event Viewer configured as follows:
File > Settings... > General (tab) > [x]Enable Wireless Event Logging.
File > Settings... > Driver Log(tab) > [x]Enable Driver Event Logging.
File > Settings... > Driver Log(tab) > [x]Standard logging.
File > Settings... > Driver Log(tab) > [x]Troubleshooting logging.
I got NO entries in Wireless Event Viewer.
But as soon as I did this:
Run Intel PROSet/Wireless WiFi Connection Utility.
Advanced > Advanced Statistics > Logging >[_Start_Logging_] (button).
In Wireless Event Viewer,
I immediately got the following:
A Warning: "The given profile already exists in the database,"
followed by 3 Information lines,
followed by 4 Success lines,
followed by 2 Information lines,
followed by 5 Success lines,
followed by 1 Information line,
followed by 2 Success lines,
followed by Warning: "Security mismatch with 11n. 11n is not in operation",
followed by Warning: "Security mismatch with 11n. 11n is not in operation".
All that took 2 seconds.
1-and-a-half minutes latter, I got
Error: "Did not receive an IP address from DHCP server".
A half minute later, I got
Error: "One or more given parameters are invalid!"
I also received a task tray notice that there was a network problem, but when I responded to the notice, there was no problem. I'm used to getting those (apparently bogus) notices. That's how all this started almost a year ago.
These are the errors I'm getting (again... sigh... after reloading the driver and being "clean" for a whole day):
# 1 is what this thread is about.
# 2 is mysterious because my LAN uses only fixed IP.
# 3 is mysterious because my LAN (and Internet) work and the WPA2-PSK is correct and matches what the cable gateway expects (otherwise, the cable gateway's WiFi would not let me through). I logged into the cable gateway (192.168.0.1) and confirmed.
# 4 is mysterious because I don't know what an "administrator profile" is. A socket expects to get an IP address. What an "administrator profile" is, I don't know. Is Intel simply afraid to use the term "socket" so it says: "administrator profile"? How much can Intel dumb-down networking?
I just discovered 2 really strange things:
1, The driver keeps turning on "Connect to a more preferred network if available"? I keep turning it off, but when I open my cable gateway's connection properties, it's selected ([x]) again.
2, Somehow PROSet changed my cable gateway's
Wireless Network Properties > Security (tab) > Security type
from "WPA2 Personal"
to "Intel - WPA2/PSK - 802.11w".
I'm changing it back right now. I'll come back in a day or two to report whether it worked.
I keep getting task tray notices that there's a connection problem, but when I click it, the Intel Wireless Troubleshooter that comes up says: "Currently there are no issues reported." In "History" (bottom of Intel Wireless Troubleshooter page) it says "An administrator profile failed to obtain an IP address from the DHCP server." Like I wrote previously, I don't know what an "administrator profile" is, and my LAN is all hard wired with fixed IPs.
WiFi (192.168.0.2) Status > Details... > DHCP Enabled = 'No'.
I don't know how to change this.
(It shouldn't make any difference because all LAN hosts are fixed IP, but this is frustrating.)
When I'm in Intel PROSet/Wireless WiFi Connection Utility and I click "Profiles..." and I select "NSA monitor" (which is the name of my cable gateway) and I click "Properties..." (opens 'WiFi Profile Properties - NSA monitor") and I click "OK" (closes 'WiFi Profile Properties - NSA monitor"), look what happens.
For what it's worth, here's the log file (...don't know what 90% of this stuff is, and it doesn't seem to match the above ...confusing...)
Thank you, GN. Experience seemed to be propelling me to that point of view also. It seemed that my problems were being manufactured inside my computer, not in the cable gateway & not by my cable company (Time Warner). I naturally assumed that the more Intel software I enabled, the better my condition. I blamed Microsoft and Windows 7. I will entertain the notion that Intel may be to blame.
I will uninstall PROSet and report my experiences back here.
On what do you base your conclusion that PROSet is at fault? Is it based on engineering knowledge or user experience?
I uninstalled PROSet and the world didn't end...
GN (or anyone)...
Now that I'm not running PROSet, I have nothing with which to monitor the network. Do you know of a tool that will monitor, record, & report the activity of the networking drivers, sockets, & protocol stacks? Perhaps something in SysInternals?
I feel that I'm flying blind.
FWIW, here's the details of my LAN:
192.168.0.1 = cable gateway (WiFi & Ethernet internally bridged),
192.168.0.2 = laptop WIFi adapter,
192.168.0.3 = laptop Ethernet adapter,
192.168.0.10 = VirtualBox virtual WiFi adapter,
192.168.0.11 = VirtualBox virtual Ethernet adapter,
192.168.0.100 = ClarkConnect (RedHat+Apache) server Ethernet adapter,
192.168.0.101 = home theater WiFi adapter.
All adapters have static IPs.
Windows WiFi is configured as Internet Zone. There is no Private Zone. There is no Domain. Hence, there is no network discovery. There is no sharing. The VirtualBox virtual adapters & the laptop's real adapters are bridged by a VirtualBox bridge driver.