White_Fi

I see Mark is wearing his see through shirt again!

OK so 5 clients is nowhere near the 25max when TKIP is used. I would suggest creating a separate SSID using WPA2 AES. Use this SSID as a test SSID for the , when you experience this problem again try connecting to the AES SSID and see if the client connects. The TKIP algorithm when used with WPA has some vulnerabilities in it, one of which were unknown bytes in the beacon broadcast can be responded to "unwillingly" by nearby 802.11 speaking devices even if they are connected to an entirely different network. This is rare however it basically just closes the SSID up from being used. This can be used by an attacker to start locally brute forcing the password, hence we always suggest WPA2 AES. Stuart

Ok so you are on the latest build which is a plus. When you say the clients cant connect, are there already a number of clients connected to the AP? if so how many? Is the Transmit power on the AP's set to auto? As well as the channel selection? Stuart

Hi, Could you tell me what version the ZD is running? Also what encryption method and algorithim is the SSID using? Kind Regards Stuart

Badders, we have updated your ticket on our support site

8.2.0.1.8 was released to support the new 73XX AP models. I believe it has been removed due to 8.2 MR1 being uploaded soon. Stuart

Under Monitor - Currently Active Clients find the client you wish to test and hit the speed dial icon (orange) far left of the client info. A new window will appear. Hit Start. Hit Ok on the popup box. Select MAC Intel or Windows. Run the SpeedFlex.exe and hit start again.

Let me start again! Have you tried running a speed TEST from the ZD after the issue occurs?

Simon have you tried running a speed on the ZD after it failed?

Yes ther is currently a thread regarding N130 and Ruckus. We have an active case open with Ruckus to investigate. We can not say it is a problem with either the AP or the Client as of yet but Ruckus are investigating into the Realtek driver the notebook uses.

Ok i hvae updated your support ticket with us. I would like to set up an online meeting to view the ZD set up. Please resond over at our support site. Regards Stuart

Simon are you using captive portal or D-PSK at all?

Driver upgrade to the latest should give you the roaming setting.

Yes, wireless chipsets do tend to have more sensitive roaming aggression these days. Ruckus is addressing the problem with these over sensitive clients roaming aimlessly with a control called bandstreering due for release in 8.2, 5-6weeks

Hi Simon i have posted back to you.

Guys do this LTs use the same wi-fi card?

Simon it is very unlikely that any wireless AP would be stopping a client from saving work on a server. It sounds like it could be down to a configuration or an ACL somewhere on your network. Is the client able to ping the server? Can you try to telnet to the server from the client on the port used for filesharing, 139 or 445 i think (you will need to double check this).

Yes you would you use the ZD to create a Layer3-4 ACL an attache that to the SSDI in question. Regards Stuart

@cookie_monster i have sent you an email to download the update files directly from us.

No, to update the Ruckus APs you would update the firmware on the ZoneDirector, (Central management). The ZD will then push the firmware out to the APs. If you are running APs in a standalone environment, very rare and not recommended if you are using multiple APs then the AP updates in different ways, either web, hence the need for proxy authentication if required or TFTP. Regards Stuart

You cannot enter proxy details into a zd

Can you please confimr you email address with me over PM. If you are going to have a multiple Access Points i strongly recommend getting a ZoneDirector to manage the APs. not only does it make the update process of the APs effortless you gain allot of features such as Mesh and roaming. Thanks

These update files are for ZoneDirectors and APs being managed by ZoneDirectors, not standalone APs.

You are unable to enter proxy details. I suggested moving the AP to another connection, with no proxy server to do the update from the fwupdate servers. Perhaps taking the AP home for an hour or so. Again, as specified in the email, this will be allot quicker / easier than grabing the update files and jumping from V 3 - 6 - 6 -7.1 - 8

Thanks Simon, Edu-IT i will get the link fixed on the Ruckus website. Stuart