Hello,

I just upgrade my laptop to Win8, it can't connect to RB2011's wifi, but before upgrade is no problem, any one got the same problem??
My laptop is using Atheros AR9287

Thanks
Alan

Does the Windows 8 machine see the Access Point? If yes, when you attempt to connect, what are the log entries in RouterOS log?

Hi Normis,

In win8 it can see the access point, after I input the WPA2(tried use WPA1 instead it, same result) key, after around 20-30 seconds, win8 show can't connect, I checked the windows event, the message is the AP no response, I tried turn on debug on RB2011, then no any log message show when win8 connect.

Then I restored to win7 everything is OK. So should be not hardware problem, just don't know is win8 problem or not compatible.

Thanks
Alan

PS: if need more information, I can install win8 again to test on weekend, just let me know ^_^

was it working with win7 ?
If yes it looks to me like Win8 driver bug.
Which wlan device do you have?
Do you use wlandrivers from vendor, or inbox drivers from microsoft?
Did you try Win7 drivers.
Perhaps boot ubuntu live image and see if wlan is working with linux in general.

br cm

It is no problem on Win7, only got problem on win8, tried win8 built-in driver and updated to Atheros V10.0.0.75_21 got same result. The wifi on notebook is Atheros AR9287.

Alan

There is no log message on connect, I enabled the debug to memory. So don't know is what happening.

It means that it is not even attempting to talk to the router

Some new finding, I turn off the RB2011's wifi and turn my old TP-Link 1043ND, it can connect without any problem, but I switch back to RB2011's wifi, can't connect.
The SSID, WPA2's key, ciphers is same

New finding, if I change the channel width to 20/40MHz HT Below, it can connect, but before using 20/40MHz HT Above is no any problem on Win7

confirm the problem with wireless on RB-751U-2HND and windows 8
switching from above to below helped
ROS 5.22, downgraded to 5.21 and then found that post.

i have a similar issue.
htc 8x will not connect to my rb751g-2hnd, ros 5.20, wpa2-psk aes

@nosovk
so in your experience:
ros 5.21 works
ros 5.22 does not work ?

just upgraded routeros 5.20 -> 5.23, with the same settings on both ap and client, the htc win8 phones started connecting.

Thought i'd add to this topic...

I too have a Win 7 x64 client that cannot connect to the hidden SSID on the RB2011. I'm running ROS 6.1

Seems like a driver/configuration issue to me because on the same hardware, running Ubuntu, the client was able to connect fine.

I found this, do you guys think the problem could be with something similar?

Windows 8 may encounter a problem when trying to connect to the Cisco Unified Wireless Network. If the client is using WPA or WPA2 key management with AES encryption, then the connection may fail. With "debug client" in effect on the Wireless LAN Controller, a message similar to the following is seen:



*dot1xMsgTask: Jun 12 20:23:37.471: 00:11:22:33:44:55 Retransmit failure for
EAPOL-Key M1 to mobile 00:11:22:33:44:55, retransmit count 5, mscb deauth count 0




Windows 8 supports IEEE 802.11w (2009) natively in the OS. The Client implementation complies with IEEE 802.11w specification. All Windows 8 certified WLAN miniport drivers are required to support IEEE 802.11w through Windows Hardware Certification program. When Windows 8 clients attempt to connect to Cisco’s MFP capable APs, the connection fails. This failure is the result of an interoperability issue between Windows 8 IEEE 802.11w implementation and Cisco’s MFP implementation on their APs. The AP doesn’t report the correct “Key Descriptor version” for M1 in 4 way handshake. The client drops the unexpected M1 and thus the 4 way handshake fails. Legacy clients that don’t support 802.11w do not have this issue.

Source https://support.microsoft.com/kb/2749073

Please removed as soon as possible from that horrible OS, this problem is an example, test any version of linux and forget about these problems.
cetalfio

Please removed as soon as possible from that horrible OS, this problem is an example, test any version of linux and forget about these problems.
cetalfio

I agree ... this is not a mikrotik issue but a micro$oft issue ...

JF

for anyone that have windows phone 8 or windows 8,this solved my problem.There is a security issue in negotiation.I managed radio signal but after that unable to connect.When i changed security profile everything worked just fine.

I have the same issue with Win8.1 x64 using atheros AR9382 with latest drivers from atheros.cz. This notebook cannot connect to my rb2011uas-2hnd-in using the same security profile as in post above. This is a shame as I have no issue connectin to number of other APs, including some other mikrotik APs with WP2-enetriprise at my work. Should this be issue in driver or in windows 8.1, it would surely prevent me from connecting to some other networks as well, so far, the only problem is with RB2011

I have at work also a problem with a new dell laptop with a intel wirless chipset, it doen't see the 2nd SSID (the first SSID is also a virtual SSID)

Windows 8 and 8.1 have removed from GUI the support for WPA and TKIP.

if you not see some fields described above, you must click on button "advance settings" on wireless tab.

The wlan must be configured like that for works on Windows 8.x:

band=2ghz-b/g (b/g only for compatibility with all devices can not recognize 802.11n, or 2ghz-b/g/n if not matter)
channel-width=20mhz not all the 802.11n devices support 20MHz + 20MHz channels!!!
bridge-mode=disabled
country=italy (your country, but THIS MUST BE SET also on Windows / Device Manager / WiFi Properties /etc.)
frequency=2437 (one frequency in both windows driver and on routerboard)

If the routerboard wlan1 are dual chain (and both antenna presents):
ht-rxchains=0,1
ht-txchains=0,1

max-station-count=30 (I do not think you link 2007 devices on this access point)
mode=ap-bridge
radio-name=MATRIX (one SSD all UPPERCASE, you can use only A-Z 0-9 and "-" for compatibility with all devices)
security-profile=your-profile-name
wireless-protocol=802.11 MUST BE SET 802.11!!!

adaptive-noise-immunity=none the other devices not support this options! leave to none
compression=no the other devices not support this options! leave to no
hw-protection-mode=none the other devices not support this options! leave to none
hw-retries=7
preamble-mode=both the other devices not support this options! leave to both
rate-set=default the other devices not support this options! leave to default
wds-mode=disabled the other devices not support this options! leave to disable
wmm-support=disabled the other devices not support this options! leave to disable

for security-profiles
name=what-you-want-as-profile-name
mode=dynamic-keys
authentication-types=wpa2-psk only
wpa2-pre-shared-key=yourpassword
unicast-ciphers=aes-ccm only
group-ciphers=aes-ccm only
group-key-update=5m
management-protection=disabled


If you need than old devices access add one VirtualAP configured identical than SSID must be different, like "MATRIX-WPA"
and use another security profile like this:
name=what-you-want-as-another-profile-name
mode=dynamic-keys
authentication-types=wpa-psk only
wpa-pre-shared-key=yourpassword
unicast-ciphers=tkip only
group-ciphers=tkip only
management-protection=disabled

I fixed this problem myself by changing the Channel Width from 20/40Mhz HT Above to 20/40MHz HT Below. Windows doesn't like "Above"

I know this is a old post, but in case anyone else struggles with the same issue on windows 10, I had to change this setting:



This is strange though, since my windows has ALWAYS worked and just suddenly stopped.