Solved

Virtual 2012 Windows server DC can’t communicate with printers

Posted on 2013-01-13
3
797 Views
Last Modified: 2013-01-19
I have setup a Virtual 2012 server in a new domain.  Everything is working except for printing.  When I setup a printer, it communicates with the printer, and knows what kind of printer it is based on me putting an IP address in.  But when I print a test page, it says it printers, but nothing comes out.  I have added the Print server roll and removed it same results.  Now on the host server, I can setup the printer and it works just fine.  Just the Virtual DC is having the problem.  The host server is also a 2012 server.

Any suggestions would be great.  I have tried everything, and this is going to mess up this upgrade if I can’t fix it.
0
Comment
Question by:rtalarek
  • 2
3 Comments
 
LVL 58

Expert Comment

by:Cliff Galiher
ID: 38776171
I am assuming the host is Hyper-V?
0
 

Accepted Solution

by:
rtalarek earned 0 total points
ID: 38776226
The Spooler folder on the C-Drive is set so everyone has no access.  Opened a case with Microsoft, and they pointed me to this artical  http://support.microsoft.com/kb/968605  This is new with Server 2012 DC's.  Follow the artical and it will fix your problem.
0
 

Author Closing Comment

by:rtalarek
ID: 38796085
Had to open a critical down case with Microsoft, and they fixed the issue
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This script can help you clean up your user profile database by comparing profiles to Active Directory users in a particular OU, and removing the profiles that don't match.
This article runs through the process of deploying a single EXE application selectively to a group of user.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question