Remote sound on thin client

Hi,
I'm not sure if this is the right board but I couldn't find anything for thin clients. OS is Win 7 embedded.
I've set up a RDP connection to a server and that starts up an application. When an error occurs like wrong username etc the app plays an error sound. We used to use Wyse terminals and those played the sound fine through the speakers but we've switched to HP 510's and 520's and they don't play the sound at all.
In connection manager Local Resources are set to bring sounds to this computer.
All locally generated sounds work fine.
Any advice?
Many thanks,
Wes

Now the parameter file comes up when I run the report using this this URL:
http://PR-apps-svr/dev60cgi/rwcgi60.exe/getjobid=87?server=PY20Repser
When I click SUBMIT QUERY, I recieve this error:
Error: The requested URL was not found, or cannot be served at this time.
Oracle Reports Server CGI - Reports Server name is not specified.

Similar Messages

T5325 Thin Clients losing remote desktop connection

My company just bought about 50 of these thin clients and they are setup to run an automatic remote desktop connection. I have the connection setup to auto start when the thin client is powered on and it just brings the user to a windows login screen. After they have logged in and leave their thin client to go on break sometimes it just brings them to a blank screen with an HP logo and the thin client has to be restarted to get back into the remote desktop, or I have to go into admin and restart the RDP connection. Any idea why this is happening? Is there a setting somewhere I need to change?
Any help would be great!

We are having this same issue and it is maddening. I have contacted HP on several occasions and I don't know if it is the language barrier or simple ignorance, but so far the issue is ongoing. I have looked high and low on the net and no one seems to be able to tell me why this is happening despite a number of plausible theories. We have a couple hundred terminals throughout the company which are spread across three servers none of which are close to congested yet.. However, the 10 or so t5325's we have are used specifically for digital signage. They run automated sessions that launch animated JAVA windows. They run great for the most part, but seemingly at random they will freeze in their tracks. The sessions drop from our terminal server and cannot be restarted remotely. After the units are power cycled they come back up directly and begin their sessions again. You can shadow these units (VNC) and the moment the display come on the unit closes the RDP session and reopens the same and start running again, odd behavior. I have tried changing session logout timers, disabling / enabling TCP settings, creating client-side refresh scripts, restarting the sessions at regular intervals via admin script, flashing BIOS and ThinPro OS to the current level, voodoo rituals, and pagan sacrifice. Yet, they still behave in exactly the same manner with no actions on my part having any apparent affect.. Currently, I am of the mind to purchase small all-in-one pc's to do the job. If anyone knows of any way to fix this PLEASE respond to this post.

Very choppy sound on t5570e Thin client

Hello dear HP support forum and forum gurus.
Our company bought approx 3 000 Thin Clients (t5570e) for a big organization in our country. The problem we encountered is associated with sound.
Every thin client connects to a Terminal Server /WinServer 2008R2/ via RDP (port:3389). Every RDServer configured identically.
Let’s take one site (biggest one) with 6 RDServers and 800-850 users. The strange things happens!!! On some RDServers (ok RDServrs hostnames: TS1, TS4, TS5) users can view videos on YouTube with perfect sound, but the same user on another RDServer of the same RDfarm can view YouTube video but with very choppy sound (not ok RDServrs hostnames: TS2, TS3, TS6).
I mentioned when user starts its RDP session and when RD Connection Broker redirected that user to ok RDServers HP Velocity tray icon on Thin Client became green. But when RD Connection Broker redirected that user to not ok RDServers, HP Velocity tray icon on Thin Client remains blue. Anyway, at a moment when I mentioned this behavior of HP Velocity tray icon on Thin Client, HP Velocity Server Side applications weren’t installed on any RDServer.
A few weeks ago I installed HP Velocity Server Side x64 on all RDServers. Now I see HP Velocity Tray Icon on my RDServer. I can even view IP Addresses of a thin clients that redirected to a RDServer. But the problem remains.
Now, when RD Connection Broker redirected a user to not ok RDServer, HP Velocity tray Icon became green but even after installing Server Side App, sound remains very choppy.
Please help me understand what the problem is?
Regards

Hi @vdadashzadeh ,
Welcome to the HP Support Forums! To get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial product. You can do this at http://h30499.www3.hp.com/hpeb/
I hope this helps!
Best,
Russ
I worked for HP.

HP 4320t Thin Client bios settings - way to set remotely?

We have a supply of HP 4320t thin clients all running Windows Embedded 2009 SP3 32-bit. Is there a way to push out BIOS settings to all of them? I've found here on hp's website that there is a "repset utility" that can accomplish this, but have failed in my endeavors to find a utility like this for the HP 4320t Thin Client.

Try to disable the Automatically synchronize with an Internet time server in Date and Time Properties.
Although I am an HP employee, I am speaking for myself and not for HP.
Say thanks by clicking the "Kudos! Star" which is on the left.
Make it easier for other people to find solutions, by marking my answer with "Accept as Solution" if it solves your issue.

LabVIEW license for terminal servers and thin clients (e.g. LTSP)

Does NI plan to provide a license agreement for terminal servers and thin
clients?
I've been told to purchase a multi-seat license. That doesn't make much
sense since the thin clients won't be accessing DAQ hardware. They're
just used for developing the LV source.
Comments/suggestions?

On Thu, 04 Nov 2004 13:43:58 -0600, jbrohan wrote:
> As far as I know it's the capability to edit the source code that NI has
Yes, this is a very good point. Quite a unique situation when compared to
text based languages. Keep in mind I certainly don't mind paying for that
but I see no need to pay for much of the other features - like running it.
This is certainly one of the other features you pay for with LV. Since
we never plan to run the app on the thin client, why pay for that
feature?
What we do is crank out source code on the thin clients. We then send the
source code to this wireless mobile DAQ station running WindowsXP. From
there we can roll it up to our clients' target systems. That machine is
used for debugging then compilin
g so it has its own LV Prof Dev license
installed on it. Also, it can be operated locally or remotely via remote
desktop (one user at a time).
I know it may sound strange but it works great. And as the NI Software
License Agreement(NISLA) specifies, we have separate licenses on all
machines that load LV into local memory. The thin clients load nothing
into local memory, hence no need for a separate license.
> I express myself clearly in the hope of guidance. I am a one man shop
Yes, this is understandable. Installing one license on multiple machines
is a big no-no. However, that is not what I'm trying to do. Take a peek
at the "Grant of License" and "Single Seat License" sections of the NISLA.
> You say "That doesn't make much sense since ..." One of my clients has a
Ha! How about this scenario: As wireless hardware (bluetooth, wifi)
becomes more common, perhaps NI will have a peer scanner on all PCs with
LV installed. That way if you get within 100 feet of a P
C with the same
LV serial number, you get locked out and it sends a small message to the
NI batcave.
Thanks for the response. I'm hoping NI chimes in soon.

Creating a thin client network in VMWare Workstation

I have recently been informed that many our customers have a thin client network in place using Microsoft RDP, Terminal Services / Remote Desktop Services.
What I would like to do is create a virtual thin client network using Server 2008 | Server 2008 R2 | Server 2012. What I am not certain of is how to emulate the "desktop" environments for the clients and how to configure VMWare to work with this type of network.
Is this possible?
I admit that I have never configured a TS before, so hopefully someone here has done this before and can provide some pointers.
I have been searching Google for information but so far have come up short. Perhaps my search criteria is wrong.
I have VMWare Workstation 10 and access to MSDN for a number of ISOs.
Thank you.
Dan

user12049849 wrote:
I have Oracle VM server release 2.1.5, IPTABLES is disable on both the VM Server host and client. I am able to ping the gateway from the VM Host; but, not from the VM client. I can't even ping the VM Host from the VM client or ViceVersa.
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif2.0vif2.0 is the connection between the bridge and your guest. It is connected to xenbr0
peth0
vif0.0
xenbr1 8000.feffffffffff no peth1
vif0.1
xenbr2 8000.feffffffffff no peth2
vif0.2
xenbr3 8000.feffffffffff no peth3
vif0.3
ethtool -i peth1
driver: e1000
version: 7.6.15.5ora-NAPI
firmware-version: 5.11-2
bus-info: 0000:25:00.1Why are you showing us information about peth1? Did you intend to connect the guest to it / xenbr1?
VM HOST:
# ping 10.1.1.1
PING 10.1.1.1 (10.1.1.1) 56(84) bytes of data.
64 bytes from 10.1.1.1: icmp_seq=1 ttl=255 time=0.812 ms
64 bytes from 10.1.1.1: icmp_seq=2 ttl=255 time=0.765 ms
64 bytes from 10.1.1.1: icmp_seq=3 ttl=255 time=0.885 msWhere is this 10.1.1.1 on your network? What is the relevance of this output?
>
>
The VM Client ifconfig shows eth0 configured correctly IP, MASK and Broadcast, then the loopback... nothing else. Route command shows the correct Gateway. Well, nobody is perfect, so maybe you can post the complete config for review? Maybe you used xenbr1 when you should be using xenbr0, or something like that. Saying that it's correct is not the same as showing us that it is correct.
- ifconfig -a on dom0 and domU
- route -n on dom0 and domU
- vm.cfg of the domU

Arch Linux as Thin Client, PXE, LTSP

Hey there all, been using Arch for about a year now, from Gentoo through Zenwalk, gotta say that Arch is bar none the best so far. I think it's the way that it doesn't try to hide the system internals through abstraction (where every distro has it's own abstraction methodology).
I'm thinking in the future that I'd like to do a network-wide deployment of "terminals" for a non-profit. I say "terminals" in because unlike a true thin client, the idea was to have PXE booting to NFS and using the local hardware more. I'm fond of the idea of centralizing system management to a single system installation, and using solid-state machines.
VNC, NX, RDP seem to be out of the question because I need clients to have native multimedia applications like the Flash plugin, and Skype. I could see audio and video redirection becoming a pain. But having the full installation on the client doesn't seem like the right thing to do because then I've got specific machines with specific problems that I'd have to diagnose. Virtualizing an entire OS session for each user would require a powerhouse server, and then we are stuck with a graphical redirection like VNC, NX, RDP. Linux Terminal Server Project really seems to be on track, they've got a great customization method, but again, they're using XDMCP and sending raw X data over the network.
I envision the clients as being mostly web browser-centric to interface with the necessary applications, and using software like Sun Global Desktop or NoMachine NX to connect to individual Windows applications on a Windows server when needed.
I'm looking at the Fit-PC2 as a possible thick-client solution. It's an Intel Atom based PC with an AMD Geode graphics solution, 512MB of soldered RAM, really low energy consumption.
The wiki doesn't seem to address having more than one client using an NFS-mounted root. If you have more than one client writing .pid and other /var files, this doesn't seem like a feasible idea.
So I suppose that the / has to be mounted in RAM, and only the static dirs like /usr /bin /boot swap are NFS imports?
At first the network would be homogenous, but if we add computers with differing graphics cards
So, in summary:
* Any clues on multiple clients using one NFS root?
* How to autoconfigure X.org and other differing hardware?
It sounds like a fun challenge, wondering if anyone else has tried anything like it.
Last edited by VitaminJ (2009-10-19 00:42:31)

I don't really know enough about this to offer any real advice, but as far as multiple machines using a single NFS root goes, you could look into mounting it on all your clients read-only, and using a union filesystem (eg aufs2, unionfs), such that you can use another partition (say on a ramdisk) to handle writes...
Just a thought

Make a test with thin client

Hi all,
I'm facing a strange boring problem. I've a tomcat runs a webapp that using thin client connects to a remote DB.
From about a week is not able to connect anymore. Java hangs and report this error:
java.sql.SQLException: Io exception: Connection reset
So I've no firewall and listener is correctly working. Telnet to listener is working.
Does anyone has a simple java class to run to make a connection test?
Thanks
Stefano

Use preparedStatement either like this
String query = update tableName set datefield= TO_DATE(?, 'YYYY-MM-DD HH24:MI') where id= ? ";
and setString(1, string);
or
String query = "update tableName set datefield= ? where id= ?";
and setTimestamp() or setDate () depends what you need in your date field .
Bets regads Alexey.

Monitoring an applet on a thin client from the server

Hello all,
I'm not even sure if this is possible or not, but here is what I would like to do.
I want to be able to monitor an applet running on a remote thin client device from the central server to determine if there have been any problems (exceptions, device failures, etc).
I'll be using java 1.5.0. If you require more info please let me know.
Thanks,

But would anyone know if there is a similar method for applets?
What makes you think you can't use that technique in an applet? Use that, and contact the server when there's an uncaught exception.
You'll probably want to report a number of caught exceptions too (unless you're really bad at handling exceptions).
Best bet is to use a utility class on your applet with a method like "logError(Throwable t, String message)" which will send the details up to the server, maybe output to the console, maybe even pop up a dialog. If you did this via an interface you could plug in different implementations and compound them if required.

Wyse Thin client not connecting to Windows 2008 R2 server

Configuration
SBS 2011 Server
Windows 2008 R2 server with Remote Desktop Services installed, License Manager installed.
WYSE WT3125SE thin clients with Windows CE 5
I setup the Windows 2008 with Remote Desktop Services and was able to successfully connect the Thin client. Then I installed the License Manger and applied my Open license using User Cals. Was able to login. Next day I get the following
error-"Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again" I still can connect fine from other machines even Windows Home Ed.
I remove license server and still was unable to connect. Built a second Windows 2008 R2 server with RDS on it. Was able to connect without issue. Pointed it to the first RDS server license manager and have still been able to connect with
the Thin Client. The thin client can rdp to the SBS server without issue in admin mode, can connect to RDS2 server but not RDS1 with the license manger. So my issue is with the license and so my question is what is it with the license server
running on that server that is keeping thin client from connecting. I even did a reload of RDS1 and tested connecting throughout the process and it worked up until I applied the license and then it stops. And then if I uninstall the license, rds, remove
from domain still not able to connect. Any help would be appreciated.

We had the same problem with older terminals after cloning a 2008R2 rds server and sysprep it.
The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error : Because
of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again"
After reading all of the postings about this issue and tried the reactivate solution of the license server,
I was sure that it had something to do with the x509 certificates that are generated the first time you connect to a valid license server.
What I did, I installed a new license server activate it but did not install licenses on it.
I pointed the defective rds server to the newly installed license server and deleted the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
Certificate
X509 Certificate
X509 Certificate ID
X509 Certificate2
Then reboot.
After the reboot all old terminals can connect fine again. As final step I pointed the rds server to the same license server as the other ones,
reboot and all worked fine.
So conclusion is that when you pont a rds server to a license server that has the new type of licenses on it it will generate the wrong x509 certificates
that are not supported by the older clients, by pointing it first to 1 without any rds calls on it, it generates the older x509 certificates which are compatible with the older rdp clients then the switch to new license server will then not regenerate the
x509 certs so it keeps working.
I hope this helps someone
This issue was driving me crazy so very happy that it is resolved now
Cheers Frits

Using SBO with Wyse Winterm S30 Thin Clients

I have a customer who is using Microsoft Terminal Services via Wyse Winterm S30 Thin cllents to access SBO over a VPN. We are experiencing excessive rolling (redisplay) when screens are refreshed. The problem is compounded if a Marketing Document contains multiple Text lines. We have two terminal servers, each with about 12 thin clients connected.
I would appreciate feedback from anyone with experience of using thin clients, regardless of brand.

Hi,
Thin clients normally have a low memory allocation on the video card (8mb to 16MB) so this can be a problem. Check to see if you can change this in the BIOS on the WYSE. If not connect at 256 Colours to reduce this. If you have pictures linked to products then their resolution will not be good but for SAP itself the difference is small. Also rename the SAPSS.AVI to .old if you have not already done so so that the splash screen does not come up when logging in.
In my multimedia testing on thin clients, unrelated to SBO, I found that both memory and processor power made a huge difference, which is contrary to thin client manufacturer claims. As an example I used a 200MHz/64MB TC for a flash application and sound was about 3 seconds behind the image and the image update would skip 3 to 5 frames when updating. Moving to a 800Mhz/128MB TC The frame refresh rate was almost perfect and the sound was only about 0.5 seconds behind. I would therefore test on a more powerful thin client to see if it improves performance.
The S30 is a 400MHz (rated @ 533 on performance by AMD). Try a 1GHz TC with the maximum Video memory you can find.
We are currently using VXL Itona 800Mhz/128MB and do not experience too much rolling but we are using 256 colours.
Hope this helps.

Microphone not working on sun ray 270 thin client

Hello
I"m trying to make headphone and microphone work on a sun ray 270 thin client for an browser (java) based application. Its basically a meeting room kind to application where people can talk with each other.
The Speaker and Headphone is working fine however mic is giving trouble. I tried to test it with /usr/dt/bin/sdtaudio but when i click on record it give an error saying could not set audio format. I tried gnome-sound-recorder as well but it says device could not be found. The device is getting created in /tmp/SUNWut/dev/utaudio directory and $UTAUDIODEV variable is also set properly.
Please tell me how to trouble shoot this problem.

Post what your environment looks like. What version of everything are you using?

Linux thin client

I have a dual boot Linux/NT 2k machine. On NT, I can connect using the Java thin client to a database running on NT 2k. The same code on Linux give me 'The Network Adapter could not establish the connection' error when I try to establish a connection. From Linux, I can ping the database box and telnet to the Oracle listener port on the database box. Anyone have suggestions?
thanks

Some of the new features of Windows Server 2008 Terminal Services, such as RemoteApp, require Remote Desktop Client (RDC) 6.0 or 6.1 on the client side. RDC 6.0 is currently available for Vista and XP only. When Windows Server 2008 is released, RDC 6.1 will be made available for these platforms as well. RDC 6.0 and 6.1 are not available for Windows CE, and will not be a part of the Windows CE 6 release.
The rdesktop project is Open Source so it might be extended at any time, but currently (as per http://www.rdesktop.org/) it is intended for "Windows NT Terminal Server and Windows 2000/2003 Terminal Services". Not for Windows Server 2008. This means it is compatible with RDC 5.x, not with RDC 6.x. Since Windows Server 2008 is compatible with older clients, rdesktop should be able to connect to it, but you will not be able to utilize the new features such as RemoteApp.
What this means is that in order to do application publishing on these platforms you will either have to continue using Citrix or alternatives such as Ericom PowerTerm WebConnect, Provision Networks VAS, 2X, etc. For more information about this see this: http://ericomguy.blogspot.com/2007/10/are-windows-server-2008-terminal.html

Fat Client and Thin Client

Hello, everyone
I am a newbie with websphere 5. I am wondering if anyone know fat clients(Swing GUI) work with websphere. I know thin clients(web-based interface) work with websphere. My scenario is like this and this is all experimental purposes:
I want to program a Swing GUI interface as the client that accesses the enterprise javabeans that is installed on websphere. So the Swing GUI is the client and Websphere is the server, which makes it a 2-tier Application. My question is basically, does websphere only work with web-based application or does it work with both desktop application clients and web-based application clients also?
Any Ideas?

Thanks, that's the kinda of straight answer I am looking for. I have been researching for this answer to this question for a long time and even posted several similar questions on Java forum, but no one seemed to have a straight answer. What I was thinking of programming is:
client/server program using websphere.
Client:
GUI interface using Swing that is just like a regular desktop application and not a web browser (I notice the most common application using websphere are web based applications like portals).
Server:
Using Websphere to accept connection when requested by the client and act as a bean container, which holds EJBs. The EJBs will connect to the database (mssql server) to pull data from.
Does this sound OK and can this be done using Websphere? I am using Websphere 5.
Thank you, I am just a newbie in j2ee, just trying to get started in this area of programming.

HELP!!! Does LabView support a thin client or dumb terminal (diskless workstation) type of deployment

Hello,
Does LabView support a thin client or dumb terminal (diskless workstation) type of deployment? I have a need to run LabView on some sort of dumb terminal / diskless workstation. If someone has deployed LabView in this matter, please provide me all the details on how this was accomplished (software, hardware, etc.)
Thanks

Sorry, can't call you.
My first suggestion has nothing to do with LV. It is simply connecting as a remote client to the windows server and controlling the windows session on the server.
My second suggestion involved writing a program which will contact the PLCs directly using Modbus and get the data from them. As mentioned, you can find some Modbus client implementations for LV by searching the web (or, if you have LV 8 and the DSC module, I think it should come built in).
My third was writing 2 programs - one would run on the server and one on the client\s. The server program would be responsible for sending the data to the client and the client would be responsible for interacting with the user and sending the appropriate messages to the server. I already gave you pointers on what to search for (the example finder can be found by going to Help>>Find Examples and the site can be searched from the box at the top of the page, but make sure you don't search just the forums).
In both cases, you would need to design the program and the interface for the user.
Wi-Fi also has nothing to do with LV and is simply a way to form a wireless network. Any mobile device would almost definitely have support for it and buying an access point to form the wireless network is easy and cheap.
To learn more about LabVIEW, I suggest you try searching this site and google for LabVIEW tutorials. Here, here, here and here are a few you can start with and here are some tutorial videos. You can also contact your local NI office and join one of their courses.
In addition, I suggest you read the LabVIEW style guide and the LabVIEW user manual (Help>>Search the LabVIEW Bookshelf).
Try to take over the world!

Remote sound on thin client

Similar Messages

Maybe you are looking for