X-13 Posted February 15, 2013 Posted February 15, 2013 Our Windows 7 build disk sets the WiFi up on computers with a WiFi connection, but instead of setting it to AES it's defaulting to TKIP. Which means no connection until I've changed it manually. Is there any way of setting the default encryption? The settings, in the RM management console, I have for the defaults don't include what encryption to use, so it defaults to the first option. This is a CC4 network, so a CC4 way of doing it would be handy. But, if I have to do it the proper Windows way I have no problems. [i just need to make a note of what I've done MS style, as opposed to RM style.]
Danp Posted February 15, 2013 Posted February 15, 2013 Might not help, but ours defaults to TKIP too, but that is fine for us 1
SYNACK Posted February 15, 2013 Posted February 15, 2013 Tkip is less secure, heavier on waps as it is usually not hardware accellerated and is more of a hack of 11g rather than fully supported. I don't think it is even supported under n speeds. AES is better to use if at all possible. 1
Michael Posted February 15, 2013 Posted February 15, 2013 Tkip is less secure, heavier on waps as it is usually not hardware accellerated and is more of a hack of 11g rather than fully supported. I don't think it is even supported under n speeds. AES is better to use if at all possible. That's correct. You can only achieve the full 300Mbps using WPA2 AES. I suspect newer wireless standards will drop TKIP all together.
X-13 Posted February 18, 2013 Author Posted February 18, 2013 (edited) Have a look here I have a question, If I were to strip out all the SSID and key information, would it still work? We have a way of pushing out all of that, it's just the encryption what we can't control. WIRELESS 574952454C455353 WIRELESS WPA2PSK AES false Like that. [With a few school specific changes.] Edited February 18, 2013 by X-13
Michael Posted February 18, 2013 Posted February 18, 2013 As far as I'm aware you'd need to leave the file 'as is'. If your wireless network isn't called WIRELESS, you'll need to manually add a Win 7 workstation to your wireless network then export the information. This is because is based on your SSID name.
X-13 Posted February 18, 2013 Author Posted February 18, 2013 As far as I'm aware you'd need to leave the file 'as is'. If your wireless network isn't called WIRELESS, you'll need to manually add a Win 7 workstation to your wireless network then export the information. This is because is based on your SSID name. That was one of the changes I was going to make. I was thinking, if the SSID and hex are the same it would just merge the two. I don't really want something floating about with our key in plain text...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now