Re: Please help with WAP54G

On Thu, 15 Dec 2005 16:35:39 GMT, "JM" <jm@xxxxxxxxx> wrote:

>I'm saying that if your
>intention truly is to assist, then you've undermined your own goal.

I thought about it over night and suspect you may be right. I'm not
sure what to do about it. I tend to separate the technical problem
from the person asking the question. That's the only way I can
effectively fix things. I've worked with customers from hell and
those that roll out the red carpet when I arrive. I treat everyone
equally and only consider the techy problems. Usually it works well.
This time, it didn't. Thanks for taking the time to point out that
I've created a problem. I'll think about it. Maybe I'll do something
else as I don't seem to be very effective at getting people to deliver
even the basics in this newsgroup.

>The WAP54G currently is part of a small business network.
>The main router is a Netgear MR814 with wireless disabled.
>The Netgear is a DHCP server.
>The Netgear is the gateway at 192.168.0.1.
>The DHCP IP range is 192.168.0.2 - 192.168.0.51

Ooops. Don't put the WAP54G in the middle of the DHCP range. The
DHCP server is suppose to ping for occupied addresses before assigning
192.168.0.31 to some client computer, but I've managed to generate
duplicate IP's anyway. However, I don't think that's causing the
connection problem.

>There are about 13 IP devices on the network, all working fine via DHCP,
>with a file server, a webcam, and an IP phone adapter assigned static IPs.

Are these IP's also assigned in the DHCP address range? You should
get a duplicate IP warning if this is the case, but such error
messages are often missed. Check the server logs.

>There are two small switches on the networking providing extra density in
>two offices.
>
>Prior to connecting the WAP54G to the network, I gave it the IP address
>192.168.0.31, subnet 255.255.255.0, gateway 192.168.0.1. I left all the
>other settings default, including the security settings, which I left turned
>off.

Please set the SSID to something other than "Linksys". The problem is
that you have no way to know if your wireless client computer is
connecting to your WAP54G or some nearby wireless router that's also
left in the default mode.

>I tried to connect a desktop machine using a Dlink DWL520 PCI NIC that I
>know to be working. I originally used the Dlink utility to configure the
>card and find the network. The NIC is set to obtain its IP info auto. The
>Dlink sees the network, SSID "linksys." It tells me there is 95%-100%
>signal strength. When I choose "linksys" profile, it tries to connect but
>does not. The "D" in the taskbar stays in the disconnected mode and I get a
>"media disconnected" statement at the ipconfig command.

I have about 4ea DWL520 PCI cards on the shelf that I won't use. They
drove me nuts. I don't recall the exact symptoms but I recall
spending literally days trying to get them to connect properly in an
assortment W2K and XP machines to my office wireless router. Driver
updates would cause the card to refuse to connect. Rollbacks wouldn't
work. WZC didn't seem any better. I had to use System Restore to
recover from the drivers as they wouldn't uninstall completely. When
functioning (using the original drivers from the supplied CDROM), one
particular card would have great signal strength and range when
running in one machine, but the same card in another machine, would
show almost no signal a few feet from the wireless router. I just
gave up, put them back in stock, bought some other PCI cards, and had
everything running a few minutes.

I then gave some of the DWL520 card to a friend, who had them running
within a few days. I don't recall if he had any similar problems.
However, there is one interesting item. All my testing of the DWL520
was done with a WRT54Gv1.1 wireless router, which has a very similar
Broadcom chipset as the WAP54G. I never bothered to test the DWL520
connectivity with another router (even though there were several
within easy reach). My friend that got them working I never
considered the possibility of a chipset compatibility issue. It's
possible, unlikely, but worth checking.

Is there another wireless client available for testing the WAP54G?
Preferably in a laptop that's known to work. (Note: I like to
diagnose things by substitution).

>I then disabled the Dlink utility and tried using Windows. Again, the SSID
>is detected, the signal strength is excellent, but no connection. It shows
>the connecting status bar, but it will not connect. It finally quits
>trying. I have deleted and rebuilt the profile several times.

I'll assume that you don't have any spyware that crams itself into the
LSP (layered service pile). Find an LSP editor and double check.

>If I enable the wireless functionality of the Netgear MR814v3 router (MAC
>address 000FB578606E, color white, with "NETGEAR" stamped in the top, black
>power cord, 36-in, 8 oz wall-wart, about 2 months old, 5-in rubber duck
>antenna, 4-port built-in switch, . . . . ; ))) [just having fun],

You forgot the firmware version. I thought the MR814 was gray.
[There's never enough information supplied to satisfy me]

>I can
>connect immediately. I also tried a Dlink DI-524 wireless router - both as
>router in place of the Netgear and as an AP connected to the Netgear - and
>again I can connect immediately.

OK. The DWL520 is functional and working with other wireless access
points. So much for that theory. There's the compatibility issue
that I previously mentioned.

>It's when I add the WAP54G back to the mix that I cannot connect.
>
>Please inform what I have left out. This truly is all the pertinent info I
>can think of at the moment.

Well, I could use the answers to a few questions.

1. What version WAP54G? 1.0, 1.1, 2.0, or 3.0? There are
substantial internal differences. Firmware version?

2. Can you plug the test machine into the network using ethernet and
have the machine work? I'm trying to determine if the test machine is
totally functional. It probably is.

3. Have you tried using the WAP54G in the client mode and try
connecting to one of the other access points? That will test the
radio part of the puzzle which appears to be suspect. You can get a
good signal strength on the DWL520, but if the receiver in the WAP54G
is comatose, it won't connect.

Drivel: Five phone calls, 5 AIM messages, and 2 Skype calls, while
writing this message. Forgive me if my thinking is a bit erratic.

--
Jeff Liebermann jeffl@xxxxxxxxxxxxxxxxxxxxxx
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
.

Relevant Pages