Re: Wireless Access Point
- From: Owen Williams [SBS MVP] <Owen@xxxxxxxxxxxxxxxxxx>
- Date: Sat, 4 Aug 2007 00:00:30 -0400
In article <CB7C2797-B357-4841-A6A3-F77538AC7E90@xxxxxxxxxxxxx>,
Ripley@xxxxxxxxxxxxxxxxxxxxxxxxx says...
Dave & Cris have sumarized the issues very nicely. (Thanks, guys!)
If you are reluctant to use a RADIUS-based authentication method because
the configuration time seems to be lengthy, perhaps I can put your mind
at ease. At least with my document (can't speak for Microsoft's), it
takes approximately one hour start to finish, although I do recommend
you read completely through the document (or at least look at the
associated slide deck) once before doing it. The part that takes the
most time isn't really the RADIUS setup - that's pretty simple. It's
configuring the GPOs. But this is not even a weekend project - it's
closer to a lunch break project.
Once it's working [and, full disclosure, some people have had problems,
most of the time because they skipped or mis-applied a step] it "Just
Works." In other words, all the work is at the beginning, after which
your life gets a LOT easier. For example, as Dave points out, you never
have to worry about changing pre-shared keys if a computer is lost or
stolen or someone leaves the company and knows the key.
I recently added a new Vista laptop to my own network. After I used the
normal /ConnectComputer method to join it to my SBS domain with a wired
connection, I disconnected the Ethernet cable, turned on the wireless,
and - voila - I had a secure wireless connection which is wired-
equivalent. There was no manual configuration on the Vista laptop: the
certificate and wireless configuration were all pushed down by GPO. It
"Just Worked."
-- Owen Williams (SBS MVP)
This isn't really a problem (I don't think) but more of a question ...
I have an SBS 2003 (Premium with ISA 2004) wired LAN which is running ok. I
purchased a D-Link Wireless Access Point and downloaded some detailed notes
on how to configure wireless networking on an SBS2003 network. These notes
can be found under the heading of "Configure Wireless Networking on Windows
Small Business Server 2003" under Technet's Library path: Windows Small
Business Server Technical Library - Windows Small Business Server 2003
Technical Library - Operations.
They seemed a bit involved to say the least and involved installing IAS onto
my SBS 2003 server. As a tester, I connect this Wireless Access Point to my
laptop, configure it with an IP address and gateway (the gateway being my SBS
2003 server), then patched it into my wired LAN. I also enabled WPA
encryption too, by the way. I then set my laptop back to DHCP, found the
wireless network, joined it, entered the key, and hey presto I'm on the SBS
2003 LAN through the WAP.
This all seems too easy and although I have full access and can see no
problems ... my question is, have I missed something?? Do I really need to go
through the detailed notes and install IAS as a RADIUS server? All I want is
for my LAN clients to be able to come into the office and connect to the SBS
2003 network via wireless.
I am a little naive and inexperienced when it comes to Wireless networking
so apologies if this question seems a bit silly or I've got the wrong end of
the stick. I'd just like to check that I've done everything ok .... ??
- Prev by Date: Re: RWW - Local Policy connect to desktop issue
- Next by Date: pppoe and two nics
- Previous by thread: Re: Wireless Access Point
- Next by thread: Re: CEICW will not start
- Index(es):
Relevant Pages
|
