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

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:

http://www.microsoft.com/downloads/details.aspx?
FamilyId=009D8425-CE2B-47A4-ABEC-
274845DC9E91&displaylang=en

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.

Hi,

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

--
--Jonathan Maltz [Microsoft MVP - Windows Server]
http://www.visualwin.com - 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.


"John Holmblad" <(E-Mail Removed)> wrote in message
news:013401c3cd95$612c9a00$(E-Mail Removed)...
> 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:
>
> http://www.microsoft.com/downloads/details.aspx?
> FamilyId=009D8425-CE2B-47A4-ABEC-
> 274845DC9E91&displaylang=en
>
> 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.
>
>
>

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.



>-----Original Message-----
>Hi,
>
>I was able to start setup by saving the file, and
setting XP compatibility
>on the EXE
>
>--
>--Jonathan Maltz [Microsoft MVP - Windows Server]
>http://www.visualwin.com - 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.
>
>
>"John Holmblad" <(E-Mail Removed)>
wrote in message
>news:013401c3cd95$612c9a00$(E-Mail Removed)...
>> 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:
>>
>> http://www.microsoft.com/downloads/details.aspx?
>> FamilyId=009D8425-CE2B-47A4-ABEC-
>> 274845DC9E91&displaylang=en
>>
>> 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.
>>
>>
>>
>
>
>.
>

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]
http://www.visualwin.com - 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.


"John Holmblad" <(E-Mail Removed)> wrote in message
news:033801c3ce63$3607f080$(E-Mail Removed)...
> 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.
>
>
>
> >-----Original Message-----
> >Hi,
> >
> >I was able to start setup by saving the file, and
> setting XP compatibility
> >on the EXE
> >
> >--
> >--Jonathan Maltz [Microsoft MVP - Windows Server]
> >http://www.visualwin.com - 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.
> >
> >
> >"John Holmblad" <(E-Mail Removed)>
> wrote in message
> >news:013401c3cd95$612c9a00$(E-Mail Removed)...
> >> 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:
> >>
> >> http://www.microsoft.com/downloads/details.aspx?
> >> FamilyId=009D8425-CE2B-47A4-ABEC-
> >> 274845DC9E91&displaylang=en
> >>
> >> 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.
> >>
> >>
> >>
> >
> >
> >.
> >

Jonathan,

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:

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]
http://www.visualwin.com - 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.


<(E-Mail Removed)> wrote in message
news:058101c3cfc9$93d39900$(E-Mail Removed)...
> Jonathan,
>
> 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:
> .
> .
> .
> You can also get online support if you are having
> problems with Windows Update.
>
>
> Send error number to Microsoft (0x800A138F)
> Note This sends error information but does not
> create a support incident; you may or may not
> receive a response.
>
>
> I restarted each system to see if a fresh boot would
> clear up the problem but no luck. The failure is
> persistent. It would appear that running the executable
> in question probably modified the registry or other OS
> component in some way so that Windows Update now FAILS
> reliably.
>
> Furthermore I learned to my dismay that, in contrast to
> Window XP, as far as I can tell, neither of the
> aforementioned server OS's support the System Restore
> feature. Boo Hoo! I will now take a "detour" to fix
> whateve broke when I ran the aforementioned executable.
>
> I am running up against a deadline to finish lab tests of
> WPA with both servers and I would like to do it with the
> Microsoft WPA support if at all possible. My fallback
> will be to use the client card supplier's configuration
> utilities (Netgear for the SBS2003 system and Linksys for
> the Server 2003 system) assuming I can get their software
> to work. I am using the latest version of the client
> utility software from each supplier so it SHOULD work.
>
> Any further ideas that you have on this issue would be
> appreciated despite this, hopefully, minor setback.
>
> >-----Original Message-----
> >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]
> >http://www.visualwin.com - 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.
> >
> >
> >"John Holmblad" <(E-Mail Removed)>
> wrote in message
> >news:033801c3ce63$3607f080$(E-Mail Removed)...
> >> 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.
> >>
> >>
> >>
> >> >-----Original Message-----
> >> >Hi,
> >> >
> >> >I was able to start setup by saving the file, and
> >> setting XP compatibility
> >> >on the EXE
> >> >
> >> >--
> >> >--Jonathan Maltz [Microsoft MVP - Windows Server]
> >> >http://www.visualwin.com - 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.
> >> >
> >> >
> >> >"John Holmblad" <(E-Mail Removed)>
> >> wrote in message
> >> >news:013401c3cd95$612c9a00$(E-Mail Removed)...
> >> >> 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:
> >> >>
> >> >> http://www.microsoft.com/downloads/details.aspx?
> >> >> FamilyId=009D8425-CE2B-47A4-ABEC-
> >> >> 274845DC9E91&displaylang=en
> >> >>
> >> >> 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.
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

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


I will let you know how it goes.

Thanks for your help.

>-----Original Message-----
>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]
>http://www.visualwin.com - 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.
>
>
><(E-Mail Removed)> wrote in message
>news:058101c3cfc9$93d39900$(E-Mail Removed)...
>> Jonathan,
>>
>> 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:
>> .
>> .
>> .
>> You can also get online support if you are having
>> problems with Windows Update.
>>
>>
>> Send error number to Microsoft (0x800A138F)
>> Note This sends error information but does not
>> create a support incident; you may or may not
>> receive a response.
>>
>>
>> I restarted each system to see if a fresh boot would
>> clear up the problem but no luck. The failure is
>> persistent. It would appear that running the executable
>> in question probably modified the registry or other OS
>> component in some way so that Windows Update now FAILS
>> reliably.
>>
>> Furthermore I learned to my dismay that, in contrast to
>> Window XP, as far as I can tell, neither of the
>> aforementioned server OS's support the System Restore
>> feature. Boo Hoo! I will now take a "detour" to fix
>> whateve broke when I ran the aforementioned executable.
>>
>> I am running up against a deadline to finish lab tests
of
>> WPA with both servers and I would like to do it with
the
>> Microsoft WPA support if at all possible. My fallback
>> will be to use the client card supplier's configuration
>> utilities (Netgear for the SBS2003 system and Linksys
for
>> the Server 2003 system) assuming I can get their
software
>> to work. I am using the latest version of the client
>> utility software from each supplier so it SHOULD work.
>>
>> Any further ideas that you have on this issue would be
>> appreciated despite this, hopefully, minor setback.
>>
>> >-----Original Message-----
>> >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]
>> >http://www.visualwin.com - 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.
>> >
>> >
>> >"John Holmblad" <(E-Mail Removed)>
>> wrote in message
>> >news:033801c3ce63$3607f080$(E-Mail Removed)...
>> >> 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.
>> >>
>> >>
>> >>
>> >> >-----Original Message-----
>> >> >Hi,
>> >> >
>> >> >I was able to start setup by saving the file, and
>> >> setting XP compatibility
>> >> >on the EXE
>> >> >
>> >> >--
>> >> >--Jonathan Maltz [Microsoft MVP - Windows Server]
>> >> >http://www.visualwin.com - 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.
>> >> >
>> >> >
>> >> >"John Holmblad"
<(E-Mail Removed)>
>> >> wrote in message
>> >> >news:013401c3cd95$612c9a00$(E-Mail Removed)...
>> >> >> 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:
>> >> >>
>> >> >> http://www.microsoft.com/downloads/details.aspx?
>> >> >> FamilyId=009D8425-CE2B-47A4-ABEC-
>> >> >> 274845DC9E91&displaylang=en
>> >> >>
>> >> >> 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.
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>
>.
>

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

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]
http://www.visualwin.com - 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.


"John Holmblad" <(E-Mail Removed)> wrote in message
news:046901c3d0c3$4469cb50$(E-Mail Removed)...
> 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
> behavior.
>
>
> I will let you know how it goes.
>
> Thanks for your help.
>
> >-----Original Message-----
> >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]
> >http://www.visualwin.com - 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.
> >
> >
> ><(E-Mail Removed)> wrote in message
> >news:058101c3cfc9$93d39900$(E-Mail Removed)...
> >> Jonathan,
> >>
> >> 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:
> >> .
> >> .
> >> .
> >> You can also get online support if you are having
> >> problems with Windows Update.
> >>
> >>
> >> Send error number to Microsoft (0x800A138F)
> >> Note This sends error information but does not
> >> create a support incident; you may or may not
> >> receive a response.
> >>
> >>
> >> I restarted each system to see if a fresh boot would
> >> clear up the problem but no luck. The failure is
> >> persistent. It would appear that running the executable
> >> in question probably modified the registry or other OS
> >> component in some way so that Windows Update now FAILS
> >> reliably.
> >>
> >> Furthermore I learned to my dismay that, in contrast to
> >> Window XP, as far as I can tell, neither of the
> >> aforementioned server OS's support the System Restore
> >> feature. Boo Hoo! I will now take a "detour" to fix
> >> whateve broke when I ran the aforementioned executable.
> >>
> >> I am running up against a deadline to finish lab tests
> of
> >> WPA with both servers and I would like to do it with
> the
> >> Microsoft WPA support if at all possible. My fallback
> >> will be to use the client card supplier's configuration
> >> utilities (Netgear for the SBS2003 system and Linksys
> for
> >> the Server 2003 system) assuming I can get their
> software
> >> to work. I am using the latest version of the client
> >> utility software from each supplier so it SHOULD work.
> >>
> >> Any further ideas that you have on this issue would be
> >> appreciated despite this, hopefully, minor setback.
> >>
> >> >-----Original Message-----
> >> >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]
> >> >http://www.visualwin.com - 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.
> >> >
> >> >
> >> >"John Holmblad" <(E-Mail Removed)>
> >> wrote in message
> >> >news:033801c3ce63$3607f080$(E-Mail Removed)...
> >> >> 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.
> >> >>
> >> >>
> >> >>
> >> >> >-----Original Message-----
> >> >> >Hi,
> >> >> >
> >> >> >I was able to start setup by saving the file, and
> >> >> setting XP compatibility
> >> >> >on the EXE
> >> >> >
> >> >> >--
> >> >> >--Jonathan Maltz [Microsoft MVP - Windows Server]
> >> >> >http://www.visualwin.com - 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.
> >> >> >
> >> >> >
> >> >> >"John Holmblad"
> <(E-Mail Removed)>
> >> >> wrote in message
> >> >> >news:013401c3cd95$612c9a00$(E-Mail Removed)...
> >> >> >> 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:
> >> >> >>
> >> >> >> http://www.microsoft.com/downloads/details.aspx?
> >> >> >> FamilyId=009D8425-CE2B-47A4-ABEC-
> >> >> >> 274845DC9E91&displaylang=en
> >> >> >>
> >> >> >> 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.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> >.
> >> >> >
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

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.


"Jonathan Maltz [MS-MVP]" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> 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
> compatible...
>
> 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
<snip>

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

>-----Original Message-----
>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.
>
>
>"Jonathan Maltz [MS-MVP]" <(E-Mail Removed)> wrote in
message news:<(E-Mail Removed)>...
>> 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
>> compatible...
>>
>> 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
><snip>
>.
>