User comments on ISPs
  >> Zen Internet


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | 2 | 3 | 4 | [5] | 6 | (show all)   Print Thread
Standard User Pheasant
(eat-sleep-adslguide) Fri 30-May-25 10:50:21
Print Post

Re: "Poor network quality" error reported by Microsoft Teams


[re: Fmrl] [link to this post]
 
To eliminate the dock, try another simple 1Gbps USB-C Ethernet adapter direct into the router. They’re a couple of quid on places like Amazon. Worth having for trouble shooting and/or spares.
Standard User Fmrl
(learned) Fri 30-May-25 10:56:48
Print Post

Re: "Poor network quality" error reported by Microsoft Teams


[re: Pheasant] [link to this post]
 
In reply to a post by Pheasant:
To eliminate the dock, try another simple 1Gbps USB-C Ethernet adapter direct into the router. They’re a couple of quid on places like Amazon. Worth having for trouble shooting and/or spares.


Thanks. I've also raised a ticket with our IT department so they can investigate too.

I'm also going to setup wifi on the laptop to see if that has the same problem.
Standard User Pheasant
(eat-sleep-adslguide) Fri 30-May-25 11:26:16
Print Post

Re: "Poor network quality" error reported by Microsoft Teams


[re: Fmrl] [link to this post]
 
You can also eliminate the Fritzbox (in testing) by placing a direct connection from the Surface to the CityFibre ONT by setting up a VLAN ID on whichever Ethernet adapter (via the dock or separate USB-C adapter).

If your still experiencing issues at that point then swap the Surface for another client device and re-test.


Register (or login) on our website and you will not see this ad.

Standard User Fmrl
(learned) Fri 30-May-25 11:56:42
Print Post

Re: "Poor network quality" error reported by Microsoft Teams


[re: Pheasant] [link to this post]
 
In reply to a post by Pheasant:
You can also eliminate the Fritzbox (in testing) by placing a direct connection from the Surface to the CityFibre ONT by setting up a VLAN ID on whichever Ethernet adapter (via the dock or separate USB-C adapter).

If your still experiencing issues at that point then swap the Surface for another client device and re-test.


I didn't know you could do that. Is the vlan id all that's needed to establish a connection?
Standard User Pheasant
(eat-sleep-adslguide) Fri 30-May-25 12:02:15
Print Post

Re: "Poor network quality" error reported by Microsoft Teams


[re: Fmrl] [link to this post]
 
Set the VLAN ID and regular PPPoE client setup and you should be good to go. Your machine will be directly visible on the internet so be careful.

Edited by Pheasant (Fri 30-May-25 12:34:07)

Standard User Fmrl
(learned) Fri 30-May-25 12:32:59
Print Post

Re: "Poor network quality" error reported by Microsoft Teams


[re: Pheasant] [link to this post]
 
In reply to a post by Pheasant:
Set the VLAN ID and regular DHCP client setup and you should be good to go. Your machine will be directly visible on the internet so be careful.


I've hit a bit of a snag as the device manager is locked down and it doesn't seem possible to change the adaptor settings anyway.
Standard User Pheasant
(eat-sleep-adslguide) Fri 30-May-25 12:39:43
Print Post

Re: "Poor network quality" error reported by Microsoft Teams


[re: Fmrl] [link to this post]
 
Do you have another machine /client device that you can test with that's not locked down? Otherwise it's over to your IT support people.

In the first instance, simply connecting directly to the Fritzbox should disprove any suspicion on your internal network, cabling, power-line adapters etc.

Docks can be problematic too. So if you can try a USB-C ethernet adapter without the dock in play, would be helpful.

Edit - for my post quoted above, it's actually a PPPoE client rather than DHCP for Zen if setting a direct client connection to the ONT (with VLAN ID of 911). My bad.

Edited by Pheasant (Fri 30-May-25 13:13:48)

Standard User Fmrl
(learned) Fri 30-May-25 13:23:37
Print Post

Re: "Poor network quality" error reported by Microsoft Teams


[re: Pheasant] [link to this post]
 
In reply to a post by Pheasant:
Do you have another machine /client device that you can test with that's not locked down? Otherwise it's over to your IT support people.

In the first instance, simply connecting directly to the Fritzbox should disprove any suspicion on your internal network, cabling, power-line adapters etc.

Docks can be problematic too. So if you can try a USB-C ethernet adapter without the dock in play, would be helpful.

Edit - for my post quoted above, it's actually a PPPoE client rather than DHCP for Zen if setting a direct client connection to the ONT (with VLAN ID of 911). My bad.


The other PCs won't have Teams installed. I've been trying to guess the bandwidth needed for a Teams screen share and then run packet loss tests but so far no issues reported so it could be Teams itself that's a bit too sensitive.
Standard User Pheasant
(eat-sleep-adslguide) Fri 30-May-25 13:36:55
Print Post

Re: "Poor network quality" error reported by Microsoft Teams


[re: Fmrl] [link to this post]
 
Have you run a loaded latency / buffer bloat test on your setup?

https://www.waveform.com/tools/bufferbloat
Standard User Fmrl
(learned) Fri 30-May-25 13:56:14
Print Post

Re: "Poor network quality" error reported by Microsoft Teams


[re: Pheasant] [link to this post]
 
In reply to a post by Pheasant:
Have you run a loaded latency / buffer bloat test on your setup?

https://www.waveform.com/tools/bufferbloat


I've been using https://packetlosstest.com/

I just ran bufferbloat and it returned a "C" (up to 200ms latency increase)
Pages in this thread: 1 | 2 | 3 | 4 | [5] | 6 | (show all)   Print Thread

Jump to