Windows WPA Client does not Install in Server 2003 or SBS Server 2003

Discussion in 'Windows Networking' started by John Holmblad, Dec 28, 2003.

  1. Despite the claimed (or at least strongly implied in KB
    article 815485) compatibility of the Windows WPA Client
    with Windows Server 2003 and, presumably with Windows
    Small Business Server 2003, it does not install properly.
    The error message when attempting to perform the
    installation says in effect that the version of the OS is
    incompatible with the update. The update to which I am
    referring can be found at the follwing URL at Microsoft
    www site:

    The file in question is named: Q815485_WXP_SP2_x86_ENU.exe

    Does anyone know where the correct WPA update can be
    located that works with W2K3 Server or SBS 2K3 Server?
    Any help on this matter would be much appreciated.
    John Holmblad, Dec 28, 2003
    1. Advertisements

  2. Hi,

    I was able to start setup by saving the file, and setting XP compatibility
    on the EXE

    --Jonathan Maltz [Microsoft MVP - Windows Server] - A Windows Server 2003 visual, step-by-step
    tutorial site :)
    Only reply by newsgroup. Any emails I have not authorized are deleted
    before I see them.
    Jonathan Maltz [MS-MVP], Dec 28, 2003
    1. Advertisements

  3. Jonathan,

    thanks for your quick response. Let me however clarify my
    original remarks/issue. The .exe in question DOES install
    properly on a Windows XP system and I have done so.
    HOWEVER when I attempt to install it on Windows Server
    2003 Enterprise Edition or Windows SBS 2003 Premium
    Edition it fails to install. I will try what you suggest.
    I suspect that, despite, what the Microsoft KB article
    asserts, this .exe is NOT compatible with the Windows
    2003 server family.

    John Holmblad, Dec 29, 2003
  4. That was what I meant to say, sorry. On Windows Server 2003 I set XP
    compatibility on the install file, and it didn't prompt me with it being the
    wrong OS

    --Jonathan Maltz [Microsoft MVP - Windows Server] - A Windows Server 2003 visual, step-by-step
    tutorial site :)
    Only reply by newsgroup. Any emails I have not authorized are deleted
    before I see them.

    Jonathan Maltz [MS-MVP], Dec 30, 2003
  5. John Holmblad

    Guest Guest


    ouch! on both W2K3ES and WSBS2K3PE, as you suggested, I
    set the windows compatibility mode to WXP on the Q815485
    exe file but the install now fails because it thinks I
    need SP 1 installed despite the fact that there IS NO SP1
    for either OS yet. FURTHERMORE when I went to Windows
    Update just to double check that SP1 is not yet out for
    the Server 2003 family, I got the following error from
    the Windows Update Service after it aborts the scan of my
    system for rev level information:
    Guest, Dec 31, 2003
  6. Hrm.....Depending on your deadline, you may want to contact the NIC's
    manufacturers and ask if/when they will have 2003 WPA drivers. I know 2003
    is capable of WPA with the proper drivers in place...

    Not sure what happened to your WU, if the update patch failed then it
    shouldn't have modified anything at all

    Using the supplied drivers with the NICs you may or may not get 2003
    support, usually the cards will have up-to-XP drivers. In personal
    experience these should work (usually) on 2003, but there's no guarantee
    since the drivers never claimed 2003 was compatible. Also remember that
    non-2003 drivers can cause a general instability

    --Jonathan Maltz [Microsoft MVP - Windows Server] - A Windows Server 2003 visual, step-by-step
    tutorial site :)
    Only reply by newsgroup. Any emails I have not authorized are deleted
    before I see them.

    Jonathan Maltz [MS-MVP], Dec 31, 2003
  7. Jonathan,

    After I rebooted the 2k3 systems a second time the
    problem with Windows update failing cleared itself up.
    The 802.11 drivers in question which I am using are from
    Linksys and Netgear respectively and they are the very
    latest ones available from those companies. The Linksys
    driver works fine on Windows XP which is the second boot
    option on the system that also has W2K3 ES on it.

    Somehow I don't think it is the 802.11 drivers that are
    the issue. To rule this out however I will uninstall the
    Netgear driver on the system running SBS 2K3PE and
    attempting the install of the WPA update for Windows.
    Perhaps there are some other difference between the
    systems I am using and whatever system on which you ran
    your install of this update which result in the different

    I will let you know how it goes.

    Thanks for your help.
    John Holmblad, Jan 1, 2004
  8. I actually only mentioned the driver issue because you said "if I ever get
    their programs to work". I was just noting that the drivers may not be 2003

    Oh, and by the way, sorry! I just did try that patch on a regular 2003
    machine and got the service pack error. I'm going to see if I can conjure
    up a better answer for WPA support in 2003

    --Jonathan Maltz [Microsoft MVP - Windows Server] - A Windows Server 2003 visual, step-by-step
    tutorial site :)
    Only reply by newsgroup. Any emails I have not authorized are deleted
    before I see them.

    Jonathan Maltz [MS-MVP], Jan 2, 2004
  9. John Holmblad

    Robert Guest

    If anyone has come up with a fix for this, I'm in the same boat. I'm
    using a LinkSys AP. I have two clients, a Windows XP laptop using an
    802.11g pccard and a Windows Server 2003 using an 802.11g nic. Looking
    at the Wireless Network Connection's Wireless network properties
    dialogs side-by-side I see that on XP I have a Network Authentication
    drop down that allows me to select WPA-PSK. On 2003 I don't have that
    dropdown. WEP seems my only choice. System all works great on WEP.

    I just learned about WPA and am trying to switch my home network to
    this system. I got the laptop switched no problem (WPA w/ TKIP). But
    the 2003 server seems clueless.

    I went down the same rabbit hole discussed here. Found the WPA patch.
    The KB article said it was appropriate for Windows 2003 (sort of), but
    then the patch download page says it's just for XP. Sure enough, it
    won't install on 2003. I'm hesitant to try to fool 2003 into thinking
    this patch is kosher by messing with the compatibility settings.

    I have the latest and greatest firmware and drivers on the NIC and AP.

    This 2003 server is a native 2003 domain controller, DNS and WINS
    server if that makes any difference. I have alos been messing with
    GPOs and AD in general so I suppose it's possible that I messed up
    something or locked myself out of something. I'm using this box to
    study for upgrading my 2000 MCSE to 2003.

    I do have a general clue about all this stuff works, but I seem to
    have hit a wall here. I've come to the inconceivable conclusion that
    Windows Server 2003 just doesn't support WPA. But that can't be right.
    Help. Thanks.

    Robert, Jan 6, 2004
  10. Robert,

    Thanks for your post on this subject.

    I have reached the same conclusion as you have. I was
    hoping that a Microsoft employee lurking on this list
    would validate that conclusion but so far that does not
    seem to be the case.

    I will say that I WAS able to get one of my server based
    systems, which runs Windows 2000 Advanced Server, to work
    in WPA-Pre SharedKey mode by using the Proxim Orinoco
    a/b/g Card client utility that I istalled on that system.

    The Server 2003 EE system to which I referred in my
    previous posts is configured with the Linksys Wireless G
    card. As you know the drivers clearly work with that OS
    but I have not tried to install the Linksys client
    utility on that system. If I get a chance after today I
    will try to install the Linksys client utility on the
    Server 2003 EE system and see if it will work correctly
    (see comment in the next paragraph for my motivation for
    attempting this).

    The SBS 2003 PE sysem to which I referred in my previous
    posts is configured with the Negtear WAG511 a/b/g card.
    On this system I DID install the client utility in
    addition to the drivers, but I cannot seem to get it to
    activate in other thatn a "view status only" kind of mode
    even when I turn off the "use Windows to configure my
    wireless settings" check box. I was hoping that by this
    means I could enable a workaround for the fact that the
    Windows WPA client does not seem to install on the Server
    2003 OS's.

    Although Windows XP, and the Server 2003 product family
    share an overlapping code base, clearly there are
    differences that cause problems, and of course, I have
    not seen ANY wireless card supplier explicitly indicate
    that they positively support the Server 2003 family of
    OS's. In that respect then we are lucky that these cards
    work as well as they do.

    I am in the final day of preparing a paper on all this
    wireless security arcania so if you are interested in
    getting a copy just let me know via this list and I will
    send it to your hotmail email address.

    John Holmblad
    john Holmblad, Jan 6, 2004
  11. Robert,

    I have been away from this thread for several days and I
    just got your response. I will send you a PDF (~3mbytes)
    of the paper to your hotmail email address. Thanks for
    the feeddback on the problem with the installation of the
    utility. I will put this on the back burner since your
    experience suggests it doesn't work anyway and in the
    meantime I will continue to press Microsoft via the
    Technet Security discussion list to find out how to get
    the WPA client update working on the Server 2003 family.
    If I find any more info through that channel I will
    update you as well via your hotmail address.

    Best Regards

    John Holmblad
    wrote in message $>...
    John Holmblad, Jan 21, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.