In reply to a post by Fmrl:

In reply to a post by jpm:

Wait if this is a laptop why haven't you just picked it up and moved it?

It's connected to a monitor, keyboard, and mouse via a docking station.

Be honest are you really looking for a resolution to this issue as I am doubting you are.

I'm out, you're not interested in fixing this

In reply to a post by jpm:

I'm out, you're not interested in fixing this

I think I will join you as I have lost count of the good suggestions the OP has received but they have pooh-pooed them all off and claiming they are still investigating.

In reply to a post by DFScale:

The upshot of this is that, for both Zoom and Teams, you look at the upstream capability and 10Mb/s is probably adequate, per channel. If Teams or Zoom are not working adequately on a link with 20Mb/s upstream, this indicates looking at other factors than the raw speed, such as latency on the ISP connection or in house issues such as powerline connectors.

I don't think many people appreciate that power-line adapters, on the actual power line interface are NOT full duplex devices. They are only half duplex.

So in a situation where there is a concurrent demand, in realtime, without laginess and artefacts - like I dunno a multiple person teams or Zoom call with screen sharing thrown in 😅. then these wondrous devices, may struggle. That's before we consider any other electrical noise, garbage etc on the line.

It's like networking with modern moderately high-bandwidth apps but reverting to half-century old CSMA/CD half duplex ethernet technology on rusty fencing wire.

I think I've sufficiently made my point now in this thread wand will likewise gracefully bow out.

Good luck OP.

In reply to a post by PCJM40:

In reply to a post by Fmrl:

In reply to a post by jpm:

Wait if this is a laptop why haven't you just picked it up and moved it?

It's connected to a monitor, keyboard, and mouse via a docking station.

Be honest are you really looking for a resolution to this issue as I am doubting you are.

Strange thing to say, if I wasn't bothered about finding a fix then I wouldn't have started the thread.

In reply to a post by jpm:

I'm out, you're not interested in fixing this

Okay, thanks anyway.

In reply to a post by PCJM40:

In reply to a post by jpm:

I'm out, you're not interested in fixing this

I think I will join you as I have lost count of the good suggestions the OP has received but they have pooh-pooed them all off and claiming they are still investigating.

Okay, thanks anyway.

In reply to a post by Pheasant:

I don't think many people appreciate that power-line adapters, on the actual power line interface are NOT full duplex devices. They are only half duplex.

So in a situation where there is a concurrent demand, in realtime, without laginess and artefacts - like I dunno a multiple person teams or Zoom call with screen sharing thrown in 😅. then these wondrous devices, may struggle. That's before we consider any other electrical noise, garbage etc on the line.

It's like networking with modern moderately high-bandwidth apps but reverting to half-century old CSMA/CD half duplex ethernet technology on rusty fencing wire.

I think I've sufficiently made my point now in this thread wand will likewise gracefully bow out.

Good luck OP.

I do understand the limitations of powerlines, I've had them for about 10 years now and I've been using Teams for at least 5 and never had any issues. This problem has only started happening in the last couple of months and only affects Teams screen sharing so I've been investigating what's changed recently, namely...

Fritzbox updating from 7.59 to 8.00 and then to 8.02 - the reason why I started the thread (looks like this has been a waste of time)
Windows 11 updates
Teams updates

I'll continue to investigate.

The logical way to problem solve this is to go back to a minimal setup that removes any extraneous elements. That is what we’ve all been trying to say…

Connecting directly to the router eliminates a major cause of these issues - your internal network.

If the issue persists then you know the problem definitely is either the ISP connection itself (including router) or your laptop. From there it’s possible to further eliminate one potential cause from the other, by a process of logical elimination.

Just saying your “investigating” is meaningless without context of what you’re doing / have done. And we all go around in circles.

In reply to a post by Pheasant:

The logical way to problem solve this is to go back to a minimal setup that removes any extraneous elements. That is what we’ve all been trying to say…

Connecting directly to the router eliminates a major cause of these issues - your internal network.

If the issue persists then you know the problem definitely is either the ISP connection itself (including router) or your laptop. From there it’s possible to further eliminate one potential cause from the other, by a process of logical elimination.

Just saying your “investigating” is meaningless without context of what you’re doing / have done. And we all go around in circles.

At the moment I'm focusing on the docking station as it's a universal type connected via USB-C. I've noticed since one of the WIndows updates a while back that it sometimes loses sync with the monitor so that might indicate a communication problem on USB (so nothing to do with the Fritzbox or LAN).

I've also been running packet loss tests on the Surface PC, a Windows 10 laptop connected to the Fritzbox, and a Lubuntu desktop via homeplugs. No indication of any problems so far.

I've not ruled out the homeplugs so I'll try connecting direct to the Fritzbox at some point.