Experiencing odd behavior when accessing shared files or protocols via Wi-Fi using Aruba WAPs; strange problem detected.
Experiencing odd behavior when accessing shared files or protocols via Wi-Fi using Aruba WAPs; strange problem detected.
Hey, so I run a small IT department for a small business (about 60 on staff) (roughly 20 computer clients working at any given time). So we had older cisco WAP561 wireless access points but they weren't necessary cutting it for our building size (very large couple of buildings); and Aruba offered us a good deal on 7 IAP-215's. I installed the 7 aruba access points and they are fantastic! Amazing speed, handles our clients well, great range, smart 2.4 - 5.0 allocation, but they have an issue and I haven't been able to resolve it. Last year I installed a synology nas rackstation on our server rack for our creative department. They love it and it's become second nature for them all to use it (they all use Mac's btw). Well, over wifi with the new aruba routers the smb shares from the nas will not show up in both Window's network discovery and Mac's shared discovery; the smb shares shows up instantly over any wireless networks from the old cisco access points. At first I thought maybe an internal dns issue? But on both mac and windows I can manually connect to the nas just fine with the hostname. On windows I can pin the nas in the file explorer, so windows users don't have to worry about the manual connection process. But in mac you can't "pin" network shares in the finder, so manual connects have to be done through there "connect to server" prompt; and this literally freaks everyone out. I have tried teaching and training everyone on how to do the manual connection on Mac but it's constant calls saying they forgot. I have done my best to just hardwire everyone, but it's not perfect; and some clients move around the buildings and wireless access is needed. And besides all that at the end of the day network discovery should be working no matter what. I posted about this on the Aruba Community Forums and they had no idea what was wrong.. and stopped responding. If anyone could shed some light that would be amazing. Here is our setup: Firewall/DHCP Server: Sonicwall NSA 2600 Switch: Cisco Systems WS-C3750G-48PS (3 vlans, main traffic is all on vlan 1 including the wireless traffic and the nas) (vlan 1: 192.168.1.1/24 ---- vlan 20: 192.168.20.1/24 --- vlan 40: 10.10.0.1/23) Wireless Access Points: Aruba IAP-215-US I attached two screens shots so you can kinda see whats going on; this is from a macbook pro. The wireless network "wildwood" is from the aruba wireless access point. The test 5.0 network is from the cisco wireless access point. The LochNasMonster is the synology nas. You can also see that over the Aruba router no devices will show up. Thank you in advance for any advice!
@leadeater is the sole member of the forum familiar with Aruba WAP. There could be others who haven’t spoken much yet. My Aruba knowledge comes from the 7005 controller acting as a gateway. For general details, do you have an Active Directory domain configured or are all accounts using local credentials?
Use Apple Profile Configurator to build a profile that links the network share and installs it across all Macs. This tool lets you set various useful settings. For Mac servers, consider installing Profile Manager; otherwise, the standalone app works well. https://support.apple.com/en-nz/apple-configurator You may need to adjust firewall rules in the Aruba controller interface—comparing Instant setup with a Mobility Controller is helpful, especially since I’ve mainly used managed APs through a controller but would check first.
I have an Active Directory domain configured on a Windows 2016 server, but only around 20 clients are connected to it. The remaining users have their own local credentials. Appreciate the update.