Remote Desktop Printing (Documents don't print completely)

Have been using Citrix Metaframe Login to reach a Windows SBS which hands us off to a SQLSERVER where our software resides.  Although that method is still available, we've begun using (testing) Remote Desktop Connection to connect to Windows 2003 SBS Terminal Services to reach the same SQLSERVER.  When using the second method, we've found that reports generated in our software do not print completely to the pages generated by our Client PC's local printer - HP 1300 Laserjet.  More importantly, on occasion when printing checks from the A/P module or Payroll module of our software, the routing number and/or account number will not print at the bottom of the check.  Big Problem.  If we logout of the Terminal Server and go back to the Citrix method of logging on, no printer issues at all - reports and checks print correctly.  Help, please.
baleman2Asked:
Who is Participating?
 
Philip ElderConnect With a Mentor Technical Architect - HA/Compute/StorageCommented:
I suggest looking up TSGrinder ... not a good idea to open 3389 to the world.
The Remote Web Workplace in SBS is an SSL secured Web site that one uses as a portal to gain access to Exchange (OWA), desktops (RDP), Terminal Services (Connect to my Application Server link), and the SharePoint CompanyWeb site.
More specifics:
http://blog.mpecsinc.ca/2007/06/sbs-2k3-rww-terminal-server-publishing.html
http://blog.mpecsinc.ca/2008/10/one-and-only-reason-to-never-have-ts.html
RWW:
http://blogs.technet.com/sbs/archive/2006/07/25/443383.aspx
http://blogs.technet.com/sbs/archive/2006/11/03/remote-web-workplace-rww-part-ii-controlling-portal-access.aspx
Philip
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Are you usine Remote Web Workplace as the portal into the network (comes with SBS) or do you have 3389 open to the world?
Philip
0
 
baleman2Author Commented:
Fortigate 60 Router is directing traffic into and out of the SBS Server with Terminal Services.  The policy in the Fortigate allows ALL RDP traffic access to the server.
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
And on topic:
If using RWW as your proxy to the remote desktop or TS desktop make sure the correct HP LJ1300 driver is installed. Do not use the universal print driver as this may cause conflicts on the remote machine.
Make sure any remote machine also has the driver installed even if they do not have the printer there. Use LPT1 as the default since parallel is uncommon for printers anymore.
Once you have the drivers setup correctly on the local and remote you should be able to print no problem.
Again, this is via RWW. But, RDP direct should work too.
Philip
0
 
baleman2Author Commented:
I'll give it a try this weekend.
0
 
baleman2Author Commented:
Followed numerous solutions as suggested by links.  No problems this week.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.