Teams stuttering all the time

[#1]

Not a problem @thetarpey

[#2]

I had great network performance in Friday working wireless all day, I thought the problems were resolved. Unfortunately this morning I could not get a stable 5g connection on my laptop and I struggled to resolve any website before disconnecting again. My phone also struggled with the wi-fi too.

I plugged my laptop onto the Ethernet and although the machine reported a connection I could not access any sites.

I rebooted the router and my access has been restored but I'm still getting the occasional DNS error. Event log here to see if you can see anything amiss.
 
Time and date
Message
08:32:11, 15 Nov.
OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 80.229.19.218-​>18.203.176.203 on ppp3)
08:32:05, 15 Nov.
IN: BLOCK [15] Default policy (TCP [199.232.142.248]:443-​>[80.229.19.218]:35978 on ppp3)
08:32:05, 15 Nov.
IN: BLOCK [15] Default policy (TCP [151.101.62.133]:443-​>[80.229.19.218]:52003 on ppp3)
08:32:00, 15 Nov.
IN: BLOCK [15] Default policy (TCP [199.232.58.133]:443-​>[80.229.19.218]:52023 on ppp3)
08:32:00, 15 Nov.
BLOCKED 2 more packets (because of Default policy)
08:31:59, 15 Nov.
BLOCKED 1 more packets (because of Packet invalid in connection)
08:31:58, 15 Nov.
OUT: BLOCK [15] Default policy (First packet in connection is not a SYN packet: TCP [192.168.1.170]:47758-​>[18.196.128.203]:443 on ppp3)
08:31:57, 15 Nov.
IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [13.35.193.171]:443-​>[80.229.19.218]:46730 on ppp3)
08:31:55, 15 Nov.
IN: BLOCK [15] Default policy (TCP [20.54.36.229]:443-​>[80.229.19.218]:61525 on ppp3)
08:31:52, 15 Nov.
IN: BLOCK [15] Default policy (TCP [199.232.142.248]:443-​>[80.229.19.218]:35978 on ppp3)
08:31:52, 15 Nov.
BLOCKED 3 more packets (because of Default policy)
08:31:52, 15 Nov.
IN: BLOCK [15] Default policy (TCP [199.232.142.248]:443-​>[80.229.19.218]:35978 on ppp3)
08:31:50, 15 Nov.
IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [13.227.150.112]:443-​>[80.229.19.218]:37986 on ppp3)
08:31:47, 15 Nov.
IN: BLOCK [15] Default policy (TCP [54.73.190.46]:443-​>[80.229.19.218]:49518 on ppp3)
08:31:45, 15 Nov.
IN: BLOCK [15] Default policy (TCP [20.54.36.229]:443-​>[80.229.19.218]:61525 on ppp3)
08:31:45, 15 Nov.
BLOCKED 2 more packets (because of Default policy)
08:31:43, 15 Nov.
IN: BLOCK [15] Default policy (TCP [199.232.58.133]:443-​>[80.229.19.218]:52023 on ppp3)
08:31:37, 15 Nov.
IN: BLOCK [15] Default policy (TCP [20.54.36.229]:443-​>[80.229.19.218]:61525 on ppp3)
08:31:37, 15 Nov.
BLOCKED 1 more packets (because of Default policy)
08:31:36, 15 Nov.
IN: BLOCK [15] Default policy (TCP [20.54.36.229]:443-​>[80.229.19.218]:61525 on ppp3)
08:31:36, 15 Nov.
BLOCKED 2 more packets (because of Default policy)
08:31:35, 15 Nov.
IN: BLOCK [15] Default policy (TCP [199.232.58.133]:443-​>[80.229.19.218]:52023 on ppp3)
08:31:35, 15 Nov.
BLOCKED 1 more packets (because of Default policy)
08:31:33, 15 Nov.
( 259.620000) Device disconnected: Hostname: PL004392 IP: 192.168.1.159 MAC: ec:79:49:3e:13:a1
08:31:33, 15 Nov.
IN: BLOCK [15] Default policy (TCP [23.55.19.155]:443-​>[80.229.19.218]:39818 on ppp3)
08:31:32, 15 Nov.
( 259.110000) Wire Lan Port 4 down
08:31:32, 15 Nov.
IN: BLOCK [15] Default policy (TCP [193.242.145.101]:40676-​>[80.229.19.218]:8007 on ppp3)
08:31:31, 15 Nov.
IN: BLOCK [15] Default policy (TCP [199.232.58.133]:443-​>[80.229.19.218]:52023 on ppp3)
08:31:31, 15 Nov.
BLOCKED 1 more packets (because of Default policy)
08:31:30, 15 Nov.
BLOCKED 3 more packets (because of Default policy)
08:31:29, 15 Nov.
( 256.340000) Lease for IP 192.168.1.158 renewed by host PL004392 (MAC fc:b3:bc:a8:dd:a6). Lease duration: 1440 min
08:31:29, 15 Nov.
( 256.340000) Device connected to ath10: Hostname: PL004392 IP: 192.168.1.158 MAC: fc:b3:bc:a8:dd:a6 via fc:b3:bc:a8:dd:a6 Lease time: 1440 min. Link rate: 866.6 Mbps
08:31:29, 15 Nov.
( 256.170000) Lease requested
08:31:29, 15 Nov.
ath10: STA fc:b3:bc:a8:dd:a6 IEEE 802.11: Client associated
08:31:28, 15 Nov.
IN: BLOCK [15] Default policy (TCP [216.58.212.227]:80-​>[80.229.19.218]:54500 on ppp3)
08:31:27, 15 Nov.
IN: BLOCK [15] Default policy (TCP [199.232.58.133]:443-​>[80.229.19.218]:52023 on ppp3)
08:31:27, 15 Nov.
BLOCKED 3 more packets (because of Default policy)
08:31:26, 15 Nov.
IN: BLOCK [15] Default policy (TCP [40.100.174.18]:443-​>[80.229.19.218]:39610 on ppp3)
08:31:26, 15 Nov.
BLOCKED 1 more packets (because of Default policy)
08:31:25, 15 Nov.
BLOCKED 3 more packets (because of Default policy)
08:31:24, 15 Nov.
IN: BLOCK [15] Default policy (TCP [151.101.62.133]:443-​>[80.229.19.218]:52003 on ppp3)
08:31:23, 15 Nov.
IN: BLOCK [15] Default policy (TCP [142.250.180.3]:80-​>[80.229.19.218]:39968 on ppp3)
08:31:17, 15 Nov.
IN: BLOCK [15] Default policy (TCP [159.65.101.124]:47090-​>[80.229.19.218]:9040 on ppp3)
08:31:16, 15 Nov.
IN: BLOCK [15] Default policy (TCP [172.217.169.3]:80-​>[80.229.19.218]:1049 on ppp3)
08:31:15, 15 Nov.
IN: BLOCK [15] Default policy (TCP [185.7.214.189]:41776-​>[80.229.19.218]:53368 on ppp3)
08:31:13, 15 Nov.
IN: BLOCK [15] Default policy (TCP [172.217.169.42]:443-​>[80.229.19.218]:44608 on ppp3)
08:31:12, 15 Nov.
IN: BLOCK [15] Default policy (TCP [142.250.200.3]:80-​>[80.229.19.218]:53542 on ppp3)
08:31:10, 15 Nov.
IN: BLOCK [16] Remote administration (TCP [108.21.227.2]:17713-​>[80.229.19.218]:80 on ppp3)
08:31:09, 15 Nov.
OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.94]:53125-​>[34.250.178.75]:443 on ppp3)
08:31:02, 15 Nov.
IN: BLOCK [15] Default policy (TCP [216.58.212.227]:80-​>[80.229.19.218]:54500 on ppp3)
08:31:01, 15 Nov.
BLOCKED 1 more packets (because of Default policy)
08:31:00, 15 Nov.
IN: BLOCK [15] Default policy (TCP [112.212.80.144]:37800-​>[80.229.19.218]:37215 on ppp3)
08:30:50, 15 Nov.
BLOCKED 1 more packets (because of Default policy)
08:30:49, 15 Nov.
IN: BLOCK [15] Default policy (TCP [142.250.200.3]:80-​>[80.229.19.218]:53542 on ppp3)
08:30:49, 15 Nov.
BLOCKED 2 more packets (because of Default policy)
08:30:48, 15 Nov.
IN: BLOCK [15] Default policy (TCP [172.217.169.3]:80-​>[80.229.19.218]:1049 on ppp3)
08:30:47, 15 Nov.
IN: BLOCK [15] Default policy (TCP [35.177.53.240]:443-​>[80.229.19.218]:54820 on ppp3)
08:30:45, 15 Nov.
BLOCKED 2 more packets (because of Default policy)
08:30:43, 15 Nov.
( 209.540000) Lease for IP 192.168.1.64 renewed by host SonyKDL43W755C (MAC ac:9b:0a:0e:8b:fe). Lease duration: 1440 min
08:30:43, 15 Nov.
( 209.540000) Device connected to eth0: Hostname: SonyKDL43W755C IP: 192.168.1.64 MAC: ac:9b:0a:0e:8b:fe via ac:9b:0a:0e:8b:fe Lease time: 1440 min. Link rate: 100.0 Mbps
08:30:43, 15 Nov.
BLOCKED 1 more packets (because of Packet invalid in connection)
08:30:43, 15 Nov.
IN: BLOCK [15] Default policy (TCP [172.217.169.42]:443-​>[80.229.19.218]:44608 on ppp3)
08:30:42, 15 Nov.
( 209.470000) Lease requested
08:30:42, 15 Nov.
( 209.440000) Wire Lan Port 2 up
08:30:42, 15 Nov.
IN: BLOCK [15] Default policy (TCP [142.250.180.3]:80-​>[80.229.19.218]:39968 on ppp3)
08:30:42, 15 Nov.
OUT: BLOCK [9] Packet invalid in connection (UDP [0.0.0.0]:68-​>[255.255.255.255]:67 on ath10)
08:30:41, 15 Nov.
IN: BLOCK [15] Default policy (TCP [216.58.212.227]:80-​>[80.229.19.218]:54500 on ppp3)
08:30:39, 15 Nov.
( 205.940000) Wire Lan Port 2 down
08:30:39, 15 Nov.
BLOCKED 1 more packets (because of Default policy)
08:30:38, 15 Nov.
IN: BLOCK [15] Default policy (TCP [142.250.180.3]:80-​>[80.229.19.218]:39968 on ppp3)
08:30:38, 15 Nov.
BLOCKED 4 more packets (because of Default policy)
08:30:37, 15 Nov.
IN: BLOCK [15] Default policy (TCP [142.250.180.3]:80-​>[80.229.19.218]:39968 on ppp3)
08:30:37, 15 Nov.
BLOCKED 2 more packets (because of Default policy)
08:30:36, 15 Nov.
IN: BLOCK [15] Default policy (TCP [64.233.167.188]:5228-​>[80.229.19.218]:59323 on ppp3)
08:30:36, 15 Nov.
IN: BLOCK [15] Default policy (TCP [64.233.184.188]:5228-​>[80.229.19.218]:57118 on ppp3)
08:30:34, 15 Nov.
BLOCKED 1 more packets (because of Default policy)
08:30:34, 15 Nov.
IN: BLOCK [15] Default policy (TCP [172.217.169.3]:80-​>[80.229.19.218]:1049 on ppp3)
08:30:31, 15 Nov.
IN: BLOCK [15] Default policy (TCP [142.250.200.3]:80-​>[80.229.19.218]:53542 on ppp3)
08:30:30, 15 Nov.
OUT: BLOCK [15] Default policy (First packet in connection is not a SYN packet: TCP [192.168.1.170]:37472-​>[151.101.18.219]:443 on ppp3)
08:30:29, 15 Nov.
IN: BLOCK [15] Default policy (TCP [142.250.200.3]:80-​>[80.229.19.218]:53542 on ppp3)
08:30:27, 15 Nov.
IN: BLOCK [15] Default policy (TCP [172.217.169.4]:443-​>[80.229.19.218]:42148 on ppp3)
08:30:27, 15 Nov.
BLOCKED 3 more packets (because of Default policy)
08:30:26, 15 Nov.
IN: BLOCK [15] Default policy (TCP [142.250.200.3]:80-​>[80.229.19.218]:53542 on ppp3)
08:30:24, 15 Nov.
( 191.360000) Lease for IP 192.168.1.170 renewed by host android-​dhcp-​11-​e6-​50-​61-​be-​41-​a3 (MAC e6:50:61:be:41:a3). Lease duration: 1440 min
08:30:24, 15 Nov.
( 191.360000) Device connected to ath10: Hostname: android-​dhcp-​11-​e6-​50-​61-​be-​41-​a3 IP: 192.168.1.170 MAC: e6:50:61:be:41:a3 via e6:50:61:be:41:a3 Lease time: 1440 min. Link rate: 6.0 Mbps
08:30:24, 15 Nov.
( 191.220000) Lease requested
08:30:23, 15 Nov.
( 189.730000) Lease for IP 192.168.1.170 renewed by host android-​dhcp-​11-​e6-​50-​61-​be-​41-​a3 (MAC e6:50:61:be:41:a3). Lease duration: 1440 min
08:30:23, 15 Nov.
( 189.730000) Device connected to ath10: Hostname: android-​dhcp-​11-​e6-​50-​61-​be-​41-​a3 IP: 192.168.1.170 MAC: e6:50:61:be:41:a3 via e6:50:61:be:41:a3 Lease time: 1440 min. Link rate: 433.3 Mbps
08:30:23, 15 Nov.
( 189.590000) Lease requested
08:30:23, 15 Nov.
IN: BLOCK [15] Default policy (TCP [199.19.226.209]:34773-​>[80.229.19.218]:81 on ppp3)
08:30:22, 15 Nov.
ath10: STA e6:50:61:be:41:a3 IEEE 802.11: Client associated
08:30:21, 15 Nov.
IN: BLOCK [15] Default policy (TCP [172.217.169.3]:80-​>[80.229.19.218]:1049 on ppp3)
08:30:21, 15 Nov.
BLOCKED 2 more packets (because of Default policy)
08:30:20, 15 Nov.
( 186.770000) Device disconnected: Hostname: android-​dhcp-​11-​e6-​50-​61-​be-​41-​a3 IP: 192.168.1.170 MAC: e6:50:61:be:41:a3
08:30:19, 15 Nov.
IN: BLOCK [15] Default policy (TCP [172.217.169.3]:80-​>[80.229.19.218]:1049 on ppp3)
08:30:17, 15 Nov.
ath10: STA e6:50:61:be:41:a3 IEEE 802.11: Client disassociated
08:30:13, 15 Nov.
IN: BLOCK [15] Default policy (TCP [74.125.133.188]:5228-​>[80.229.19.218]:38813 on ppp3)
08:30:13, 15 Nov.
BLOCKED 1 more packets (because of Default policy)
08:30:13, 15 Nov.
OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.94]:53125-​>[34.250.178.75]:443 on ppp3)
08:30:13, 15 Nov.
IN: BLOCK [15] Default policy (TCP [135.92.6.73]:443-​>[80.229.19.218]:55265 on ppp3)

[#3]

Hi @thetarpey,

I'm really sorry to hear that you're experiencing issues with your connection this morning. I've had a look at the account and our RADIUS logs aren't showing any physical connection drops, plus I haven't been able to detect any underlying fault conditions on the line when carrying out some testing. Had you been using a VPN by any chance when these issues occurred earlier today?

[#4]

Hi @TheMightyAJ , thanks for your help.

Yes, I was trying to use a VPN on the laptop. It's the first thing I would normally do.

It also seems to caused issues on my mobile, so I didn't think it device specific.

Can you offer any advice as to why the VPN might cause me issues? My software is very locked down, so I'm not sure what I might do.

Thanks again.

[#5]

Thanks for confirming this @thetarpey. There's potentially a couple different things at play here, so it's really a matter of trying sort out what's going on and respond to each problem. I think the landline fault we'd detected previously may have been coincidental to the main reason you've opened the thread, though it is good that it seems to have been sorted out now. Teams stuttering could be it's own issue and one way we could prove that would be by setting up another router in the property to see if the same DNS issues occur. As the router you're currently using is out of warranty, we're unfortunately unable to send out a replacement at this time. Do you have an old router spare from your previous provider, or one that you may be able to borrow temporarily for testing purposes?

[#6]

Hi @TheMightyAJ  Thanks again. No sorry I don't have another router any more. When I first raised these issues I was using a Ubiquiti AC-LITE as a wireless AP, but I recently threw it away. Before that I used a TP-LINK AC-750, again just as a Wireless AP but that also kept dropping connections and ended up getting the boot too. 

Is there an alternate router you would recommend? 

[#7]

I'm afraid I can't make any outright recommendations when it comes to 3rd party equipment, but there's been plenty of discussion about various pieces of hardware here on the forums over the years. If you can get your hands on a BT SmartHub, they're based on the same models as our routers are, so they're quite compatible. Just make sure that any router you attempt to set up is Fibre enabled and hasn't been locked down to another supplier. Hope that helps, but if you have any further queries, please let us know and we'll be happy to assist.

[#8]

Thanks I will have to look into that. How much is a new router from Plusnet? Is that not an option?

[#9]

@thetarpey A new Hub1 from PN is (IIRC) £99.00. However, if you can get your hands on a BT HH6 from an auction site, I understand they are between £10-£20 and perform better.

[#10]

Thanks for getting back to us @thetarpey

We sell a Hub One for £99.99 + £6.99 postage & packaging, but as you're still within contract I'll be happy to send you a new one free of charge (Waiving the postage fee as a goodwill gesture) if you'd like to give it a go?

[#11]

Thanks @Gandalf, really appreciate the offer. I' m planning on working from home for another few days this week, if it's ok I'd like to monitor it over the week before I make a decision. I had asked the router to reserve an IP address for my laptop, and I wonder if that was what caused issues yesterday trying to switch between wireless and wired. I have disabled that option now, and will keep a close eye on the performance. Thanks again for your help it's really appreciated.

[#12]

No problem at all @thetarpey, let me know how it goes.

[#13]

Hi @Gandalf, this is what I'm getting trying to connect to the 5ghz radio this morning on my work laptop. All other devices seem fine. The machine is reporting connected but no internet.

[#14]

Hi @thetarpey

Those logs just suggest your device(s) are disconnecting from the WiFi of your router.

Are your other devices connecting onto the 5GHz fine or are they on the 5GHz?

Also are you able to connect your laptop onto 2.4GHz and/or using an ethernet cable OK?

[#15]

Hi @Gandalf, I'm on Ethernet right now, I can't connect to either 2.4g or 5g. This is me trying to connect to 2.4g:

15:13:23, 18 Nov.	ath00: STA fc:b3:bc:a8:dd:a6 IEEE 802.11: Client associated
15:13:22, 18 Nov.	ath00: STA fc:b3:bc:a8:dd:a6 IEEE 802.11: Client disassociated
15:13:14, 18 Nov.	ath00: STA fc:b3:bc:a8:dd:a6 IEEE 802.11: Client associated
15:13:13, 18 Nov.	ath00: STA fc:b3:bc:a8:dd:a6 IEEE 802.11: Client disassociated
15:13:13, 18 Nov.	ath00: STA fc:b3:bc:a8:dd:a6 IEEE 802.11: Client associated
15:13:13, 18 Nov.	ath00: STA fc:b3:bc:a8:dd:a6 IEEE 802.11: Client disassociated
15:13:05, 18 Nov.	ath00: STA fc:b3:bc:a8:dd:a6 IEEE 802.11: Client associated
15:13:04, 18 Nov.	ath00: STA fc:b3:bc:a8:dd:a6 IEEE 802.11: Client disassociated

My phone is preferring 2.4g this afternoon. when it would normally show 5g. I can connect and get 57.6 Mbps wirelessly though.