Protected WLAN distribution @ existing Server Organization

Dear users,

I'm busy with Windows Server 2003 for 1 yr. now, and understand most of the
basics. Once i managed to set up my server as an IAS (internet.access.server)
for my companies network. Simply looked like this:

internet > input @ server > output from server > pc-network
(my server has 2 LAN connections: 1x ISP, 1x LAN)

Nowadays, I have an internet connection, routed to my PC's with a Linksys
modem/router. One of the ports goes straight to my Windows Server 2003
(Ent.Ed.) which supplies an Exchange Organization for those PC's, and does
some backup-processes 24/7.

Now I want to use the other LAN port on that server, to connect that to a
Linksys Wireless Accesspoint, to supply wireless users with kinda "hotspot",
well protectected by shielding off my network of PC's.

So I need the BEST way to CONFIGURE my server as a 2nd router in network,
supplying a protected DHCP range for clients connecting through the AP
(accesspoint). I don't need RADIUS configs, cuz my AP doesn't support it
(only WEP64/128 :-( )

HOW do I need to fix that? What guides should I follow and in what order?
There need to be specific whitepapers for it, and it shouldn't be too
difficult i guess.

BUT MOST IMPORTANT: i need to MANAGE those clients, not as part of a domain,
but I want to setsome policies for each wireless connected client, like only
the use of HTTP and HTTPS, but very much would like to set the maximum down-
and upstream rates for each client.

Here's a schematic view of the network I'd like to create:

*****************************************
INTERNET
|
ROUTER/MODEM LINKSYS
|
|
PC 1 PC 2 PC 3 PC 4
|
|
SERVER
|
|
WIRELESS ACCESSPOINT
|
|
wl.user1 wl.user2 wl.user3 wl.user4
******************************************
Thanks in advance for any help! I would appreciate it!
Best regards,
Stensol, The Netherlands

=?Utf-8?B?U3RlbnNvbA==?= <(E-Mail Removed)> wrote in
news:8AFA77DE-85BE-49C9-ABC6-(E-Mail Removed):

>snip<
>
> So I need the BEST way to CONFIGURE my server as a 2nd router in
> network, supplying a protected DHCP range for clients connecting
> through the AP (accesspoint). I don't need RADIUS configs, cuz my AP
> doesn't support it (only WEP64/128 :-( )
>
> HOW do I need to fix that? What guides should I follow and in what
> order? There need to be specific whitepapers for it, and it shouldn't
> be too difficult i guess.
>
>snip<
> ******************************************
> Thanks in advance for any help! I would appreciate it!
> Best regards,
> Stensol, The Netherlands
>

Hi Stensol --

This paper explains how to deploy Wi-Fi with or without a domain:


"Step-by-Step Guide for Secure Wireless Deployment for Small Office/Home
Office or Small Organization Networks" at
http://www.microsoft.com/downloads/d...269902e8-fc41-
4eb1-9374-44612e64f0fb&displaylang=en


Obviously if you are going to connect the AP directly to a network adapter
on the server you need to use a crossover cable, not a regular Ethernet
cable.

And if you are going to require any authentication you need to determine
the user account database you want to use. Does the AP allow you to create
user accounts...? If not, perhaps it provides a way to authenticate against
the Local Users and Computers database on the server or against Active
Directory if you have that installed on the server -- you will need to
check the AP documentation for that.

To route traffic on the server to the LAN you can install Routing and
Remote Access service and configure it as a router. The Help on the box has
all the information on how to do this.

For security reasons (to be honest) it would be best to buy an AP that is
compatible with 802.1X and RADIUS so that you can use IAS and deploy PEAP-
MS-CHAP v2 as your authentication method. (How to do that is described in
the paper above.)



--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.