Forum Discussion

Jamesatighe's avatar
Jamesatighe
Brass Contributor
Jul 24, 2020
This is interesting to read. So it is clearly an issue with the MSDRC process somehow not releasing the audio channel.

Be interesting to see what MS come back with as seems to be an issue with anything using audio connections in this way.
rpextech's avatar
rpextech
Copper Contributor
Jul 24, 2020

Jamesatighe Hi James.  The other thing i noticed yesterday.  I was having inconsistent results trying to reproduce the problem.  What i found was if i closed the remote app (which is running BigHand). I'm monitoring msrdc.exe using https://www.nirsoft.net/utils/cports.html current ports.  I can see after about 15 seconds that there are some additional connections that are made and dropped.  Then if i try and open the published app again after that, i'm prompted for credentials. I enter them, then it fails and BigHand audio does not work.  If you reopen before that 15 second window the problem doesn't occur and i'm also NOT prompted for credentials.  If you stay persistently connected. It doesn't seem to occur.  You can probably replicate the behaviour yourself, assuming its not some setting we have that's causing it.  Its like the remote host is somehow closing the connection and the client is not handling that correctly.

 

I think the reason we are seeing more of the problem at the moment is many users working from home with poor broadband connections. 

Resources