Just set up my first standalone hp thin client. It has the advantage over the ncomputing devices that it doesnt require any special software on the central server like the ncomputing. It should lend stability, because it was getting harder and harder to keep vspace running either under linux or windows xp. Updates in xp tripped it up, and random failures occured all too often in the linux version.
The hp's are available for some pretty reasonable prices used. This one is linux based, and I am waiting for a win7 embedded one to try as well. The rdp client worked flawlessly with none of the keyboard mapping quirks of the ncomputing units. Win7 would give me the option of running rdp on a linux or windows server, as well as executing avimark locally, loaded off a server if necessary.
Have to get some miles on them to be sure.. But looks promising.
Tuesday, May 21, 2013
Wednesday, May 15, 2013
Oops spoke too soon on the ncomputing
They jumped up and bit me again today. They just couldnt get along with the cups printing system again, so... Shut em down, and the rest of the rdp sessions soldiered on perfectly all day. Sigh
Friday, May 10, 2013
My apologies to ncomputing
The ncomputing terminals kept logging out or hanging on their own neccesitating restarts to resolve it all.
The problem turned out to be network issues unrelated to ncomputing. Mediacom's dns server addresses once again exposed my network to a non local .local domain. The principal trouble that causes with ubuntu in a multi user setting is the ongoing resolution of the printers under CUPS. I had one computer on the network that had been set long ago to a fixed ip address and fixed dns server addresses that were different from the rest of the network. Go looking for printers attached to that one, and it was periodic choke time.
I set everything to a public dns server address, and the printing issues went away completely, along with the network instability that was kicking off the ncomputing devices. End result has been tremendous stability.
Looks like I am in this for the long haul now.
The problem turned out to be network issues unrelated to ncomputing. Mediacom's dns server addresses once again exposed my network to a non local .local domain. The principal trouble that causes with ubuntu in a multi user setting is the ongoing resolution of the printers under CUPS. I had one computer on the network that had been set long ago to a fixed ip address and fixed dns server addresses that were different from the rest of the network. Go looking for printers attached to that one, and it was periodic choke time.
I set everything to a public dns server address, and the printing issues went away completely, along with the network instability that was kicking off the ncomputing devices. End result has been tremendous stability.
Looks like I am in this for the long haul now.
Subscribe to:
Posts (Atom)