The WAP have nothing to do with "domains". A WAP is nothing more than a
glorified "switch".
Just plug the WAPs into the LAN near the physical area that they serve.
Give each one a distinct "network name" so that you know which WAP you a
connecting to when you see the wireless "networks" on the scan list on the
client. The wireless "network" has nothing to do with a *real*
network,...think of it more as a way to give the WAP a "name" that
identifies the WAP.
****Looking at the model numbers you bought the wrong kind of devices****
You did *not* buy WAPs, you bought Wireless NAT Devices (they call them
routers,...I don't). These will not work the way you expect. Take them back
to the store and buy WAPs (there is no "R" in the model number),...they do
not do NAT,..they have nothing to do with what kind of Internet Connection
you have,....they have nothing to do with the Internet at all.
Wireless NAT Devices are mean to be used as NAT Firewalls for the LAN and
they sit on the "network edge" between the LAN and the Internet,...and there
is only supposed to be one per LAN,..or at least one per Internet Link.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Oscar" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Some Help Please.
>
> I need to install two Access Points into my wired Network, so the people
> with notebooks
> would logon into the domain and use shared resources, but I cant configure
> the Access Points,
> either the Windows 2003 Domain.
>
> I have 3 Servers:
> 1 - Domain Controller
> 2 - Exchange Server / Secondary DC
> 3 - ISA Server
>
> And I have 2 AP/Routers Linksys WRT54G and a WRT54GX4
>
> If somebody could help me please.
>
> Regards.
>
> Oscar
>
>
Similar Threads
Linear Mode
