Need Remote Desktop Viewer with Sound Support for CentOS 5.6
CentOSThis forum is for the discussion of CentOS Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So as said before; if you paid someone to build it (or bought it outright), then pay them to UPDATE IT. Simple. And if you cannot discuss it in public (which I find very hard to believe), then why post on a public forum?
Simple, the question is general enough so that it's not an issue. If you find that hard to believe, your problem.
Quote:
Again, you aren't paying attention to what you've asked or been told. No matter WHAT YOU DO, sound isn't going to work over remote desktop on what you're using. Real server, virtual, whatever...not going to work. Your original problem remains.
Nope, that has not been said. First, as I said before, sound WORKS. Second, there are current remote desktop solutions that would work, the question was if anyone knows one that might have this feature as far back.
Quote:
Still haven't said ANYTHING about the software, or how you're dealing with this now, or why this has SUDDENLY become an issue after so many years.
Why do you keep repeating this? As I said, sound IS working LOCALLY. The reason to virtualize is because the hardware is starting to fail, which I told you before. The reason for the remote viewer is to get to the GUI of the guest VMs.
Quote:
And lastly, if you're not the one making a decision you are certainly WORKING for those people, to whom you need to give advice. And if it's going to be about five years before this replacement, you will have ZERO CHOICE but to live with no sound for five years.
So you purchased the system; pay for maintenance on it and have them solve the problem. If it's this 'secret' production system that you paid top dollar for, the company that developed it will be happy to solve your issues...have you actually contacted them?
And since this is all 'secret', and you're planning on replacing all of this anyway, you must already have some ideas on who else to purchase from. Have you asked THEM? Because they want to make a sale....and will probably bend over backwards for a big opportunity. Either way, your problem is solved.
You really don't like to read answers. As I said, we plan to replace it, but this will take time. Not all systems are such that they can be replaced in a few weeks AND we do not have the manpower to do it all at once.
Quote:
No one is arguing about it...you have been told plainly, several times, that what you're after WILL NOT WORK with what you have. That's it....simple answer. You were also asked why sound is suddenly an issue after so many years, but haven't answered. When you provide zero information, you will get close to that back in answers; there may well be workaround, but without knowing anything about what you have/are doing now, we can't even suggest anything past "Run a long speaker wire from the server".
Interesting choice of words. YOU are the only one that categorically denies any possibility that such a program might exist. Which, unless you tried to find something similar once, I have difficulty taking at face value.
And again, I was not asking for anyone to solve my problem. I was asking if anyone knows a program with the given specifications. If not, FINE. I am not asking for more than that.
I will then need to rethink my virtualization solution.
Why do you keep repeating this? As I said, sound IS working LOCALLY. The reason to virtualize is because the hardware is starting to fail, which I told you before. The reason for the remote viewer is to get to the GUI of the guest VMs.
Can you please clarify a bit... sound works locally - understood. But it works when it is on physical hardware?
Does the sound work locally when server is running as a VM?
Quote:
Originally Posted by inscil
You really don't like to read answers. As I said, we plan to replace it, but this will take time. Not all systems are such that they can be replaced in a few weeks AND we do not have the manpower to do it all at once.
You have to understand that there was a failure somewhere right? after all the OS you are running was EOL 4-years ago!
Not disagreeing with you that not all systems can be replaced/upgraded at once. But someone in your IT shop has ignored this server for years... Only now it is a problem because hardware is failing.
Can you please clarify a bit... sound works locally - understood. But it works when it is on physical hardware?
Does the sound work locally when server is running as a VM?
It works on the VM too - but locally of course. However, going from here, I think I have found a solution. You can get sound out of a KVM/QEMU VM using spice. This does not work with CloudStack where I wanted to host the machines, but it might work in OpenStack. Another alternative is using VMWare which should also allow sound.
Quote:
You have to understand that there was a failure somewhere right? after all the OS you are running was EOL 4-years ago!
Not disagreeing with you that not all systems can be replaced/upgraded at once. But someone in your IT shop has ignored this server for years... Only now it is a problem because hardware is failing.
Of course. Problem is, in the sector I work in, hardware was generally used for 15-20 years or even longer. When they started switching to standard server hardware to run the software on, they did not consider that this would become a problem later on. In fact, how to handle this in future systems is an ongoing discussion. There is no contractor I know of that, in this business, provides updates (hence CentOS 5.6, not even 5.11). Updating ourselves where possible would take time as it must be ensured that the system behaves EXACTLY as before - meaning more people and (planned) system outages. Obviously, this is all solvable with money - but what isn't nowadays?
Simple, the question is general enough so that it's not an issue. If you find that hard to believe, your problem.
Not a problem at all.
Quote:
Nope, that has not been said. First, as I said before, sound WORKS. Second, there are current remote desktop solutions that would work, the question was if anyone knows one that might have this feature as far back.
You said it worked locally; we also told you that no, there isn't (still) one that works via remote going that far back.
Quote:
Why do you keep repeating this? As I said, sound IS working LOCALLY. The reason to virtualize is because the hardware is starting to fail, which I told you before. The reason for the remote viewer is to get to the GUI of the guest VMs.
And you still won't have one for an OS that old.
Quote:
You really don't like to read answers. As I said, we plan to replace it, but this will take time. Not all systems are such that they can be replaced in a few weeks AND we do not have the manpower to do it all at once.
Seems you don't like to read answers either. Your original question was answered quite some time back. Again:
Upgrade things
Don't, and live with no sound
That's it. Not going to work with what you have since it's too old.
Quote:
Interesting choice of words. YOU are the only one that categorically denies any possibility that such a program might exist. Which, unless you tried to find something similar once, I have difficulty taking at face value. And again, I was not asking for anyone to solve my problem. I was asking if anyone knows a program with the given specifications. If not, FINE. I am not asking for more than that.
Again: there is not. You've said you looked into several and they don't work...that is (and remains) the answer. Is there something that might work? Absolutely a possibility...however, it seems no one here knows about it. Seems as if you can't find it either.
Quote:
I will then need to rethink my virtualization solution.
You need to also check into other options; again, we know ZERO about your 'secret' environment, past CentOS 5.
The commercial version of RealVNC supports audio; they may have information about the legacy versions as well, so contact their sales folks; pricing just isn't that high, especially if it will keep the business running. Beyond that, there are options (again, no idea if they fit since we know zero about your environment):
xtightvncviewer MAY work.
qemu has an extension to VNC that allows audio; virtualize like that and it MIGHT (maybe) work.
Teamviewer may work (again, purchase)
Install/run paprefs and check "Enable network access to local sound devices". You can then tunnel audio elsewhere, even over SSH.
It works on the VM too - but locally of course. However, going from here, I think I have found a solution. You can get sound out of a KVM/QEMU VM using spice. This does not work with CloudStack where I wanted to host the machines, but it might work in OpenStack. Another alternative is using VMWare which should also allow sound.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.