On Sat, 20 Nov 2004 02:35:09 GMT, "Bill Jasiulewicz"
<(E-Mail Removed)> wrote:
>With the 802.11b wireless router, I could move from the office where the AP
>was located to the living room about 20 feet away and still keep 11Mb/sec
>transfer, but with the WRT54G, I can't move more than about 10 feet before
>the connection is dropped.
This is not normal. I'll assume you're using the same laptop and
radio for testing. If you changed both the wireless router *AND* the
wireless client radio at the same time, you have the possibility that
both are busted.
>FYI, I have now tested with 3 different WRT54G wireless routers and all have
>the same range problem when compared to their 802.11b counterparts.
Again, it takes two to tango. What are you using on the client end
and does it work (without any changes) with the old unspecified
802.11b wireless routers? If it's the same laptop and radio, then my
guess(tm) is that something is busted in the new WRT54G. However, the
possibility of 3ea WRT54G wireless routers all being defective is
difficult to fathom. Therefore, I would look for problems with the
wireless client (laptop).
>Can/should I use coax to separate the antennas and place one of the antennas
>in the living room and another in the office?
That will work, but not very well. The coax loss is far to much to be
useful. I would go back to the two access point model that you
started with. If you're stuck with using the same channel on both,
just make sure they don't "see" each other and you should be ok.
>Is there a better solution, besides scrapping LinkSys (since I have a
>substantial investment in equipment) and moving to Parker Vision?
I can't offer a solution as you started out with what I consider to be
a decent approach. The problem is that you're troubleshooting with
far too many unknowns. I suggest you divide and conquer. Drag your
laptop with it's unspecified wireless card over to a local free hot
spot or coffee shop and test the range. If you can see your neighbors
wireless router, try it with theirs. Do some walking and convince
yourself that the client end of the puzzle is working as expected and
as it was before you started juggling hardware. If the client works,
then try to figure out what went wrong on the wireless router end.
For me, that usually means using my "known working" test laptop with
Netstumbler and watching the signal strength and S/N ratio. If the
signal strength is good, but the S/N (or noise level) sucks, you're
getting interference on your allegedly empty channel.
--
Jeff Liebermann
(E-Mail Removed)
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060 AE6KS 831-336-2558