Greetings TeamViewer community
Recently we've begun having some puzzling issues at my company, that I'd like to run by you guys.
Setting the stage with some basic information:
Windows 10 22H2, spanning over different quality updates.
TeamViewer version info:
UI version: 15.47.2
Host version: 15.47.3
On all machines tested. All machines are the same make/model. Specifically: HP Elitebook 650 G9.
Same Windows versions, updates etc.
A user complained that, when connecting to any device via TeamViewer, he is met with the "Starting remote session" screen indefinitely.
Now, indefinitely could mean a number a things, but he's waited upwards of 20 minutes before aborting and trying again.
Now, I got the ID's of the machines he attempted to access. Worked just fine.
At first I thought maybe he was blocked in some sense from those teamviewer hosts, but this proved not to be the case. Instead, I decided to try and see if it is network related in one way or another.
I then proceeded to reset network settings on his PC, winsock reset, flushdns and so on, just to cover all my bases - within reason.
However, this would prove to not solve anything. Same issue.
So I connected to his ethernet drop, and attempted connection again. Lo and behold: Now I also had the "Starting remote session" screen indefinitely.
I waited no more than 5 minutes though, before aborting and trying via a wifi connection. This worked perfectly. I also tried via wwan/cellular connection. This also worked just fine.
Finally I tried both wifi and wwan on the users PC, and could confirm that this worked for him as well.
I created a ticket for our network team.
To my surprise though, the ticket got sent back to me with the explanation that the issue could not be reproduced on their end.
So I got a colleague to try and do the same things as I did: Connect to the same ethernet drop and connect to one of the devices. It worked perfectly for him.
So I thought: Maybe the issue has resolved itself, one way or the other?
I then connected my PC to the drop, expecting the issue to be gone... However it wasn't.
I'm at a loss right now
Do any of you great minds have any tips as to where I would go from here to get closer to the root cause?
I'm not a network guy, but I would be inclined to power on wireshark and try to see if there is anything here that could get tell me whats going on, but I'm worried I might be missing a much simpler answer.