|
| | | New Member
Group: Forum Members
Last Login: 9/11/2005 4:01 PM
Posts: 1, Visits: 3 |
| Hello all,
hope that I can get some help on this, as I have needed up with nothing everywhere else. Windows Server 2003 with Terminal services. Users are able to add the printer, but get the error "Default printer cannot be set" at the end of the add printer wizard. also, users are unable to set printers that they are currently connect to as default.
Only happens to none domain admin users and only on Windows Server 2003 terminal servers. Users are able to connect and set printers as default from our Windows 2000 terminal servers.
any help you can give would be very appreciated.
Oscar |
| |
| | | New Member
Group: Forum Members
Last Login: 9/22/2005 5:31 PM
Posts: 1, Visits: 1 |
| Here's the same issue but a little more in depth. And be patient if I miss a space, my spacebar is broken  Environment: Windows 2003 Server in Terminal Server Mode. Client machines boot into a local copy of XPP/XPH/2000/ME/98, it's a very mixed enironment. Then a TS connection is launchedand the user logs into the server. The Problem: No account, except the administrator's account, has or can set a default printer. However, when I add a printer tothe admin account, it will showon other user accounts. I am able to print a test page and anything else as long as the program doesn't care if there isno default printer. Unfortunately, we have to use QuickBooks 5.0 which cares alot about a default printer, it won't let us select from an available printer. I have gone through the default domain policy, terminal server configuration, active directory policies, everything... I cannot discover a solution or find anything that can give me more information on where this problem resides. |
| |
| | | New Member
Group: Forum Members
Last Login: 10/7/2005 4:50 AM
Posts: 1, Visits: 3 |
| I had exactly the same issue which I "fixed" by uninstalling Win2003 service pack 1
There must be something in SP1 that is adding an extra level of security to printing, but I havent worked out what so far??????
|
| |
| | | New Member
Group: Forum Members
Last Login: 3/29/2007 3:20 PM
Posts: 1, Visits: 1 |
| | This is caused by a corrupt registry key. You will find the information from Microsoft here Article http://support.microsoft.com/?scid=kb;EN-US;224148 and a solution of sorts here http://www.brianmadden.com/forum/tm.aspx?m=29437&mpage=1 . I have tried this and it does work. |
| |
|
|
