[
https://issues.apache.org/jira/browse/GUACAMOLE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17101166#comment-17101166
]
Carlo Grossman commented on GUACAMOLE-296:
------------------------------------------
Thanks for the quick reply. I just spun up a Guac 1.1.0 on CentOS 7 (thanks
ZeroCoolX script). Using an RDP connection to the same exact Win 10 computer-
in Guac 1.2.0, it works perfectly. In Guac 1.1.0, the browser asks for me to
allow use of the microphone, I can see the Remote Audio on the Recording tab of
the Sound control panel app, but the meter doesn't move. I tried recording
using Sound Recorder, and there's no audio.
> RDP audio input cause disconnection on Windows Server 2012 / 2016
> -----------------------------------------------------------------
>
> Key: GUACAMOLE-296
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-296
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
> Affects Versions: 0.9.12-incubating
> Reporter: Hisham
> Priority: Major
> Labels: audio
> Fix For: 1.1.0
>
>
> I know this problem was discussed in resolved thread, but it is a bit
> different, please help me, I tried every thing I was able to find about the
> topic.
> On Windows Server 2012 R2: Audio playback works, but the minute I start
> Sound settings in the "Recording" tab the connection gets disconnected
> immediately. After that it is impossible to connect to the VM with guacamole,
> because it keeps disconnecting immediately, the only why is using a RDP
> client, and closing the Audio settings.
> this are the log info:
> May 8 10:19:27 ip-172-31-20-3 guacd[14887]: Loading keymap "base"
> May 8 10:19:27 ip-172-31-20-3 guacd[14887]: Loading keymap "de-de-qwertz"
> May 8 10:19:27 ip-172-31-20-3 guacd[14887]: guacsnd connected.
> May 8 10:19:27 ip-172-31-20-3 guacd[14887]: guacdr connected.
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: Connected to RDPDR 1.12 as
> client 0x0002
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: Ignoring server capability set
> type=0x0001, length=44
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: Ignoring server capability set
> type=0x0002, length=8
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: Ignoring server capability set
> type=0x0003, length=8
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: Ignoring server capability set
> type=0x0004, length=8
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: Ignoring server capability set
> type=0x0005, length=8
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: Sending capabilities...
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: Capabilities sent.
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: Client ID confirmed
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: User logged on
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: Sending filesystem
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: Registered device 0 (Guacamole
> Filesystem)
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: All supported devices sent.
> May 8 10:19:28 ip-172-31-20-3 guacd[14887]: Device 0 (Guacamole Filesystem)
> connected successfully
> May 8 10:19:37 ip-172-31-20-3 guacd[1183]: Connection
> "$70610038-ba7e-4e1d-9103-1b870c0cb079" removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
