Issues.
Symptoms and Scenarios that we have tested.
Domain Client -> Primary Domain Print Server -> Printer – Not ok, Jobs stuck between Domain Client print spooler.
Domain Client -> Secondary Domain Print Server -> Printer – Not ok, Jobs stuck between Domain Client print spooler.
Domain Client -> Workgroup - VM (2012R2 Testing) -> Printer – Ok
Domain Client -> Printer – Ok
Domain Print Server -> Printer - Ok
Workgroup Client -> Domain Print Server -> Print – Ok
Created a testing VM Windows 7 joined xxxx.com domain, tested mapped to domain print que and printed ok, but after restart pc or log in and log out, unable to print out. My Guess is it possible during that time the domain policy not yet push down the operating system. After policy is pushed on the operating system it will not be able to print.
Network is not blocked by firewall as all ports is allow, and the basic troubleshooting restart printspooler, restart server, remap que, reinstall drivers&packages all done, in windows/system32/drivers also given everybody written permissions.
Is there any policy that will cause this issues anyone can help?