Why is there no sound from a remote server?

Servers often have no audio hardware, so there is no playback device to redirect. Installing a virtual audio device gives the system an output that redirection can capture.

I enabled audio redirection and still hear nothing. Why?

Group policy may be overriding the session setting, the default playback device may be one that is not connected, or the application may be muted in the volume mixer.

Does remote audio use much bandwidth?

Enough that it is often disabled by default and sometimes dropped automatically on constrained links to protect screen responsiveness.

Can I hear the remote microphone as well?

That is a separate capability from playback redirection and is not always offered. Check whether your tool supports input redirection specifically rather than assuming audio covers both directions.

Troubleshooting · 5 min read

No audio in a remote session: how to get sound working

Written for: Operators troubleshooting media, conferencing or alert sounds that do not come through a remote session.

In short

Remote audio fails for one of four reasons: redirection is switched off, the remote machine has no playback device to capture from, the wrong output is set as default, or the application's own volume is muted in the mixer. Headless servers are the notable special case — with no sound hardware present there is nothing to redirect until a virtual audio device is installed.

Key takeaways

Audio redirection is often off by default because it costs bandwidth.
A headless machine with no sound hardware has nothing to redirect; a virtual audio device solves it.
Windows can route audio to a disconnected device that still shows as default.
Per-application volume in the mixer is muted more often than the system volume.
Some tools suppress audio automatically on constrained links to protect responsiveness.

Confirm redirection is enabled

Audio redirection takes the sound the remote machine would have played and streams it to you. It uses continuous bandwidth, so many tools and administrative policies leave it off by default, particularly for support sessions where sound is rarely needed.

Check both the session setting and any group policy governing it. Policy commonly overrides the per-session preference, which produces the confusing situation where the toggle is on and nothing happens.

Is there anything to capture?

Servers, virtual machines and thin clients frequently have no audio hardware at all. Windows shows no playback device, applications fall back to silence, and there is nothing for redirection to forward.

Installing a virtual audio device gives the operating system an output to render into, which redirection can then capture. This is the same pattern as the virtual display driver used for headless screen capture.

Default device and mixer state

Windows will happily keep a disconnected monitor's HDMI output or an unplugged headset as the default playback device. Audio then goes somewhere real but inaudible. Open the sound settings on the remote machine and confirm the default is the device you expect.

Then check the volume mixer rather than just the master volume. A single application muted in the mixer is the most common cause of 'the machine has sound but this program does not'.

Default playback device set to something actually present
Per-application volume in the mixer, not just the master level
The application's own internal mute control
Exclusive-mode applications holding the device and locking others out

Bandwidth-driven suppression

On a constrained link, some tools drop audio deliberately to protect screen responsiveness — the right trade for support work, and confusing if you do not know it is happening. If audio works well on a good connection and vanishes on a poor one, this is the likely explanation.

Where sound genuinely matters for the task, look for a quality setting that prioritises audio, and accept the effect on the visual side.

Frequently asked questions

Why is there no sound from a remote server?: Servers often have no audio hardware, so there is no playback device to redirect. Installing a virtual audio device gives the system an output that redirection can capture.
I enabled audio redirection and still hear nothing. Why?: Group policy may be overriding the session setting, the default playback device may be one that is not connected, or the application may be muted in the volume mixer.
Does remote audio use much bandwidth?: Enough that it is often disabled by default and sometimes dropped automatically on constrained links to protect screen responsiveness.
Can I hear the remote microphone as well?: That is a separate capability from playback redirection and is not always offered. Check whether your tool supports input redirection specifically rather than assuming audio covers both directions.

How this works in 247connect

247connect prioritises session responsiveness on constrained links, so where audio matters for the task it is worth checking the quality setting rather than assuming redirection has failed.

Start a 14-day free trial See the feature list