Tip: Run a free scan for common Windows errors ad

re: No sound on windows xp over remote desktop Wednesday, July 14, 2004 at 1:33 pm Posted by RC (4 messages posted) Problem solved. I believe this is an obscure bug in Windows XP. The problem, I think is that in some cases (perhaps just with this sound card or configuration), although a piece of hardware is "recognized" by the os, it's not functional until you log in at the terminal physically, which is what I did. I really pushed every configuration, reinstall of components, driver manipulation, etc. and nothing worked. When I finally pulled out the monitor, keyboard and mouse from the basement and reconnected them to the headless unit, then attempted to access the components directly (and not remotely), XP picked them up and now I can control the server's sound output remotely as well. Very satisfying to have this beast running the way I want it. -Rich. On Wednesday, June 30, 2004 at 8:44 pm, RC wrote: >I am running windows xp pro, up to date with patches and I cannot get the sound to >function. The system has no monitor or keyboard - I am accessing it from another >xp pro system via remote desktop. > >I have an onboard soundcard (Intel 82801AA AC'97 audio controller) that didn't >work despite everything I tried, so I purchased a soundblaster live card (model >SB0060US #SB0220) which unfortunately has not solved the problem. > >This is the problem: I cannot get the card to play (either) in any fashion. > They are both detected in device manager and drivers are up to date. However, in >Sounds and Audio Devices under control panel, under the volume tab it says >"No Audio Device". Under the hardware tab, however, both devices are seen, enabled, >and working properly. > >Sound Recorder gives the following error: > >Sound Recorder >Another application is playing audio. You can either interrupt the application or >wait until it is done. Then try using Sound Recorder again. >The record button is grayed out, there are no other apps running. > >Windows media player gives the following error: > >Windows Media Player Error >Cannot play back the audio stream; no audio hardware is available, or the hardware >is not responding. (error id is 0x80040256) > >Winamp will give the following error: > >DirectSound output v2.2.10 error >Bad DirectSound driver. Please install proper drivers or select another device in >configuration. Error code: 8878000A >I have tried selectively disabling, removing and reinstalling both cards without >success. Remote access is set to play sounds at the remote machine. > >I am pretty sure this is not a problem with the remote access, but I haven't borrowed >anyone's monitor and keyboard to verify it yet. > >Any ideas? It sounds like there's something confliing or windows won't recognize >or utilize the sound card for some reason. I'm stumped for now and could use some >help. Thanks for any thoughts. [Reply or follow-up to this message] re: No sound on windows xp over remote desktop Wednesday, July 14, 2004 at 7:45 pm Posted by RC (4 messages posted) Actually, problem was not solved, but now it is. I thought the problem was that the sound cards would not run when the box was headless (no monitor, keyboard or mouse). But the problem was that it would not use the sound card(s) when there had not been a local (at the physical computer) login since the last reboot. The workaround: Using Tweak-UI, I caused the machine to auto-login. Then, with the same account, I connect remotely through remote desktop. That way, everytime there is a reboot, the first login is a local one (auto-login) and then the box can be accessed remotely. It's important to use the same user account for auto-login and remote, because remote access on xp allows you to kick yourself off a local machine remotely without confirmation. If two different users were used, a confirmation dialog box would appear for the local (auto-logged in) user and getting no response (as the machine is headless) it would just keep telling you connection denied. This was an absurd problem that took me a while to fix. I hope this helps someone out there reading this. R On Wednesday, July 14, 2004 at 1:33 pm, RC wrote: >Problem solved. > >I believe this is an obscure bug in Windows XP. The problem, I think is that in >some cases (perhaps just with this sound card or configuration), although a piece >of hardware is "recognized" by the os, it's not functional until you log in at the >terminal physically, which is what I did. > >I really pushed every configuration, reinstall of components, driver manipulation, >etc. and nothing worked. When I finally pulled out the monitor, keyboard and mouse >from the basement and reconnected them to the headless unit, then attempted to access >the components directly (and not remotely), XP picked them up and now I can control >the server's sound output remotely as well. > >Very satisfying to have this beast running the way I want it. > >-Rich. > [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows XP Discussion Forum