Mobile Apps VMUG Mobile Apps VMUG Top Forums: vSphere NSX vSAN vCenter Fusion Horizon Workspace ONE vRealize Automation Workstation Skyline VMCloudOnAWS Error: You dont have JavaScript enabled.This tool uses JavaScript and much of it will not work correctly without it enabled.The summary of the problem is: Virtual printing from the vmware client using the printers of the host does not work, because no virtual printers are displayed at the client.
Thinprint Client Manager Professional 32Bit SP1Thinprint Client Manager Windows 7 Professional 32BitFirst some information about the system environment: The vmware player version is 6.0.3 build-1895310, the host OS is Windows 7 professional 32bit SP1, the client OS is Windows XP home SP3 (without network connectivity).
Latest VMWare tools with option virtual printing are installed and the TPAutoConnSvc service is running at the client. Thinprint Client Manager Serial Port 1A printer device has been added by the vmware setup using serial port 1 of the virtual machine, as as shown in the virtual machine settings. Accordingly to the device manager of the client (virtual machina) the COM1 port exists and is operational. The host PC has a default printer installed, which is also working without problems. I tried several things to get printing from the client using the printer of the host to work (setup a printer using the ThinPrint print port and the ThinPrint Output Gateway driver manually, enabled debug log for TPAutoConnect), but could not fix the following issue: c:ProgrammeVMwareVMware ToolsTPAutoConnect.exe -v -q -i vmware -a COM1 -F 30 ThinPrint AutoConnect component, Copyright (c) 1999-2013 Cortado AG, 8.8.774.1 Cant connect to virtual channel (5). This is the output of the command (as originally found in the registry of the client, with additional option -v for verbose output), which is used by ThinPrint to startup TPAutoConnect. ![]() Id:2652 INFNORM01h: VCRequest169 CLIENT Entering. CVCRequest 19.08.2014 11:19:01:328 Id:2652 INFNORM01h: VCRequest199 CLIENT Virtual channel DLL freed 19.08.2014 11:19:01:328 Id:2652 ERRNORM01h: TPACApp5145 CLIENT iResult COMMANDNOCONNECT, try next (continue) 19.08.2014 11:19:01:328 Id:2652 INFNORM01h: TPACApp5154 CLIENT No suitable client protocol found. Access check of the default printer: 1 Can you please give me advise, what can be done to fix the above issue -- Thanks in advance, regards Gerhard. Tried to change configuration of serial port 1 (COM1) first at host PC by assigning it to device name COM2. Then I changed the configuration of the first serial port in the virtual PC from COM1 to the first unassigned device name COM6. I changed this in the device manager using the advanced settings for this serial port. Now I expected another error because the printer device is still using serial port 1 of the virtual machine accordingly to the virtual machine settings, but got unexpectedly in the TPAutoConnect log: Trying Current Protocol with. After that I found the virtual printers and now I can print from the virtual PC finally as intended. What I learned is, that the serial port 1 of the virtual machine isnt necessarily the same as COM1 in that virtual machine. But this doesnt really explain, why virtual printer assignments suddenly works with COM6. Contact Us Terms of Use Privacy Accessibility Site Index Trademarks Help Feedback.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |