i had the same problem, the only fix i found was to make the user a local admin, then install and configure the session as the user. no problems after that...
i am having this same problem, the print job is created on a mainframe at a different location, prints to a network printer on the user's same subnet. (this seems to have started when we upgraded all desktops to win2k.) i have upgraded 5 of the machines that had the problem to 6.7, one of them...
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.