INS

Hi,

The only reason I can think off is a defect cable or a problem with the cabling. Is the same connector used every time or did you used new connectors?

Furthermore I've checked your configuration files. I don't see failures but I can give you some advice to enhance your system.

1. You use 802.11h I wonder why you have chosen for this. Is it an outside application? Are all the channels available for 802.11a blocked by other systems?

2. Please choose a different alternative channel. Here I would advice zou to use channel 140.

3. Update your firmware to version 4.1.11. Do not use 4.1.18 because with this version the 802.11h channels are blocked. This is only temporarily.

4. You could check what happens with your connection if you change the MAC Mode of the Client to Layer2Tunnel. You don't use PN IO Traffic since your are talking about PUT/GET but you have a PN IO System in your HW-Config otherwise your BF2 LED won't lit up when the cable is gone.

5. Did you already exchanged the CPU's for a time to check or the behaviour is only there where the WLAN Client is involved.

6.I would love to get feedback when you solved the problem.

3. Thanks for the link.

4. Yes that's right, we don't have PN-IO so I have disabled it in the CPU already. Didn't mentioned; sorry

5. Yes I did. but that was for a couple of ours and did not help much as that time a huge amount of unsatisfied feedback have been given. Now we are in a much better position and we will also replace the CPU. Unfortunately the custome is not patient. And the problem occurs in periods of 1-5 days. You never know.

6. sure