Sign in
Microsoft.com
 
Windows Server TechCenter
 
 
 
Windows Server TechCenter > Windows Server Forums > Network Access Protection > Vista 64 bit wireless client times out on server connect when using radius server
Ask a questionAsk a question
Search Forums:
 

AnswerVista 64 bit wireless client times out on server connect when using radius server

  • Monday, June 22, 2009 11:30 PMclarkes Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I have followed the steps  in the practice exercise" Configure WPA-EAP Authentication for a Wireless access Point" in the Microsoft press MCTS 70-642 book chapter 7 to the T. My setup is this :I have a linksys wrt54gs (latest firmware (even tried ddwrt  mega stable version sp1 same thing) router wired in to a vista 64 bit sp2 machine running vmware server 2.0.1 and the virtual machines running on that machine are a Vista Ultimate Edition sp1, and a windows server 2008 enterprise sp1 both are 64 bit. I have the windows server 2008 vm image running as a dc,domain cert,NPS server with RADIUS, and nat. The windows server 2008 is bridged to the ap so that it can work. the vm vista client is configured with a usb wireless nic to hook up to the ap. I am getting a time out error on the vm vista client(it can connect to other wireless networks just not the coorperate wlan I setup) Whenever I try to connect to the dc  wirelessly through my AP, I get Windows vista was unable to connect to the Contoso Network. I click diagnose and it says that the connection timed out. I go to the logs on the DC and and I get whats pasted below.It says to look at more logs, I do and then I can't find anything. How do I fix this? I saw a different post with the same problem but I do not have a vlan setup.http://social.technet.microsoft.com/Forums/en-US/winserverNAP/thread/864b11ff-fcc8-4239-a6bc-1153f3a61248

    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          6/21/2009 11:08:43 PM
    Event ID:      6274
    Task Category: Network Policy Server
    Level:         Information
    Keywords:      Audit Failure
    User:          N/A
    Computer:      Dcsrv1.nwtraders.msft
    Description:
    Network Policy Server discarded the request for a user.

    Contact the Network Policy Server administrator for more information.

    User:
        Security ID:            NWTRADERS\clarkh
        Account Name:            NWTRADERS\clarkh
        Account Domain:            NWTRADERS
        Fully Qualified Account Name:    NWTRADERS\clarkh

    Client Machine:
        Security ID:            NULL SID
        Account Name:            -
        Fully Qualified Account Name:    -
        OS-Version:            -
        Called Station Identifier:        0014bf104c57
        Calling Station Identifier:        001ee5e74bb2

    NAS:
        NAS IPv4 Address:        10.0.0.3
        NAS IPv6 Address:        -
        NAS Identifier:            0014bf104c57
        NAS Port-Type:            Wireless - IEEE 802.11
        NAS Port:            30

    RADIUS Client:
        Client Friendly Name:        linksys
        Client IP Address:            10.0.0.3

    Authentication Details:
        Proxy Policy Name:        Secure Wireless Connections
        Network Policy Name:        Secure Wireless Connections
        Authentication Provider:        Windows
        Authentication Server:        Dcsrv1.nwtraders.msft
        Authentication Type:        EAP
        EAP Type:            -
        Account Session Identifier:        -
        Reason Code:            1
        Reason:                An internal error occurred. Check the system event log for additional information.

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" />
        <EventID>6274</EventID>
        <Version>0</Version>
        <Level>0</Level>
        <Task>12552</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8010000000000000</Keywords>
        <TimeCreated SystemTime="2009-06-22T06:08:43.007Z" />
        <EventRecordID>2517</EventRecordID>
        <Correlation />
        <Execution ProcessID="568" ThreadID="1320" />
        <Channel>Security</Channel>
        <Computer>Dcsrv1.nwtraders.msft</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="SubjectUserSid">S-1-5-21-154703731-3983820093-106904993-1105</Data>
        <Data Name="SubjectUserName">NWTRADERS\clarkh</Data>
        <Data Name="SubjectDomainName">NWTRADERS</Data>
        <Data Name="FullyQualifiedSubjectUserName">NWTRADERS\clarkh</Data>
        <Data Name="SubjectMachineSID">S-1-0-0</Data>
        <Data Name="SubjectMachineName">-</Data>
        <Data Name="FullyQualifiedSubjectMachineName">-</Data>
        <Data Name="MachineInventory">-</Data>
        <Data Name="CalledStationID">0014bf104c57</Data>
        <Data Name="CallingStationID">001ee5e74bb2</Data>
        <Data Name="NASIPv4Address">10.0.0.3</Data>
        <Data Name="NASIPv6Address">-</Data>
        <Data Name="NASIdentifier">0014bf104c57</Data>
        <Data Name="NASPortType">Wireless - IEEE 802.11 </Data>
        <Data Name="NASPort">30</Data>
        <Data Name="ClientName">linksys</Data>
        <Data Name="ClientIPAddress">10.0.0.3</Data>
        <Data Name="ProxyPolicyName">Secure Wireless Connections</Data>
        <Data Name="NetworkPolicyName">Secure Wireless Connections</Data>
        <Data Name="AuthenticationProvider">Windows </Data>
        <Data Name="AuthenticationServer">Dcsrv1.nwtraders.msft</Data>
        <Data Name="AuthenticationType">EAP</Data>
        <Data Name="EAPType">-</Data>
        <Data Name="AccountSessionIdentifier">-</Data>
        <Data Name="ReasonCode">1</Data>
        <Data Name="Reason">An internal error occurred. Check the system event log for additional information. </Data>
      </EventData>
    </Event>
    • Edited byclarkes Monday, June 22, 2009 11:49 PMupdate
    • Edited byclarkes Monday, June 22, 2009 11:47 PM
    •  
     

Answers

  • Sunday, June 28, 2009 11:28 PMGreg LindsayMSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    Since NPS received the request, there doesn't appear to be a connectivity problem between the AP and NPS. The connection timeout on the client is likely caused by the authentication failure. 

    NPS might discard the access request due to improper formatting of the request packet, or it may be a configuration issue. Does the AP have debug capabilities? If so, this may provide a hint as to whether or not NPS is able to read the request from the AP.

    Is the client machine joined to the contoso domain and does it have a computer (client authentication) certificate?

    Thanks,
    -Greg
     

All Replies