Clients Disconnected from file server when jumping between APs.

  • 1
  • Question
  • Updated 2 years ago
  • (Edited)
Users are connected to a file server on the local network.  They often walk around the building with their laptops connected to the file server.   Whenever their laptops change the Access Point they are connected to, the computer is disconnected from the file server.    Is this expected behavior?

To rephrase: Should users expect to be disconnected from the file server if their computer jumps access points due to them moving around the building? If not, what settings do we change to correct the problem.
Photo of phcranston

phcranston

  • 7 Posts
  • 1 Reply Like

Posted 2 years ago

  • 1
Photo of John Fabry

John Fabry

  • 28 Posts
  • 8 Reply Likes
Absolutely not.  They should roam without interruption. Here is a video that explains some of the roaming intricacies; https://www.youtube.com/watch?v=jq9mBMz-vyI&feature=em-subs_digest

In Aerohive you should turn off BANDSTEERING, enable K, V, and R if your clients can handle them, and ensure you have great coverage and capacity. Hard to help troubleshoot, look at the log files from client monitor to see what is happening.
Photo of phcranston

phcranston

  • 7 Posts
  • 1 Reply Like
thanks.  good information.  I'll look into those settings.   We have great coverage and capacity so I don't believe that is the issue.
Photo of phcranston

phcranston

  • 7 Posts
  • 1 Reply Like
we are using HiveManager NG.   I noticed under the "Neighboring Devices" section that there are no neighboring devices listed?   could this be part of the problem.  Should I add them manually?
Photo of John Fabry

John Fabry

  • 28 Posts
  • 8 Reply Likes
That is definitely an issue. The neighbor data bases cannot update. Unfortunately I have not seen that before so can't help fix it. Have you tried calling Aerohive or       opening a ticket through NG?
Photo of phcranston

phcranston

  • 7 Posts
  • 1 Reply Like
I have a ticket open with support.  I'm waiting to hear back.  I tried the option of adding the neighbors manually.   That worked in NG but when I tried to push out the delta update I'm getting this error.   

Device Update Failed: The CLI 'no interface wifi0 radio tx-power-control auto' execute failed, cause by: Unknown error.

Not sure what that means, but I'm going to try a full update tonight after hours.
Photo of John Fabry

John Fabry

  • 28 Posts
  • 8 Reply Likes
I had the same error yesterday when putting some radios in sensor mode. Pushed a complete config and it succeeded.