One Terminal Services Client Cannot Print

Greetings all,
We have a client with a single 2008 R2 Server, configured as a standalone server. Employees from multiple physical locations will remote connect into the server, use Quickbooks, and then print to redirected printers at their own locations.
One employee is having print issues. He can connect to the server, he can access and use Quickbooks, and he can print documents, but any document that he prints comes out of the printer at the local office where the server is located, not at his remote location.
I've confirmed that his Remote Desktop client is configured to use local resources. His user account has all the same group memberships as accounts that can print with no issues. The printer at his remote location is the exact same model as the printer
in the local office (a Brother MFC) , so I know that there are already drivers for that model installed on the server.
The employee has renamed his printer on his personal computer with a name that corresponds to his location, and then is able to confirmed that a Redirected icon for that printer appears when he his logged into the server. But he is unable to print to it.
I've tried from within QB, and also a basic Windows test page.
Any thoughts? I'm running out of ideas. Thanks

Hi,
Please check if the user can see the redirected printer in Printer Management of the remote PC. It should use the TS00* port.
In addition, is there any related error in the Service and Application log on both server and client sides? What is the OS version of the client?
Terminal Services Printer Redirection
http://technet.microsoft.com/en-us/library/cc775315(v=ws.10).aspx
Windows Server 2008\Printer redirection not working
http://support.microsoft.com/kb/2003646
Thanks.
Jeremy Wu
TechNet Community Support

Similar Messages

New Terminal Service client plugin for ASA?

Hi all,
since Feb a new version (rdp-plugin.111024.jar) of the Terminal Service client plugin for ASA is available.
Can somebody tell me what is changed or new in this version? There are no release notes for this version, only for the older rdp-plugin.101215.jar.
Thanks,
Markus

Hi Yasser,
Thank you for posting in Windows Server Forum.
As you have commented it happens with single user so might possible there is some issue with specific user profile.
Have you tried to login that user from different systems and check result?
Here I can suggest you to delete the roaming profile cache and verify result. You can enable GPO policy as below steps & then try to religion and check the result.
1. Edit the GPO that you want to modify.
2. Locate the following section: Computer Configuration \ Administrative Templates \ System \ User Profiles.
3. Double-click Delete cached copies of roaming profiles (the Group Policy setting).
4. Click Enabled.
In addition, you can checkthis article for user profiles guide. Also see whether you have applied proper
permission to that user for accessing that application.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Terminal services client (windows mobile v5.0)

Hello all, I've been using ARD3 for a while now with no dramas at all, I wonder if is possible to use the terminal services client on my shiny new o2 XDA mini s(iMate K-Jam etc...) to control the macs on my network via my airport connection, I've tried the obvious ie connecting to the network, enabling windows sharing and remote desktop etc in the prefs pane. I have then entered the ip of my make but the little pda just timesout trying to connect to the server.
any ideas would be much appreciated.
steve

errr, it does have wifi cos I'm writting this post on it whilst sat in the loo and I have it connected to my home network, and in response to the other post, I know that terminal services is windows technology, I myself loath the windows OS but unfortunatly 95% of the world continue to use it.
The PDA has a 320 x 240 screen with a full qwerty keyboard, I have used terminal services with my work network(XP I'm afraid) and it works quite well,
I'm not really after full desktop control but the ability to view the desktop rather than have people trying to describe(usually badly) it to me when I'm out and about would be very usefull.

Reporting Services Client-Side Printing

All my BI users should be able to print SSRS directly from their Local PC. Right now they do not have administrative rights on their PCs. How do I install the print- client SSRS files on the client machines. Also, what and where are the
files I need to install in order to enable client-side printing. I am using SSRS 2012 SharePoint integrated mode.

Check out this article...
http://www.kodyaz.com/articles/client-side-printing-silent-deployment-of-rsclientPrint.aspx
The same concept applies no matter which version of SSRS you are dealing with. You just need to find the CAB file. For SSRS 2008 R2 it is in:
C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\bin

One account on computer cannot print from internet

Mac mini with separate accounts, using HP Officejet J4550 as printer. From one account cannot print anything from the internet, including web pages and email.

Hi @Cabon,
Welcome to the HP Forums!
I see that you can print from Windows, but not from the internet. I am happy to help you with this printing issue!
What version of Windows are you using? If you do not know the operating system you are using, please visit this website. Whatsmyos.
In the meantime, please see this printing guide, Print Jobs from Your HP Printer are Stuck in the Print Queue. (Even though the guide title may not match your issue, I believe the solutions will help).
Hope this guide helps, and thank you for posting!
RnRMusicMan
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to say “Thanks” for helping!

Call Viewer Terminal Services Client

We have unity 5.01, call viewer used to work via terminal services, now its stopped - says it can't be run via TSC, any reasons why?

errr, it does have wifi cos I'm writting this post on it whilst sat in the loo and I have it connected to my home network, and in response to the other post, I know that terminal services is windows technology, I myself loath the windows OS but unfortunatly 95% of the world continue to use it.
The PDA has a 320 x 240 screen with a full qwerty keyboard, I have used terminal services with my work network(XP I'm afraid) and it works quite well,
I'm not really after full desktop control but the ability to view the desktop rather than have people trying to describe(usually badly) it to me when I'm out and about would be very usefull.

Windows Server 2012 Terminal Services (Client Side)

I would like to see the interface of the new Windows Server 2012 Terminal Session via RDP. Reason being, is that users are resistant to change - and if there is no start button like in windows 8, that is a big concern when considering upgrading our
server to 2012. Anyone know what it looks like? Screenshots of being logged in as a user via RDP would be much appreciated!
Thanks

Hi,
Yes, there is a Start Button in Server 2012 R2:
You may download the preview and test if you like:
http://technet.microsoft.com/en-US/evalcenter/dn205286.aspx
-TP

P1566 and Terminal Services.

I have a 64 bit 2008 server running terminal services,
A client with windows xp 32 bit and HP LaserJet P1566 printer attached to it.
When connecting via RDP to the server the printer is mapped though to TS and appears on the printer list. How ever when printing it comes up saying that it is not possible to print.( this message is on the server)
The server is using the Terminal Server Easy Print driver.
As far as I am aware Microsoft recommend not using host based printers and HP say that it is compatible (but is this directly connected to server or passed through the RDP client?)
has anyone manged to connect on of these printers, or are host based printers just NO GO areas when connecting though an RDP client?
Other PCL5e based printers recieve the print jobs in the Local Queue (Client) from the Terminal Services Clients
Many Thanks for you help.
Malcolm.

We have now investigated further and it looks like we have found a solution.
If the following group policy key is set to enabled/disabled the system configured to use the terminal server easy print.
computer policy/administrative templates/windows components/terminal services/printer redirection/Remote Desktop Easy Print Driver First
By changing the key to "not configured" the printer then listed the P1566 driver instead of the Easy Print Driver.
If this key was set to Disabled one would have expected it to try the correct driver before easy print, but this was not the case.
Hope this helps a few others of you with a similar problem.
Malcolm

RE: (forte-users) Terminal Services - Win 2000

Hi
l've already installed my application 'appA' at my server 'ServerA'.
When l try to execute this application in my pc thru Terminal Server, there
were nothing displayed at my pc but when l check at on 'ServerA' , l can
see that 'appA' is running over at the 'ServerA' side. Actually, I'm new at
this Terminal Server thingy...
thanks..
-----Original Message-----
From: Jean-Paul Gabrielli [mailto:Jean-Paul.Gabriellisema.fr]
Sent: Friday, January 19, 2001 5:08 PM
To: Zulkifli Mohamad
Subject: RE: (forte-users) Terminal Services - Win 2000
hmm when you telent a machine to run a process remotely, don't expect to
have it locally :-)
j-p
-----Message d'origine-----
De: Zulkifli Mohamad [mailto:zulkifli_mohamadkonnas.com.my]
Date: vendredi 19 janvier 2001 09:19
À: forte-userslists.xpedior.com
Objet: (forte-users) Terminal Services - Win 2000
hi..
l'm trying to run forte application thru Terminal Services Client
(Win 2000) but my application only running on the server not at the client
pc. Some one can help me...
thanks.
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Il suffit de mettre les BTD/BTX sur un drive réseau (net use X:
\\server\share_point),
puis d'installer des icônes pour les clients: ftexec -fi bt:x:\MyApp.
Pour que les noeuds ne s'auto-enregistrent pas, peut-être mettre un password
Ou bien définir les noeuds comme un 'groupe' et donc seul le groupe est
connu.
Si mettre le mot de passe suffit pas, et si vraiment le model node gêne,
alors il
faut un autre environment manager.
I think that to avoid install, the software could be located on a shared
drive,
and users linking to it through running 'ftexec' or directly the compiled
binaries.
For nodes not to appear in the environment as nodes, they could be defined
as members
of a model node '(which then would be in the environmnet)'
Putting a password in the environment could prevent nodes to be registered
there, but
might prevent the apps from being executed.
Cheers,
j-paul gabrielli
Sema DTS
-----Message d'origine-----
De: Thomas Felix [mailto:tfelixaxialog.fr]
Date: mardi 2 mai 2000 14:14
À: forte-userslists.xpedior.com
Objet: (forte-users)
bonjour a tous
je souhaites installer une application distribuée sur des postes clients.
Y'a t'il moyen de ne pas installer les noeuds de ces postes clients sur l'
active environnement lié au développement et si oui comment?
hi
I would like to install an application on clients workstation
Can i install this nodes in a different Active environnement than this one
that we use for the developpement ?
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

ORARRP with Win 2000 Terminal Services

Hi,
We find that ORARRP (1.3.4) directs output to a file instead of the virtual printer on Windows 2000 terminal services. The print dialog comes up OK, we select a virtual printer (not LPT1 or a network printer share), and a file named TS001 is written. If we turn debug on, nothing is written to orarrp.dbg. The normal print dialog in Notepad, Word, etc. works OK.
Is there any way to direct report output to Windows 2000 Terminal Services virtual printers?
Thanks,
Dave Ball
Oak Ridge, TN

I am using Tomcat 5.0.27 and it is working perfectly. perhaps check the stdout.log to see what errors are thrown while starting the tomcat. Check the port also

Terminal Services Application?

I searched the App Store and could not find an application that would behave like a Terminal Services Client. Does anyone know if such an application exists? Also, if it does exist, how easy it is to use given the small screen size of the iPhone.
Thanks

I believe that there are a couple VNC clients in the works, and the original developers of Terminal Services, Citrix, are working on a version for the iphone.
http://searchservervirtualization.techtarget.com/news/article/0,289142,sid94_gci 1337825,00.html

Printer for Terminal Services / Thin Clients

Hi, Just checking on what multifunction printer you would suggest for use with a Terminal Services environment? We only require the printer to go through TS. The other features will be used locally (photo copy/fax).
I am looking at the CM2320, a good choice?
Terminal Services: Windows 2003
Thin Client: T5730 using RDP 6.0
Many thanks

Hi,
Thank you for posting in Windows Server Forum.
A mandatory user profile is a special type of pre-configured roaming user profile that administrators can use to specify settings for users. With mandatory user profiles, a user can modify his or her desktop, but the changes are not saved when the user
logs off. The next time the user logs on, the mandatory user profile created by the administrator is downloaded. There are two types of mandatory profiles: normal mandatory profiles and super-mandatory profiles.
User profiles become mandatory profiles when the administrator renames the NTuser.dat file (the registry hive) on the server to NTuser.man. The .man extension causes the user profile to be a read-only profile.
User profiles become super-mandatory when the folder name of the profile path ends in .man; for example, \\server\share\mandatoryprofile.man\.
More information:
Mandatory User Profiles
http://msdn.microsoft.com/en-us/library/windows/desktop/bb776895(v=vs.85).aspx
Using User Profiles in Windows Server 2003
http://technet.microsoft.com/en-us/library/cc776120(v=ws.10).aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Cannot print to recognized Bonjour printer - one client only!

Hello - please help!
Purchased a new Epson WorkForce 30 printer and plugged it into the USB port of one of my Airport Extreme (the one configured as a bounce station). Both my Aiports are 802.11g.
I can print wirelessly from my old ibook G4 (running 10.3), and my PC running Windows XP home - but not from my MacBook Pro running 10.5.8!
The really frustrating part is that my MacBook recognizes the Epson over Bonjour, adds it as a printer, sends the job to the queue - but nothing actually prints.
I tried Network Diagnostics and it says DNS settings may be interfering? Any ideas?
Wireless internet works fine and can admin both Airports from the MacBook.
Please help!!!

I have a similar issue... I got an Airport Express, plugged it in and it worked great from my Mini. It also worked great from my HP Laptop - and would print fine, even with the HP laptop turning on the HP 5650 printer. It would NOT turn on automatically from the mac, which I thought strange. After a while the HP laptop seemed to lose the internet connection, and had I constantly had to mess with it to get it back. Changed the settings in airport - from 10.0.1.1 addressing to 192.168 addressing. also changed it from WPA security to just MAC addresses. Also noticed the setting for "Enable Remote Printer Access" - and presto, the Mini could turn on the printer. The HP Laptop connects everytime with no hitches. Except.. now the HP Laptop will not print. I went back to all the original settings to no avail. Bonjour for Windows sees it. reinstalled, let's see.. Bonjour, HP Printer Software, deleted all the ports in windows - but cannot print from Windows.
any ideas would be appreciated!
tia
ferd
mini Mac OS X (10.4.7)

New 2012 R2 domain - xp clients cannot join or print

I just migrated a 2003 domain to 2012 R2.   Things were working ok & then XP clients became AD stupid.
Steps I took:
Added a VM 2012 R2 DC to the domain. Server had DNS installed. Ran dcdiag & bpa and resolved any issues.
About a week later I moved all roles over to the VM DC.
Tore down one of the NT2003 DCs (not VM) and rebuit it as a 2012 R2 DC w/DNS. Ran dcdiag & bpa and resolved any issues. Had problems with DNS scavenging removing some static records. readded records & made sure the "Delete
record when it becomes stale" was unchecked on all static records (all fwd & rev zones).
Moved all roles from the VM DC to the hardware DC.
After a week I tore down the 2nd (& last) nt2003 DC (not VM) and rebuilt it as a 2012 R2 DC w/DNS. Ran dcdiag/bpa and fixed any issues. Also ran it on the other DCs.
Removed the VM 2012 R2 DC from the domain (demote, remove features, remove from domain, power off, delete VM).
Everything seems to be working fine. dcdiags look clean, event logs seem good.
Bump forest/domain to 2012 R2 native.
Then, a few days later, it goes bad. I (after hours) install all accumulated updates on both DCs. Reboot both.
Next AM a user calls. Her thin client cannot connect to the terminal services server. DNS has deleted its dns record, even though the delete when stale was unchecked. :| So I readd the static record and turn off scavenging.
Problem solved.
Next call s from a XP user (we have XP, Win 7, and thin clients). She cannot print. Printers show "cannot connect". Try various things to no avail. Check Win 7 boxes and they're working fine & printers are connected.
Note that the XP & Win7 boxes all pull their DHCP address from the same dhcp server/scope.
Review error logs and run dcdiag. There are several somewhat esoteric errors. After several hours or tail chasing I decide to take a more scorched earth tack. I demote the 2nd DC and remove AD & DNS from it. After demotion and role
removal I check AD and it still shows the DC. I remove the now just a server from the domain. Clean up DNS & AD removing all traces. This takes a while as I have to run variuos scripts (tahnk you google) to ensure AD is clean.
Run dcdiag and resolve issues. Even a detailed dcdiag comes out clean. Replication tests show the old server is now forgotten.
Check XP boxes and they still show printers as "cannot connect".
Remove a XP PC from the domain. Try to rejoin and I get a error. Rename it and still get the error. I can ping, nslookup, etc and they return the correct IP.
I've tried the simple change the join a domain in system properties. That gives a somewht non descript error. The network identification wizard seemed to find the domain but didn't work. As it was trying to find the PC in AD, I went ahead
and added it via AD users& Computer console. Run the wizard and it tells me it found the record in AD. It then says "a domain controller for the domain [ourdomain] could not be contacted." !? Yet the prior screen it told
me it had found the record for the PC on the DC.
nslookup for ourdomain.local as well as dcname.ourdomain.local resolve correctly. Tried chenging the PC to static - no change. Rename the old win 2012 R2 dc (now just a server outside the domain), reboot, and the try to rejoin the domain.
Works flawlessly.
BTW - We're running tcpip w/o netbios over tcpip.
So basically my XP boxes cannot use AD printers and cannot join the domain. IDK if they're picking up gp updates (I'll check in the AM), but I suspect they're not.
Short of buying a truckload of Win 7 licenses and reloading OSs, what can I do to fix this?
Details on the XP box error (fyi - I did a record to record comparison to a Win 2008 domain's SRV records and they look identical (except, fo course, the domain& server names)) :
The domain name [ourdomain] might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.
If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain [ourdomain]:
The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
The query was for the SRV record for _ldap._tcp.dc._msdcs.[ourdomain]
Common causes of this error include the following:
- The DNS SRV record is not registered in DNS.
- One or more of the following zones do not include delegation to its child zone:
[ourdomain]
. (the root zone)
For information about correcting this problem, click Help.
dcdiag /test:dns results
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = Domctl1
   * Identified AD Forest.
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\DOMCTL1
      Starting test: Connectivity
         ......................... DOMCTL1 passed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\DOMCTL1
      Starting test: DNS
         DNS Tests are running and not hung. Please wait a few minutes...
         ......................... DOMCTL1 passed test DNS
   Running partition tests on : DomainDnsZones
   Running partition tests on : ForestDnsZones
   Running partition tests on : Schema
   Running partition tests on : Configuration
   Running partition tests on : [ourdomain]
   Running enterprise tests on : [ourdomain].local
      Starting test: DNS
         Test results for domain controllers:
            DC: Domctl1.[ourdomain].local
            Domain: [ourdomain].local
               TEST: Dynamic update (Dyn)
                  Warning: Failed to delete the test record dcdiag-test-record in zone [ourdomain].local
               Domctl1                      PASS PASS PASS PASS WARN PASS n/a
         ......................... [ourdomain].local passed test DNS

I see the following errors:
"TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing
connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period
to elapse between successive connections from a given local endpoint to a given remote endpoint."
Please read that: http://social.technet.microsoft.com/Forums/windowsserver/en-US/d770e9fd-53a2-4ae9-99b3-2754c4564592/tcpip-connection-issue-on-windows-server-2008-sp2?forum=winserverPN
"DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID      b70 (C:\Windows\system32\dcdiag.exe)."
As you can see, it is pointing to 8.8.8.8. You need to make sure that public DNS servers are configured as forwarders and not in IP setting of your DCs. Better if you could use your ISP DNS servers as public ones instead of 8.8.8.8.
Please read this Wiki article for recommendations about IP settings: http://social.technet.microsoft.com/wiki/contents/articles/18513.active-directory-replication-issues-basic-troubleshooting-steps-single-ad-domain-in-a-single-ad-forest.aspx
" TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone [ourdomain].local
Warning: Failed to delete the test record dcdiag-test-record in zone [ourdomain].local
[Error details: 9505 (Type: Win32 - Description: Unsecured DNS packet.)]
Here, you need to make sure that only secure DNS updates are allowed if you would like to secure dynamic updates. This is detailed in here:http://social.technet.microsoft.com/wiki/contents/articles/21984.how-to-secure-dns-updates-on-microsoft-dns-servers.aspx
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Get Active Directory User Last Logon
Create an Active Directory test domain similar to the production one
Management of test accounts in an Active Directory production domain - Part I
Management of test accounts in an Active Directory production domain - Part II
Management of test accounts in an Active Directory production domain - Part III
Reset Active Directory user password

Windows 2008 R2 Terminal Services, ODBC and Oracle 10.2.0.5 32-bit client

Hi All,
I am setting up an application to work under windows 2008 R2 terminal services/Citrix XenApp which is 32bit. This application uses ODBC connections and not relying directly on TNSName for connection resolution.
I installed 10.2.0.3 and patched to 10.2.0.5, and when trying to create an ODBC connection I only see "junk" in the connections list for TNS Server Name without regard to what exists in the TNSNAME.ORA file.
We have JDE on the same server which uses TNSNAMES and work fine, so I don't think it is Oracle client related directly, but I've not seen this before.
Has anyone seen this before and know how to resolve?
Geoff

Patches are only available to Oracle customers with valid support contracts. If you do have such a contract, pl contact the person in your team who has access to My Oracle Support to download the needed patch. Patches cannot be posted on public servers as this violates ones support contract
Srini

One Terminal Services Client Cannot Print

Similar Messages

Maybe you are looking for