problem connecting a Linksys WAP11 to BEFW11S4

[Selster]

I'm having problems adding a WAP11 to my existing wireless network. I
have a Linksys BEFW11S4 Wireless Access Point/Cable Router. I want to
add another PC to this wireless network via a WAP11. I've downloaded
the newest drivers and firmware upgrades. I have attempted to
configure the WAP11 as a Wireless Access Client, but it still does not
get an IP. I went to the Linksys Knowledge Base and they have a
solution but I can't get it to work. Does anyone know if I need to
place another WAP11 in my BEFW11S4 to act as a bridge?

Need some clarification,
thanks,
steve.

[Yenie Tran]

You need the bridge.... but what is your OS? You may not need one.
"Selster" <wood...@usa.net> wrote in message
news:9961c295.02012...@posting.google.com...

[Edward Gerety]

Depends on your software!
"Yenie Tran" <ye...@bellsouth.net> wrote in message
news:ziQ28.30072$Y17.2...@e3500-atl2.usenetserver.com...

[Rob Lind]

I am using a wap11 in client mode without difficulty. I have had it connect
to both my befw11s4 and a separate wap during testing phases. Should work.
Make sure channel setting , ssid etc are same. Turn off WEP to test then
turn back on. Just some thoughts. Good luck

Rob

"Selster" <wood...@usa.net> wrote in message
news:9961c295.02012...@posting.google.com...

[Selster]

When you say software do you mean OS? Linksys software? Firmware? If
you have this working, please give me specifics. I could use the help.

Here's my configuration:
Windows 98SE machine with BEFW11S4 connected and configured. Windows
2000 machine, now, with the Linksys USB wireless device (works fine).
Before I installed the USB wireless on the W2K machine, I was trying
to configure the WAP11 on this machine. No luck. Could not get an IP.
Then tried another configuration at my buddies house: W2K with
BEFW11S4 connected and configured. Added new software/firmware to
another W2K machine and attempted to configure the WAP11 from that
machine. Able to configure, but still no IP.

Still dead in the water.
thanks,
steve.

"Edward Gerety" <ger...@uga.edu> wrote in message news:<HlQ28.30077$Y17.2...@e3500-atl2.usenetserver.com>...

[Rob Lind]

Is the wap 11 connected to the computer via cat5 directly? If so you need
to use a crossover cable as the connection. If you run it into a hub then
straight thru cable is ok.

[Selster]

Rob,
I have the correct configuration and setup. Crossover cable in place
all along. Doesn't seem to get IP. Did you have a configuration
similiar to mine? Meaning, did you try accessing the WAP11 without
another one connected to the BEFW11S4? That's what I'm trying to do.
My buddy seems to think that we need another WAP11 attached to the
BEFW11S4 in order for this to work. Maybe you can email me your
settings (screen prints?). Sure would appreciate any help.
thanks again,
steve.

"Rob Lind" <rsl...@rcn.com> wrote in message news:<a2i4e6$4lc$1...@bob.news.rcn.net>...

[Rob Lind]

The IP address for the wap is only for snmp use and not needed for
functionality. I did not use DHCP to obtain IP address but manually set it
ti 192.168.1.252 subnet 255.255.255.0 and diasbled (unchecked) DHCP. I think
with such a small network it is easier to use staic IP addresses for these.
Are you putting the correct BSS (MAC address) of the router in? I also used
a static adress for the single computer connected to the wap but DHCP should
function normally. make sure authentication and preamble type are set the
same on router and wap. I hate to fiddle with my stable system but i'll try
to connect my wap to router tonight. It currently is connecting with next
door neighbors WAP thru external antenna.

Rob

[Selster]

Hi Rob,
Thanks for the info. You bring up a good point about the BSS. Which
MAC address should I be using? There are 3, one from the WAN, one from
the LAN and one from the ROUTER.
I'll try the other options as well.
Thanks for your continued support.
steve.

"Rob Lind" <rsl...@rcn.com> wrote in message news:<a2ksps$1lf$1...@bob.news.rcn.net>...

[Don Widders]

I've been away for a while and I'm catching up.

The WAP11 client mode only works with another WAP11. That seems a little
pathetic and not a TRUE client mode if you ask me, but I've used the WAP11
many times as client of a WAP11 access point and advised someone else to do
the same with a non-WAP11 access point. Someone posted the message that
WAP11 client mode only works with a WAP11 access point. I didn't believe
that, so I tried to associate a WAP11 in client mode with a non-WAP11 access
point and I was not successful.

Don W.

[Don Widders]

Rob, now I'm confused! I'm happy to hear the WAP11 in client mode will
associate with the BEFW11S4, but I was unable to make it work with the
RangeLAN DS access point. What was the "separate wap"?

Don W.

"Rob Lind" <rsl...@rcn.com> wrote in message

news:a2i38m$sor$1...@bob.news.rcn.net...

[Rob Lind]

When I was in early setup/testing phase I successfully connected my wap to
my wap/router as far as I can remember. This was 6 months ago. I eventually
set up external antennas and have a wap in client mode set up to talk to
another wap in standard wap mode. I would love to recreate my previous
success with router to show it works but this would require taking down
access panels and climbing in crawl space etc. I hate to say I don't
remember specifics of settings because I was only fooling around prior to
completing my final setup. how would the wap in client mode tell the
difference between a wap/router and just a wap? My regular USB client lists
them both when I do a site survey. You've got me so interested I might have
to get the screw driver out and go at that access panel again.

"Don Widders" <wid...@talkwithoutdifficulty.org> wrote in message
news:u4un7hi...@corp.supernews.com...

[Rob Lind]

In reading updated manual for linksys wap it does suggest that a wap11 in
client mode can only link to another wap11. However the documentation
confuses me because it also suggests that a wap11 in client mode should be
able to also connect to other clients. This I do not believe is true because
I remember not being able to see that wap with a usb client on laptop
whenever I placed it in this wap11 client mode. Steve if your reading this
maybe I am off base and wasting your time. What does linksys say?

Rob

"Rob Lind" <rsl...@rcn.com> wrote in message

news:a2npg6$j0v$1...@bob.news.rcn.net...

[Rob Lind]

I've been lurking in this group long enough to know if Don Widders thinks
I'm wrong them I'm retracting all statements and running for the hills. :)

Rob

"Rob Lind" <rsl...@rcn.com> wrote in message

news:a2nqnk$oft$1...@bob.news.rcn.net...

[Don Widders]

I'm very interested too! I did a survey using the AMTEL utility when
selecting the preferred AP to which the client WAP11 was to connect. The
client WAP11 was able to see both a WAP11 access point and the RangeLAN DS
access point. It associated easily with the WAP11 access point, but I was
not able to coax it into associating with the RangeLAN DS access point.

I have several uses for an 'Ethernet client', so it will make me very happy
to find out I was doing something stupid when trying to connect to the
RangeLAN AP.

I'm in agreement with you that the WAP11 in client mode shouldn't be able to
tell the difference between a WAP11 access point and any other AP, but I
tried everything I could think of for over an hour and never was able to
make it work with anything but the WAP11 AP, so I don't know what to tell
you. If anyone else has associated a WAP11 (in client mode) to a non-WAP11
AP, I would like to know how you did it! Maybe it's a Linksys thing --
works with Linksys APs only? (I don't have a BEFW11S4 to try!)

Don W.

"Rob Lind" <rsl...@rcn.com> wrote in message

news:a2npg6$j0v$1...@bob.news.rcn.net...

[Don Widders]

I should find the docs and read them. From what you wrote here, it sounds
to me like the WAP11 will only connect to a WAP11 access point, but perhaps
there is a way for it to connect to other clients in ad hoc?

Don W.

"Rob Lind" <rsl...@rcn.com> wrote in message

news:a2nqnk$oft$1...@bob.news.rcn.net...

[Don Widders]

I certainly don't think you're wrong, Rob... you took the time to read the
documentation and I did not!

This is an important thread because USB is probably the best choice for a
desktop adapter -- unless there is an Ethernet adapter that works! If I'm
not mistaken, the WAP11 would also match the most expensive client products
in output power, so it could be an interesting alternative when the access
point can't reliably 'hear' the client. It does bring up some routing
issues (or questions) and maybe that was my problem, but my setup was pretty
simple: desktop connected to the 'client' WAP11 through a crossover cable.

So hopefully I was doing something stupid and the WAP11 can be used as a
generic Ethernet connected client.

Don W.

"Rob Lind" <rsl...@rcn.com> wrote in message

news:a2nr0a$po5$1...@bob.news.rcn.net...

[c....@nospam.blueyonder.co.uk]

>The WAP11 client mode only works with another WAP11. That seems a little
>pathetic and not a TRUE client mode if you ask me, but I've used the WAP11
>many times as client of a WAP11 access point and advised someone else to do
>the same with a non-WAP11 access point. Someone posted the message that
>WAP11 client mode only works with a WAP11 access point. I didn't believe
>that, so I tried to associate a WAP11 in client mode with a non-WAP11 access
>point and I was not successful.

If it's purely a single unit at each end (a single point-point) then you might
like to try setting each end in bridging Point-2-Point mode ... anyone running
netstumbler won't see the network then.

Clive

[c....@nospam.blueyonder.co.uk]

>I'm very interested too! I did a survey using the AMTEL utility when
>selecting the preferred AP to which the client WAP11 was to connect. The
>client WAP11 was able to see both a WAP11 access point and the RangeLAN DS
>access point. It associated easily with the WAP11 access point, but I was
>not able to coax it into associating with the RangeLAN DS access point.

Did you try power cycling (power it off, then back on) the wap11 after changing
the settings ?

We had the same problem and found we had to power cycle the wap11's for the new
settings to actually work, not sure why but no way could we get them to work
after a setting change and no power cycle.

Clive

[Don Widders]

I don't remember whether or not I did that. At the moment I don't have a
WAP11 that is not in use. This weekend I'll try again.

Thanks for the tip!

Don W.

<c....@nospam.blueyonder.co.uk> wrote in message
news:omuv4usgb6eqj16eh...@4ax.com...

[Selster]

Boy oh Boy, did I stir up tizzy! I'm gone a day and WOW! Well, good
news and bad news. The WAP11 cannot communicate to the Router, YET!
Linksys finally called me back and confirmed this. Also, they ARE
working on a fix for the Router and WAP11 to work this way. Soon to be
a neighborhood near you.
Bad news, I had to buy another WAP11. Good news, it worked without a
glitch. Couple of settings later and BAM. Seamless connectivity. I
have a PC connected to a BEFW11S4, connected to a WAP11. Upstairs I
have an older MAC connected to an ethernet crossover cable connected
to the other WAP11. Works like a charm. Downstairs, I have another PC
connected to a WUSB11 (USB version) and again its a beautiful thing!

All is well in my world (of course, I'm out the cost of another
WAP11). I hope all is well in yours.

P.S. Keep emailing Linksys about this conflict and maybe we'll get the
fix sooner.
Thanks for all your support and help. You've been courteous and
informative.
steve.

"Don Widders" <wid...@talkwithoutdifficulty.org> wrote in message news:<u50m41t...@corp.supernews.com>...

[Rob Lind]

Guess I'll keep that access panel screwed on the wall.

Rob

"Selster" <wood...@usa.net> wrote in message
news:9961c295.02012...@posting.google.com...