You may want to check the print drivers that are being used. I have just spent the better part of two weeks trying to figure out a very similar scenario and it turned out that a faulty .dll was the culprit.
Once it was removed things have been working great. Check out...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.