Terminal server yet not ready - NComputing L230 Network Terminal

There were some issues with single core vs. multi-core processors with earlier versions of vSpace. Perhaps the two server/hosts you're using as a reference point are different in that one is single core, the other is multi-core. Regardless, my recommendation is to uninstall the vSpace software, reboot, run their cleanup utility, and reinstall the latest version. Before reinstalling, make SURE that you have applied any Service Packs and ALL of the current MS updates. Additionally, browse Device Manager and make sure there are NO missing or conflicting drivers. Do NOT, I repeat, do NOT install from the provided CD. As of this posting date, the cleanup utility is available here: nc-eng.com/tools/ncuninstall. The most up to date vSapce for L230 is on the NComputing download site. If you hit this post later and the supplied URLs are not valid call NComputing TS at 888-365-1210. Lastly do NOT forget to register the vSpace software.

Uninstall any current version of vSpace. Reboot. Makesure you have no missing or conflicting device drivers inside of devicemanager. Then run the NComputing cleanup utility located here:www.nc-eng.com/tools/ncuninstall.exe. Download current version for yourOS from the NComputing download site, install vSpace and reboot and register. Do NOT, I repeat, do NOT install from theprovided CD and upgrade. Simply install straight from the downloadfile I provided in the link. Lastly makeSURE you REGISTER vSpace. Be sure toenable the background hardware activation option. This is available on the last screen of theregistration or in the NComputing System console, under System Settings.

re-instal vspace software only - without license

It could be one of a lot of things but, sounds to me like your server hard drive is full or you have a memory problem with server..
I would suggest you get a network engineer to have a look at the server and system.
Hope this helps

This problem appear after u updated windows. U must update vspace with vSpace_4.05.002.03_for_Windows_L-Series. Register required and free on ncomputing sites, download and try...Itried it and solved this problem

check your server RDP policy in terminal server configuration,double click RDP permission tab,add user everyone,set full permission.

try to add users with password on your windows 2003 server first and test and see if this resolve your issue you c

Are you remoting into your server from a differnet location than where the server is? I need to know th physical location of the printer to the server. If the printer is connected to the server there is a problem with the driver. if the printer is connected to your local PC you will need to click on the options button in remote access and tell it you want to use local resorceses. If the server / Printer / PC are in the same location do not access the server thru terminal services, set it up as a client server.

Are you receiving errors in the "event viewer"? And if you are what are they?

I’m happy to assist further over the phone at https://www.6ya.com/expert/lou_afa492c634393790

Hello, Do you still need the solution? You can warm reset and exit the kermit mode, and then the download ur data using PTComm.