Re: adding wireless access points (WAP's) to my network - can't get it to work
- From: "Mike Webb" <Mike_Webb@xxxxxxxxxxxxxxxxx>
- Date: Fri, 10 Mar 2006 08:24:49 -0600
Background: Our "compound" is composed of 5 buildings -- admin, a dormitory
for up to 40 people, a small laboratory, and two houses used to house
long-term graduate students. Due to the distances (straight-line), the
vendor I worked with recommended 3 WAP's - one in the center of the admin
building, one in the dormitory and one in a house. In this way, no one
building is more than 4-500 feet from a WAP. Easily handled by the Linksys
WAP54GX.
The WAP in the admin building is, and will stay, wired to the router. In
that way it can "talk" to the other WAP's so they can handle any wireless
clients. The router is set to handle it's own DHCP through the WAP's, with
the address field set to 192.168.1.11 through 192.168.1.239. The subnet
mask is 255.255.255.0 and the IP of the router is 192.168.1.1. I've set the
IP's for the WAP's to 192.168.1.5 through .7 by selecting Static IP from the
configuration dropdown.
I can browse to the admin WAP by web-browser and just confirmed the subnet
mask is correct and the gateway is set for the router's IP.
Mike
"Cris Hanna (SBS-MVP)" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:%23TSmm1$QGHA.4384@xxxxxxxxxxxxxxxxxxxxxxx
Well never in your original post did you indicate that you didn't want the
wireless clients to have access to your network.
So now that we have a better picture of what you are trying to accomplish
we can go on a bit.
Does your router have a wireless access point?? If the answer is
yes...why do you need others??
But what it sounds like you what you need to set up is wireless
bridging...so you'll have to read the docs for your router and the WAPs
and see if they can do that.
Since you removed the cable to the router...unless you setup wireless to
wireless bridging, there's not path from teh WAP to the router
Make sense?
--
Cris Hanna [SBS-MVP]
--------------------------------------
Please do not respond directly to me, but only post in the newsgroup so
all can take advantage
"Mike Webb" <Mike_Webb@xxxxxxxxxxxxxxxxx> wrote in message
news:uoC$ES8QGHA.3916@xxxxxxxxxxxxxxxxxxxxxxx
Well ... How would you recommend I handle this: I don't want the
wireless clients to have access to the LAN - primarily becuase I'm very
new to wireless and fairly new to SBS; I don't want to go too far too
fast and thereby open us up to a serious security hole. They are in
other buildings and just need internet access for web-mail and personal
use (they live here for short periods of time doing research). And, we
are in a very rural area, nearest neighbor is a mile away, nearest town
is 7 miles, and nearest public road is 1.5 miles away. We're at the end
of a private road and have a bit of control over who's here with
permission.
Mike
"Cris Hanna (SBS-MVP)" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:O9NInB8QGHA.4920@xxxxxxxxxxxxxxxxxxxxxxx
Pardon me for being blunt but your system is not properly connected.
Your WAPs should not be connected to the router...they should be
connected to the switch on the internal LAN along with all workstations
and the LAN nic of the server.
DHCP should not be running out via the external nic.
--
Cris Hanna [SBS-MVP]
--------------------------------------
Please do not respond directly to me, but only post in the newsgroup so
all can take advantage
"Mike Webb" <Mike_Webb@xxxxxxxxxxxxxxxxx> wrote in message
news:%23JTC1m4QGHA.2300@xxxxxxxxxxxxxxxxxxxxxxx
We have MS SMall Business Server 2003 Premium. Until 2 days ago, I was
operating with just 1 NIC. Based on advice from
www.smallbizserver.net, I have both NIC's up and working - one as
internal and one as external. The ISP gave us a dynamic IP (they don't
offer static yet). I set my default gateway (router) to 192.168.1.1
and have it connected with the external NIC. The internal NIC is
connected to my switch and is on network 192.168.16.* I ahd been
letting the router handle DHCP, but now I turned on DHCP in the server
and set 2 Scopes - one for the 192.168.1.* external NIC and one for
the 192.168.16.* internal NIC.
The WAP's are Linksys WAP54GX's. Per the setup CD, I connected each in
turn to the router, gave them each a static IP of 192.168.1.5 through
.7, and tested them. I could access each from a web-browser, so
thought I was good-to-go. But .... I was wrong.
The problem is they won't do anything more than indicate to a wireless
client that a wireless network exists. Can't go any further. When I
disconnect them from the router (take out the CAT5 cable but leave on
otherwise), I can't access them via a web-browser. Tried putting one
on the internal Scope, same result. Obviously I did something wrong,
but I ahve no idea what it is. It's my first foray into wireless. Can
someone give me advice on what I should do?
--
Mike Webb
Platte River Whooping Crane Maintenance Trust, Inc.
a 501 (c)(3) organization
.
- Follow-Ups:
- Re: adding wireless access points (WAP's) to my network - can't get it to work
- From: Owen Williams
- Re: adding wireless access points (WAP's) to my network - can't get it to work
- References:
- adding wireless access points (WAP's) to my network - can't get it to work
- From: Mike Webb
- Re: adding wireless access points (WAP's) to my network - can't get it to work
- From: Cris Hanna \(SBS-MVP\)
- Re: adding wireless access points (WAP's) to my network - can't get it to work
- From: Mike Webb
- Re: adding wireless access points (WAP's) to my network - can't get it to work
- From: Cris Hanna \(SBS-MVP\)
- adding wireless access points (WAP's) to my network - can't get it to work
- Prev by Date: Re: Auto-Started services not running
- Next by Date: After new install, what updates
- Previous by thread: Re: adding wireless access points (WAP's) to my network - can't get it to work
- Next by thread: Re: adding wireless access points (WAP's) to my network - can't get it to work
- Index(es):
Relevant Pages
|
