Getting Connected

• Getting Connected Services
• uNID and Password
• Password Synchronization
• Computer Labs
• Campus Modems
• Department DSL
• VPN Connections
• Campus Wireless Services
• Services Home
• OIT Home

Wireless Client Instructions

SecureW2 Client Installation for Windows Vista

This information is posted as a courtesy only - Vista is NOT currently supported by the Campus Help Desk. Please refer to Microsoft with questions.

Note: we hope to get the uconnect.utah.edu wireless network working for Vista without any required client software soon (summer 2007).

1. Download the FINAL version of SecureW2 3.2.0 for Vista (as of April 21st) at the following website:  http://www.securew2.org/ or direct download URL:  http://www.securew2.org/resources/SecureW2_TTLS_320_VISTA.zip . 
2. Make sure to uninstall any previous versions of SecureW2 first.
3. Install the SecureW2 beta client.  There may not be a prompt to enter user information, as was the case in previous versions of SecureW2,  prior to being prompted to restart the machine to finish installation. 

    

   

    

   
   

4. After rebooting, look at the notification area on your toolbar for any wireless signal.

    

    

   1. Then click on Wireless Connections (or optionally go straight to Network and Sharing Center).

    

   

5. There is no automatic wireless connection.  Click on Connect to a network and continue to look for any available networks broadcasting an SSID.
   
   

    

   Networks with a yellow “!” are unsecured networks.  Networks without the "!" require not only authentication, but encryption and radio type (SSID).  When connecting to any of the unsecured networks, you will likely still be unable to connect.  The network will have to be manually put into the network configurations, even though the laptop running Vista can see SSIDs being broadcast.  This is a Vista security measure to prevent malicious listeners from exploiting the wireless client. See http://www.microsoft.com/technet/itsolutions/network/evaluate/hiddennet.mspx for more information.

6. Select a connection.  If and when the connection fails, the user will have to create the connection manually.  Then click on the Set up a connection or network. 
7. Creat a network with the exact SAME SSID. 
8. Next, enter the wireless network information into the fields being asked for:

    

   

    

   

    

   

    

   

   1. Click on Settings, then click Configure under the DEFAULT Profile:

    

    
   

   1. Uncheck Use alternate outer identity.
   2. Under the Certificates tab, uncheck Verify server certificate. 
      Note: Vista mandates certificate validation.  The alternate solution to this is to manually install UofU’s CA into the certificate store under Trusted Root & Persons & Enterprise & etc.

    

    

    

   1. Next, leave PAP in the Select Authentication Method field.
      

    
   

   1. Under the User account tab, enter your uNID, password and the utah.edu domain:

    

    
   

   1. Then click on OK.  This prompts the following window again:

    

    
   

   1. Then connect to the wireless network or network SSID you just created:

    

    
   

   1. Click Next, and the connection will be confirmed.  It may take a few seconds for the Network and Sharing panel to identify the network and show the Connected status.

    

       

Your computer should now be configured with the Final SecureW2 client to authenticate to the uconnect.utah.edu network.

SecureW2 Client for Vista - Troubleshooting

• It’s important to understand that Microsoft has built into Vista a security feature that, should the wireless client go into hibernation, or the client lose it’s connectivity… the connection may or will not be automatically re-connected.  Microsoft’s tech-notes indicate that auto-connect would force the wireless client to broadcast and listen for the SSID.  Their solution is to have the wireless user log off, and then log on again or possibly reboot the machine.  Microsoft’s tech-notes also indicate that in some situations, depending on wireless security settings, the user may have to delete and create the SSID each and every time the attempt to connect to the “Private” or authenticating wireless network is made.
• The instructions above will help get you around Vista’s mandatory certificate installation through its certification authority and root authority.  Also, you can go into the run command in the Start menu, and go directly to the certificate store by typing in “certmgr.msc” here you will find all of your installed certificates.  To get Vista to accept or install or import certificates that are being denied or not accepted, you will have to locate the afore mentioned certificate in the store, and copy or install it into the “Trusted Root Certification Authorites/Certificates” and any other directory you feel is necessary in the Certificate management console.  
• Certificate installation on Vista Home and Vista Business (upgrade) requires special instructions.  The default method of SecureW2 certificate installation fails on (at least) these 2 Vista products.