"dexterMor via WinServerKB.com" <u53265@uwe> wrote in message
news:9916ebefae179@uwe...
> http://technet.microsoft.com/en-us/l...86(WS.10).aspx
>
Thank you for posting the link. According to the first paragraph, it states:
"To provide authorization and authentication, automatic IP address
assignment, and name resolution for wireless users, your networking
infrastructure should include the following services:"
This means that if you want to use wireless in an AD infrastructure
utilizing certificate authentication, certificate autoenrollment using GPOs,
and a certificate server, you need all those components listed in the
article.
I'm not sure if you are aware of it or not, but this is a very complicated
setup. I set this up with one of my clients a couple of years ago using a
Cisco Aironet 1231 Wireless AP and it took me about two weeks before I got
it setup correctly.
And yes, you need Active Directory, which requires DNS, then you need a
separate server for your Certificate Authority (you could install it on a DC
but not recommended) in order to create a PKI for the domain, an IAS server
(Windows version of RADIUS), a wireless laptop to test it, as well as a
wireless Access Point, such as a Cisco AP, (there are others you can choose
from), that supports certificates authentication, TKIP, EAP, as well as
RADIUS.
This is a very complex setup.
You could probably install this all on one laptop, but the laptop needs to
be a beefy laptop, with plenty of RAM and diskspace, as well as a strong
CPU. You still need a wireless access point, too, as well as another laptop
to test it. However, I really do not recommend it on one laptop, rather it
needs multiple servers, and besides, it will utilize all the resources of
your laptop to the point you won't be able to run anything else.
I would suggest installing this on a PC using Virtual PC, and create virtual
machine, one each for a DC, a RRAS server with IAS installed, and another
virtual machine for Certificate Services.
And as I mentioned in an earlier post, the DNS error you were getting was
because the NICs were not connected to anything and had no IP addresses. The
NICs need to be online (connected), enabled and configured for DNS to run,
as well as any other service to run that requires network services.
Good luck with everything. Let us know how you make out.
Ace