Brian Hancock wrote:
Hi Michael,Have you now got rid of using DP over a wan link? Is it all running well with Win2003? I presume you are using TAME on the server?
No. I am using the terminal server for our new thin client studying computers. We are running a Filemaker program and have deployed about 100 units over 5 locations. I have just been testing the DP database through the Terminal server and have not installed tame. So far in testing it has been working working without tame, but a couple of the testers said that running over the wan was faster than through the terminal server.
By the way, I find Linux clients connect very well to Terminal Server, (but I have forgotten the name of the client program to connect them.). Have you totally given up on Linux?
I have not totally given up on Linux but at this point after installing xp on all of the employee computers I am not working on it at all.
Also, does the environment variable %computername% resolve back to the client computer or does it resolve to the server name?
It resolves back to the server name. Thanks Michael
Regards Brian----- Original Message ----- From: "Michael Shadel" <[EMAIL PROTECTED]>To: "DataPerfect Users Discussion Group" <[email protected]> Sent: Tuesday, May 09, 2006 2:29 AM Subject: Re: [Dataperf] Printing on a Remote DesktopHi Brian, I am not sure what you mean.I am running a terminal server (win2003) without a domain controller and have locked down everything except shutdown and printers. I have set up a personal directory for each user as a place to store tmp files and installed a printer and shared it and am using net use lpt2 \\%computername%\sharedprinter. This is working great and the user does not have any rights other than running the dp database.Thanks Michael Brian Hancock wrote:Hi Jeff,On Windows you can redirect a local port to a shared Windows network printer, using the NET USE command, but in the case of Terminal Server where you would never grant a user administrator rights you can only readily and dynamically redirect a local printer port if it is not real, ie LPT1 and LPT2 are real even if they do not have connectors, they are often supported on the motherboard), so best to use LPT4 in the reports, to redirect NET USE LPT4 \\computer\printersharenameRemember with Terminal Server that DP is executing in the memory space of the server and not of the client, so if you want to use a local printer you are sharing in the opposite direction. So the server becomes the printer client, and your client becomes the printer server.Regards Brian----- Original Message ----- From: "Jeff Puhlmann-Becker" <[EMAIL PROTECTED]>To: "'DataPerfect Users Discussion Group'" <[email protected]> Sent: Sunday, May 07, 2006 9:31 AM Subject: RE: [Dataperf] Printing on a Remote DesktopI though DP only printed to a local prniter on a LPT1 or LPT2 port. Is this correct, or is there a way to get DP ro print across a network connection toa newwotrk printer? I'll try this other stuff when I am in the office on Monday. Thanks. Jeff -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Hancock Sent: Saturday, May 06, 2006 4:50 PM To: DataPerfect Users Discussion Group Subject: Re: [Dataperf] Printing on a Remote Desktop Hi Jeff, This article might help describe the Windows printing process,http://www.brianmadden.com/attachments/Brian%20Madden%20-%20Terminal%20Server%20Printing.pdfI have a feeling you might need a thirdy party product like Citrix, however you could try setting up shared printers on the client and then say use abatch file to redirect the local port to the network queue.eg Using MyClient and MyServer , create a printer shared on MyClient (NB keep share name to 8 chars or less), and give permission to the TerminalServer user. On MyServer use a batch file to start DP, (ie instance running on MyServer -Terminal server session) net use lpt4 \\Myclient\MyShare dp myStr.strand configure DP report to print to LPT4, do not use LPT1 or LPT2, or evenLPT3, as non-Administrators cannot remap a real local port. Since most systems do not have support for LPT4 it is reasonable safe.You might be able to use environment variables set in log in scripts tomanage the bactch file for multiple users, eg net use lpt4 %MyPrinter Regards Brian----- Original Message ----- From: "Jeff Puhlmann-Becker" <[EMAIL PROTECTED]>To: <[email protected]> Sent: Sunday, May 07, 2006 6:50 AM Subject: [Dataperf] Printing on a Remote DesktopHello, Fellow DataPerfect Users!We're using DataPerfect on Windows Server 2003. Almost everything worksgreat (especially with the Tame DOS addition I picked up here!) Our users log on to the server via a Remote Desktop connection. As I said, almost everything works...Users can do anything EXCEPT print reports from DataPerfect on their local printer. They can print any other documents from any Windows programsrunning on the remote desktop, so I know the connection to the local printeris good. I need a workaround to get DataPerfect to print directly to thelocal LPT1 port. Can anyone help me? Thanks. Jeff _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf_______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf_______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf_______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf_______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
