+ Post New Thread
Results 1 to 8 of 8
Windows 7 Thread, AES > TKIP in Technical; Our Windows 7 build disk sets the WiFi up on computers with a WiFi connection, but instead of setting it ...
  1. #1

    X-13's Avatar
    Join Date
    Jan 2011
    Location
    /dev/null
    Posts
    8,020
    Thank Post
    508
    Thanked 1,591 Times in 1,122 Posts
    Blog Entries
    19
    Rep Power
    700

    AES > TKIP

    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.]

  2. #2

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    8,943
    Thank Post
    232
    Thanked 1,512 Times in 1,206 Posts
    Rep Power
    328
    Have a look here

  3. Thanks to Michael from:

    X-13 (15th February 2013)

  4. #3
    Danp's Avatar
    Join Date
    Jul 2011
    Posts
    1,284
    Thank Post
    58
    Thanked 147 Times in 130 Posts
    Rep Power
    107
    Might not help, but ours defaults to TKIP too, but that is fine for us

  5. Thanks to Danp from:

    X-13 (15th February 2013)

  6. #4

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    10,707
    Thank Post
    829
    Thanked 2,571 Times in 2,188 Posts
    Blog Entries
    9
    Rep Power
    731
    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.

  7. Thanks to SYNACK from:

    X-13 (15th February 2013)

  8. #5

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    8,943
    Thank Post
    232
    Thanked 1,512 Times in 1,206 Posts
    Rep Power
    328
    Quote Originally Posted by SYNACK View Post
    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.

  9. #6

    X-13's Avatar
    Join Date
    Jan 2011
    Location
    /dev/null
    Posts
    8,020
    Thank Post
    508
    Thanked 1,591 Times in 1,122 Posts
    Blog Entries
    19
    Rep Power
    700
    Quote Originally Posted by Michael View Post
    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.

    Code:
    <?xml version="1.0"?>
    <WLANProfile xmlns="http://www.microsoft.com/networking/WLAN/profile/v1">
    	<name>WIRELESS</name>
    	<SSIDConfig>
    		<SSID>
    			<hex>574952454C455353</hex>
    			<name>WIRELESS</name>
    		</SSID>
    	</SSIDConfig>
    	<MSM>
    		<security>
    			<authEncryption>
    				<authentication>WPA2PSK</authentication>
    				<encryption>AES</encryption>
    				<useOneX>false</useOneX>
    			</authEncryption>
    		</security>
    	</MSM>
    </WLANProfile>
    Like that. [With a few school specific changes.]
    Last edited by X-13; 18th February 2013 at 08:42 AM.

  10. #7

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    8,943
    Thank Post
    232
    Thanked 1,512 Times in 1,206 Posts
    Rep Power
    328
    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 <hex> is based on your SSID name.

  11. #8

    X-13's Avatar
    Join Date
    Jan 2011
    Location
    /dev/null
    Posts
    8,020
    Thank Post
    508
    Thanked 1,591 Times in 1,122 Posts
    Blog Entries
    19
    Rep Power
    700
    Quote Originally Posted by Michael View Post
    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 <hex> 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...

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 1
    Last Post: 17th February 2009, 11:06 PM
  2. Set Your Video - Nissan GT-R vs Japanese Bullet Train
    By SYSMAN_MK in forum General Chat
    Replies: 15
    Last Post: 14th July 2008, 02:53 PM
  3. Nvidia Model codes - whats best? GS/GTS/GT
    By j17sparky in forum Hardware
    Replies: 21
    Last Post: 4th December 2007, 01:02 PM
  4. WPA, TKIP, MS-CHAPv2 and Vista
    By Psymon in forum Windows
    Replies: 6
    Last Post: 17th September 2007, 09:25 AM
  5. wireless card for domain with wpa-tkip
    By strawberry in forum Wireless Networks
    Replies: 3
    Last Post: 30th August 2007, 02:06 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •