Cannot ping WAP54G client mode APs

[genzel]

Hi, All.
I configured a network of 3 WAP54G and 3 computers connected to them. One WAP54G is AP. two other - AP clients.
Everything is good, i.e. I can ping any computer from the rest two ones, I can ping AP (WAP54G) from any computer also. But I cannot ping client AP WAPs, so I cannot remotedly manage them. Actually, they can be pinged but with terrible irregularity - one successful ping per ~300 failures.
My firmware version - 2.08
Linksys vers.2.
All firewalls removed, all Linksys's hardware reset.
Any ideas?
Thanks in advance, Alex.

 

[Gintarelis]

Hello,
did you find solution? I have the same problem.

Regards, Gintaras

 

[genzel]

I discussed the problem with Linksys. I seems to have no solution. I think that it is one of their numerous bugs.

 

[usatracy]

I also had same prob with 1 client and 1 access point. Can't ping to client. Worked on it for days to no avail.

I changed both ends to DHCP and that fixed it.

Only problem is that if the access point resets or is saved, the client must be rebooted to restore connection, needs a keep alive to be sent from the client to the access point so the client will reconnect if access point is rebooted or saved.

Opposite works, rebooting client will auto connect back to access point when both are DHCP, but not if access point is rebooted.

 

[genzel]

Thanks, but DHCP is not the option for me. I install the network between 7 buildings with Linksyss located inside unmanaged metal boxes. Each of them is connected to embedded data acquisition device. All the addresses have to be static. I tried to look for alternative industrial network adapters but to my surprise failed to find any. All the companies (Cisco, Netgear etc) manufacture only PCMCIA or PCI cards