Wednesday, January 23, 2013

MS Remote Desktop and the IP Audio Driver

I have always preferred Microsoft Remote Desktop as a remote entry tool of choice.  It stems, I believe, from being lazy efficient, and Remote Desktop is always there.  There is even a Remote Desktop client application available for OS X.

The problem is that Remote Desktop by default likes to transfer the audio from the remote computer to the client computer. The Axia IP driver doesn't like this so much, thus using Remote Desktop to connect to sysrtems with driver in use for programs like iProfiler will cause the audio connection to the application to break in favor of sending the audio to the remote client.  Fortunately this is pretty easy to fix by setting some parameters in Remote Desktop before making the connection.

Remote Desktop Server

Enable Remote Desktop Connections on the target computer.
By default, any users in the Administrators group for the computer automatically will be able to make a remote connection now.

Remote Desktop Connection

The way to connect to a computer is with the Remote Desktop Connection application.  This app is a part of all Windows versions since Windows XP.  
To connect to a computer with the  IP driver, it is necessary to have the Remote audio playback feature set to "Play on remote computer." This can be found under the Remote Audio Settings under the Local Settings tab.

An even easier shortcut is to make a remote desktop protocol file for common computer connections.  This is a text file saved with a .RDP extension which can contain the specific parameters needed to connect to a remote system and leave the audio on the remote computer.

Here are default file contents:

screen mode id:i:1
connect to console:i:1
full address:s:

Change the IP address to the destination and then save this text file with a .RDP extension.

The window size can be adjusted to taste as needed.  Their is also a configuration to access the console session of a server which is good for administering Pathfinder Server login sessions.  This file will work with both the Windows client application and Mac OS X Remote Desktop.


  1. This comment has been removed by the author.

  2. What's your host OS, Windows 7? (or 8 as in the first screenshot?) Sadly this hack doesn't work in Windows Server 2008 R2, appears a reengineering of the driver might be needed to adapt it for kernel streaming and bypass the Windows audio APIs completely (like how Breakaway Live seems to do: Proving very frustrating to try and work around.

    1. My configurations are not hacks, but sanctioned connection configurations for MS Remote Desktop. As previously mentioned, I have never encountered an error connecting from XP, Win 7 or Win 8 to any operating system running the IP driver as long as audio is left at the source machine and a console session is initiated.

      Further support can be obtained by writing to

  3. I have never had any issue connecting from any OS to any OS, including Windows Server 2012. The Remote Desktop configuration may require unchecking "Network Level Authentication" to connect from an Operating System older than Windows 7.