Server 2008 R2 Print Server - Clients can't load driver from the server over a WAN (different AD site)
-
Friday, June 15, 2012 3:56 PM
Local clients (Windows 7 64-bit) have no issues clicking on the shared printer and installing the drivers, but when trying to add the printer from across our WAN, the client gets prompted "Do you trust this printer?", but once you select "Install Driver", they simply get "Windows cannot connect to the printer, operation failed with error 0x0000007c". The server and client are on the same domain, just a different Active Directory site. Permissions are all good, double-checked that. It shouldn't be a connectivity issue because I can add a shared printer from our 2003 print server across the WAN no problem. Also, if I install the print driver manually on the client, and then connect to the shared printer over the WAN, it completes successfully, so it's just the driver that won't install over the WAN.
My only hunch right now is perhaps our WAN accelerator is causing the problem, but that doesn't explain why the 2003 server works, unless they deliver the driver to the client via different method. I'm going to bypass the accelerator to rule it out and will post back to confirm, but please let me know if you have any other suggestions.
All Replies
-
Monday, June 18, 2012 9:42 AM
please refer this:
- Marked As Answer by Elytis ChengModerator Wednesday, June 27, 2012 5:03 AM
-
Monday, June 18, 2012 8:45 PMAnswerer
The delivery is different for package aware print drivers. 2003 does not support package driver install, it's a file copy process.
Off hand I'd say the Async RPC authentication channel is failing. Getting a trust prompt for a package aware print driver is not expected since the print server knows that the driver is a package and will hand that to the client but the client will think it needs to install the driver in legacy mode (XP, 2003 methods) which will not work with the package.
Ideally figuring out where authentication is falling down or getting blocked would be the long term goal but I think Citrix guidelines to fake out package point and print will get you what you want.
http://support.citrix.com/article/ctx128786
Alan Morris Windows Printing Team
- Marked As Answer by Elytis ChengModerator Wednesday, June 27, 2012 5:03 AM
-
Monday, June 18, 2012 8:51 PMAnswerer
Here's the group policy thread where I saw the Citrix information.
Alan Morris Windows Printing Team
- Marked As Answer by Elytis ChengModerator Wednesday, June 27, 2012 5:03 AM
-
Monday, February 18, 2013 11:27 PMDid you ever find out what the issue was? We are having this EXACT issue and we are also using WAN accelerators. Thanks for any help you can offer!!
-
Tuesday, February 19, 2013 1:05 AM
Did you ever find out what the issue was? We are having this EXACT issue and we are also using WAN accelerators. Thanks for any help you can offer!!
Unfortunately no, I only had one user that needed it while traveling, so it wasn't worth spending a lot of time on. My next step was going to be excluding the print server traffic from the WAN accelerators to see if it worked. To me it seemed like the drivers were getting cached by the accelerator and the client/server did not handle that well. Based on what Alan said above, it makes sense that it was the accelerator causing it since it worked fine with a 2003 server and the delivery process is different. Good luck!- Edited by QuickTek Tuesday, February 19, 2013 1:07 AM
.png)
