Wireless Access

Hello

We are having an issue with Microsoft Teams and Wireless.  When a user disconnects their laptop from a HP Dock with a wired connection, the laptop will automatically connect to our corporate SSID.  All is good and works except Teams. 

When a user attempts to send a message etc It will just stall and will not send.  Incoming messages will be received, just outgoing is not sending.  

Workaround has been to get user to restart laptop (Essentially start a new wireless session) . 

Anyone experience this?  It's strange as its just cropped up out of nowhere.  Wondering if adding into the roles and polices ALG for Teams would make any difference..

Troubleshooting steps taken-  Updated drivers for dock and laptops, updated BIOS.  Tried different docks, laptops, models etc.   Checked Firewall settings.  Tested different SSIDs.  Checked ClearPass Access Tracker.  Checked Mobility Conductor.

Aruba Mobility Conductor 8.10.0.15 LSR

-------------------------------------------

Instead of rebooting, have you tried disconnecting wireless adapter and reconnecting back again? If this works, it means you have a Stale session binding.

Check if possibly you have Teams running in TCP Fallback, which makes it a big headache for Teams to operate in NIC Change. In such cases, force/enable Teams UDP Only traffic.

Also, you can perform a quick test where you can disconnect the laptop from docking station and then run on cmd nestat -anob to check if Teams is still showing connections tied to the old NIC.

If yes, try to do only ipconfig /release & ipconfig /renew on wireless afterwards and check if it fixes the issue.

------------------------------
Shpat | ACEP | ACMP | ACCP | ACDP
Just an Aruba enthusiast and contributor by cases
If you find my comment helpful, KUDOS are appreciated.
------------------------------

Isn’t there a bug fix for Teams in 8.10.0.17?



Original Message:
Sent: Sep 16, 2025
From: shpat
Subject: RE: MS Team - Wireless Issue

Instead of rebooting, have you tried disconnecting wireless adapter and reconnecting back again? If this works, it means you have a Stale session binding.

Check if possibly you have Teams running in TCP Fallback, which makes it a big headache for Teams to operate in NIC Change. In such cases, force/enable Teams UDP Only traffic.

Also, you can perform a quick test where you can disconnect the laptop from docking station and then run on cmd nestat -anob to check if Teams is still showing connections tied to the old NIC.

If yes, try to do only ipconfig /release & ipconfig /renew on wireless afterwards and check if it fixes the issue.

------------------------------
Shpat | ACEP | ACMP | ACCP | ACDP
Just an Aruba enthusiast and contributor by cases
If you find my comment helpful, KUDOS are appreciated.
------------------------------

 saw a similar thread: https://community.arubanetworks.com/discussion/logonms-teams-problems-after-upgrading-to-81004-85105-on-sep-30
But didn't see a solution on it Yet.

------------------------------
Shpat | ACEP | ACMP | ACCP | ACDP
Just an Aruba enthusiast and contributor by cases
If you find my comment helpful, KUDOS are appreciated.
------------------------------

Original Message:
Sent: Sep 16, 2025 03:34 PM
From: nkuhl30
Subject: MS Team - Wireless Issue

Isn't there a bug fix for Teams in 8.10.0.17?




Original Message:
Sent: Sep 16, 2025
From: shpat
Subject: RE: MS Team - Wireless Issue

Instead of rebooting, have you tried disconnecting wireless adapter and reconnecting back again? If this works, it means you have a Stale session binding.

Check if possibly you have Teams running in TCP Fallback, which makes it a big headache for Teams to operate in NIC Change. In such cases, force/enable Teams UDP Only traffic.

Also, you can perform a quick test where you can disconnect the laptop from docking station and then run on cmd nestat -anob to check if Teams is still showing connections tied to the old NIC.

If yes, try to do only ipconfig /release & ipconfig /renew on wireless afterwards and check if it fixes the issue.

------------------------------
Shpat | ACEP | ACMP | ACCP | ACDP
Just an Aruba enthusiast and contributor by cases
If you find my comment helpful, KUDOS are appreciated.
------------------------------

True, there is a lot of discussion about Teams on this thread: hickups with latest LSR and SSR releases of AOS8 (8.12.0.3 en 8.10.0.14) | Wireless Access

-------------------------------------------

Original Message:
Sent: Sep 16, 2025 03:34 PM
From: nkuhl30
Subject: MS Team - Wireless Issue

Isn't there a bug fix for Teams in 8.10.0.17?




Original Message:
Sent: Sep 16, 2025
From: shpat
Subject: RE: MS Team - Wireless Issue

Instead of rebooting, have you tried disconnecting wireless adapter and reconnecting back again? If this works, it means you have a Stale session binding.

Check if possibly you have Teams running in TCP Fallback, which makes it a big headache for Teams to operate in NIC Change. In such cases, force/enable Teams UDP Only traffic.

Also, you can perform a quick test where you can disconnect the laptop from docking station and then run on cmd nestat -anob to check if Teams is still showing connections tied to the old NIC.

If yes, try to do only ipconfig /release & ipconfig /renew on wireless afterwards and check if it fixes the issue.

------------------------------
Shpat | ACEP | ACMP | ACCP | ACDP
Just an Aruba enthusiast and contributor by cases
If you find my comment helpful, KUDOS are appreciated.
------------------------------

Hi there,

Just in case its unrelated to the update.

If the laptop works fine when connected via Ethernet but not over Wi-Fi, the issue likely lies somewhere along the wireless path-from the laptop's Wi-Fi interface to the point where both wired and wireless connections converge (typically at the router or firewall).
Sectionalize, Localize, Isolate, Extract, Repair/Replace, Repeat. 

Here's a step-by-step approach to help isolate the problem:

1. Start with the laptop itself:
   Compare the settings of the Wi-Fi and LAN interfaces-look at IP configuration, DNS, WINS, and any protocol differences. This can reveal mismatches or misconfigurations.

2. Check the AP configuration:
   Ensure the access point is assigning the correct VLAN (or VXLAN) to the wireless client, similar to what the switch does for wired connections.

3. Verify the AP's uplink:
   Confirm that the AP is properly connected to the switch and that the switch port is configured correctly (e.g., trunk/access mode, VLAN tagging).

4. Inspect firewall policies:
   Make sure the firewall treats wireless and wired traffic consistently. If there are differences, especially for cloud services like Microsoft 365, ensure all required IPs and domains are reachable.

   Microsoft provides an API endpoint to regularly fetch the latest list of Microsoft 365 IPs and URLs:
   👉 Microsoft 365 URLs and IP address ranges: Microsoft 365 URLs and IP address ranges - Microsoft 365 Enterprise | Microsoft Learn
   

Good Luck and i hope this gets you closer to a solution.

Best Regards,
Valentin

Hello,

First, can you test the following steps before restarting your device?

By the way, are you using a proxy in your setup?

On the user side (Windows);
Immediately after disconnecting from the Dock, before restarting:
Command Prompt   = route print
Windows PowerShell = Get-NetIPInterface | sort InterfaceMetric
(Is the Wi-Fi interface the lowest metric? Are there any old virtual/NIC remnants?)

Windows PowerShell = netsh winhttp show proxy
Windows PowerShell = netsh winhttp reset proxy
(Is the WinHTTP proxy still there? (Teams often uses this.)

For DNS tests;
ipconfig /flushdns
Windows PowerShell = Test-NetConnection

Instead of restarting Teams, just apply the following when changing networks;
WinHTTP proxy reset/import;
Windows PowerShell = ipconfig /renew
Windows PowerShell = taskkill /IM ms-teams.exe /F

Are you using roles/ACLs on the Aruba controller?
If so, please check the following outputs: 

Controller cli = show user-table | include <ip or mac>
Controller cli = show rights <assigned_role>
Controller cli = show datapath session table user <user_ip>
Are 443/TCP and, if applicable, 443/UDP sessions visible? Check the state/age and hit values.
Controller cli = show ucc client | include <user_ip>
Is Teams/UCC classification occurring?

Check these and apply the above tests and observe when the problem occurs.
If the problem is resolved, please inform us.

-------------------------------------------