Tech Support > Microsoft Windows > Windows Server > Using Windows Storage Server 2003 for print serving
Using Windows Storage Server 2003 for print serving
Posted by Steve on July 27th, 2004


This is probably a question with a fairly simple answer -
we've just bought an Iomega NAS 203M box, which runs
Windows Storage Server 2003 Standard Edition. We'd like to
use it for print serving in addition to the file serving
it's currently set to provide.

According to the specs on Microsoft's site, it *should* be
able to do this, but whenever we share a printer we get
told that "Remote connections to the Print Spooler are
blocked by a policy set on your machine".

I've checked in both the local Group Policy and the one
applied from the domain and in both the option to 'Allow
Print Spooler to accept client connections' is enabled.

I've restarted the server, forced a group policy update
and restarted the spooler service, all to no effect. The
printer itself works fine (it's an HP Inkjet on a
JetDirect box), but I just can't share it.

Is Storage Server 2003 standard edition capable of being a
print server?

Posted by Jack on September 17th, 2004


Well, was there a fairly simple answer???...I hope so. I'm experiencing the
exact same problem, and have gone through the exact same steps with the same
results. Have you succeeded??

"Steve" wrote:

Posted by Francisco Shillander on October 12th, 2004


1. From the Start menu, point to Administrative Tools and then open
the Local Security Policy console.

2. Expand the Policies node, and then select Security options.

3. In the Details window, double-click Devices: Prevent users from
installing printer drivers.

4. A dialog box displays. Select to disable this policy, and then
click OK.



"Jack" <Jack@discussions.microsoft.com> wrote in message news:<67790804-9CBE-4A75-9C77-1EEC4C511E35@microsoft.com>...

Posted by Jack on October 12th, 2004


Tried that....the policy was already disabled, still, I get the error message
stating that "remote connections to the print spooler are blocked by a policy
set on your machine"....

"Francisco Shillander" wrote: