Printing through Terminal Services Server 2008 R2
I have a Customer with two offices, the main location is Server 2008 R2 x64 with Terminal services enabled, licensed and policies are ot blocking any redirection. I have verified that all of the printers in question are supported by the operating system, and i have downloaded and installed all the appropriate drivers.
The remote client is XP Pro that has all network printers with static IP addresses assigned to them. The MSTSC has all devices checked under local resources, when the client connects to the server all of the remote clients local printers are listed. I can send a print test page to the redirected printer but it never prints out and when monitoring the local printer queue for the printer it never pops up the print job. The customers printer is a Brother MFC-7220N.
I also tried this from my office, Windows 7 Officejet 8500, same results. but i can print ok from other customers locations.
The remote client is XP Pro that has all network printers with static IP addresses assigned to them. The MSTSC has all devices checked under local resources, when the client connects to the server all of the remote clients local printers are listed. I can send a print test page to the redirected printer but it never prints out and when monitoring the local printer queue for the printer it never pops up the print job. The customers printer is a Brother MFC-7220N.
I also tried this from my office, Windows 7 Officejet 8500, same results. but i can print ok from other customers locations.
I understand that all these networked printers are installed and working locally on the windows XP client machine?
After he connects to the TS, they are listed as redirected printers, correct?
Can you check the sharing permissions on the windows XP for any issues? (Eg. allow all access)
Optionally, share out the printers and connect to the manually in the TS. The connections should be retained for later session too..
After he connects to the TS, they are listed as redirected printers, correct?
Can you check the sharing permissions on the windows XP for any issues? (Eg. allow all access)
Optionally, share out the printers and connect to the manually in the TS. The connections should be retained for later session too..
ASKER
Yes the printer is installed and working correctly.
Yes the printers are definitely listed in TS as redirected.
The printer is currently shared with full access, although on my own personal desktop my printer is not shared and I am able to connect to other customers TS and I can print successfully.
I am not sure what you mean connect manually to TS, sorry can you elaborate?
Yes the printers are definitely listed in TS as redirected.
The printer is currently shared with full access, although on my own personal desktop my printer is not shared and I am able to connect to other customers TS and I can print successfully.
I am not sure what you mean connect manually to TS, sorry can you elaborate?
Does your user have administrative rights on the server perhaps? If so, please check to make sure that printer redirection is allowed for all users on the TS.
Open up "Remote Desktop Session Host Configuration" and under connections, right-click "RDP-Tcp" and select Properties. Navigate to the "Client Settings" tab. There should be a sub-section there called "Redirection"
Verify that Windows Printer is NOT checked. (checked means disabled..)
Open up "Remote Desktop Session Host Configuration" and under connections, right-click "RDP-Tcp" and select Properties. Navigate to the "Client Settings" tab. There should be a sub-section there called "Redirection"
Verify that Windows Printer is NOT checked. (checked means disabled..)
ASKER
I have veried that Redirection for printers is not disabled.
The other thing to check (often overlooked) is the Remote Desktop Client version on the problem machine. You should always ensure that you are running the latest RDP Client on your client machines.
ASKER
The client version is 6.1.7600
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thank you, i ended up checking the log files and found there were some access errors. i set security settings on the system32\drivers folder and everything worked after that.
cheers
Mark