• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Remote Desktop, audio???

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

K1ll1nT1m3

Member
Joined
Nov 1, 2002
Location
KC. Mo
I have learned that The Windows Remote Desktop cannot play audio on the PC you are connected to. Does anyone know of a way around this? I am trying to setup a server ( controlled remotely ) that will play audio for my home theater. Thanks
 
Yeh, I just have the audio out going to the reciever ( s-video too ). I am controlling the server from another PC, via "remote connection".

It says on the Microsoft site that they did this on purpose. I get an error "Invalid driver or a confilct, or the device is in use", when I try to play audio on the server from the remote connection. I can play audio fine when I am directly logged into the server. All drivers are updated. Its a SoundBlaster Live PCI card on 2000 server. Thanks
 
I'm just trying to figure out what you are trying to achieve............
> Do you want to control/program your server remotely in order to hear the audio on your home theater?
> OR do you want to listen to the audio locally?
 
I want the Server to play audio through the theater. But it seems Microsoft has made Remote Management so that you cant play audio through the Remote connection.

Here is the error I get :
"Windows Media Player cannot play the file because there is a problem with your sound device. There may not be a sound device installed on your computer, it may be in use by another program, or it may not be functioning properly."

If I log onto the server directly, I can play it fine. Just not through through the Remote Connection from my other PC.

Edit: Here is kind of the same problem I am having. I cant get either workarounds to work in my case. :(
 
Last edited:
You need to remote control the server console then, and you need to install vncserver on your server, and the vnc client on your remote pc. RDP or remote desktop only provides a virtual remote desktop, and NOT remote control of the console. If you really 'need' to remote control your server desktop vs just walking up to the server console and queing up your toons' then you need VNC. Me, I just fire up my laptop, hooked to my theater (audio out blah blah) and queue up all the audio I want from my linux mp3 server in my basement - remote control, why? All my pc's map a drive to my linux mp3 server via samba and can listen to music on locally connected speakers, my laptop audio out is connected to aux in on my stereo reciever (home theater) No need for remote control. I could if I wanted, but it kinda pointless, I just walk up to my laptop and queue up want I want to lisent to.
 
Nevermind, I got it. Thanks for the help. I like VNC better.

Edit: ( in case you wanted to know ) I didnt want to hook up a monitor, keyboard and all that stuff on the server. I just have it stashed away. Now I can play Internet radio and stuff through the theater. Thanks again
 
Last edited:
I'm getting ready to do the same thig with my system. Glad you started this thread! :D
 
If you are running Windows XP or Windows Server 2003 on the box, you should be able to play the sound through it and control it remotely. When you use the Remote Desktop Client (mstsc.exe), click the "Options>>" button to expand the advanced options. Now click the "Local Resources" tab, and under "Remote Computer Sound", set it to "Leave at Remote Computer". This does work because I have done it before.
 
I tried it all. Microsoft set up Remote Connection so it wont play audio when you "leave at remote computer" ( I think it just does the desktop sounds ). For some reason, Media Player 9, Winamp or the OEM Media Player, wont work through the remote connection.

I did get it to work very well using Real VNC. Download the full version ( both in one ) and install the Server version on the Server, and the Client version on PC you are using. I set the server to start the Server Version at startup, so its on all the time ( i kind of had to, I use WOL ). Then if I want to connect to the server, I just start the Client ( listen ) version on my PC. It totaly takes over the Server. ( just like you were logged into it, not like a remote connection ) It works great, its not laggy like the Remote Connection is.

I tried Remote Connection on both 2000 Server and 2003 Server ( both evaluation editions ). I use both XP Home and XP Pro for my PC. I cant Remote Connection to what I want it to do in any combination of these OSs.
 
Back