Remote Desktop/ZaraRadio/Server 2003.

C

CharmingNathan

Member
Hello,

I hope someone maybe able to help with this:

This maybe one worth posting to your forum!

In a nutshell, my issue is that I am unable to log into Windows 2003 Server via Remote Desktop and still have 2003 Server be able to detect its Sound Card.

I have literally spent all night, from around 2200 to 0530 hours, trying fixes and work-arounds, which vary from removing one's Sound Card drivers, and disabling then re-enabling the card, to leaving Media Player playing music to 'lock' the card into place for detection - none of it has worked.

I run my own server, including the streams, and wish to administer ZaraRadio remotely, but to be able to do this, Zara needs to be able to detect the server's own sound card, which it ONLY does when I physically log onto the Server itself, under Remote Desktop it only shows the R.D.P. option - which to be fair DOES work - but not with Zara detecting the 'proper' Sound Card.

Having researched this matter on the Internet, there seems to be no real 'fix' for this, and to be fair most of the solutions that are proposed are for those who wish to stream audio via R.D.P., which on my system DOES work, but Zara just sees the standard R.D.P. option; those posts that do mention something close to this problem, actually suggest that Micro$haft actually made both Server 2003 and 2008 function like this, which basically suggests that this is not a flaw but how it should work, and I should actually contemplate 'downgrading' the O.S. to X.P.

Any thoughts, suggestions would be greatly appreciated!

Thank you.
 
Having played around with this a bit, I can be more direct than I was with my original post, though, which should have read:

"How can I ensure my sound card can still be detected by Windows 2003 Server when using Remote Desktop, instead "Micro$shaft's R.D.P. Audio Driver" being the only option?"

Before I get accused of going totally off-topic, the reason I need to know this is so I can enable Zara Radio to run remotely, which I can't all the while it only detects the R.D.P. Audio Driver which the encoders don't detect.

I hope this makes some sort of sense?!
 
Just so those interested know...

CharmingNathan said:
Having played around with this a bit, I can be more direct than I was with my original post, though, which should have read:

"How can I ensure my sound card can still be detected by Windows 2003 Server when using Remote Desktop, instead "Micro$shaft's R.D.P. Audio Driver" being the only option?"

Before I get accused of going totally off-topic, the reason I need to know this is so I can enable Zara Radio to run remotely, which I can't all the while it only detects the R.D.P. Audio Driver which the encoders don't detect.

I hope this makes some sort of sense?!
Click to expand...

I haven't exactly found a solution to this issue, in as much it seems like it is 'proper' behaviour to have Micro$haft's R.D.P. Audio driver available during a remote session, though quite why it removes the other useful drivers is a mystery, however...

I have found er, well, it's not even a workaround, it's an alternative to Remote Desktop, which as it in my case, resolves all these issues, I thought it was worth passing the information on...it's called "Tight V.N.C."

Basically, it acts in the way that, in my opinion, Remote Desktop should, in as much as it logs you not into your own session, but how your Desktop would look if you actually physically logged into the machine.

Now, all I have to do is find Windows-based logging software that records average songs per hour and total listeners per month...any ideas?! ;-)
 
You must log in or register to reply here.
Top