Hi, I use the 2X Webportal to access my application on my terminal from home etc. When I use the Webportal the Microsoft Easyprint driver isn't being used and so I can't print on my printers. Only the 2X Universalprinter is working and it's very slow. When I login to my terminal directly with RDP the Microsoft Easyprint drivers is working fine. Looks like a problem with the rdp version of the 2X client or something?! Maybe anyone can help me? Regards, Jurgen Weijer
Hi; Also we have ThinPrint. When I connect directly to the terminal the thinprint output gateway is working smooth! But; when I connect through 2X the ThinPrint printer is also not working Regard, Jurgen Weijer
Hi; We use both. When I puslish a full desktop the server is trying to create the printers like I use a legacy RDP version. So I get the odlschool eventid 1111 error. Printerdriver for printer XXXX not found. Where XXXX the printername like OKi B2200, Dell3110 etc. etc. When I connect directly with the same computer to the same server the printers are redirected fine with the easyprint driver. Best reagrds, Jurgen Weijer
Is the option toredirect printers from the 2x client enabled? 2X uses the same com object that MS are using. Please check the version information from 2X Client, by clicking on the client help and version control option in the menu. Check also the shell and control version from mstsc , right click on the title bar and select about.
Thanx for your reply! Yes; the printer redirection option is enabled. We use 2X client en server version 8.1(build 930) and control version 6.1.7600(80) Best regards, Jurgen Weijer ETB Automatisering
sounds like you have some settings not setup correctly, however try to set 2x connection to be in direct mode. i would start by using the windows client, then once it is solved, will move to the webportal again. also please starte the version you get in mstsc see previous post
Thanx for your reply again! When I set 2X in direct mode it's also isn't working; the strangest thing is that I noticed that it's working fine on a Windows XP client. In Direct, Gateway and SSL mode. Only when the client is a Windows 7 of Windows 2008 client the printers are only made if the terminal has it's local driver. Like you connect with an old RDP client. I also tried installing the 2X Application server on another test server. Same issues. I can't figure out which RDP version 2X is using when connecting through direct mode. When I show the properties of the mstsc.exe it is version 6.1.7600.16385 Best regards, Jurgen Weijer
the same rdp is used for all modes. The mode control how the data is passed but the data is the same. please contact support as from my testing everything worked as expected. make sure you are using the same user when you are doing your tests and that no GPO can effect these settings
