[Webinar] Learn how to a build a cloud-first strategyRegister Now


Unable to Add a Network Printer to an XP Machine

Posted on 2006-05-25
Medium Priority
Last Modified: 2013-12-23
When trying to add a Windows 2000 Networked Printer to a Windows XP client I get the following error:

"A policy is in effect on your computer which prevents you from connecting to this printer queue, please contact your system administrator"

Any ideas? The XP client has no policies applied and has SP2 installed.
Question by:hertel-dev
LVL 10

Accepted Solution

kgreeneit earned 500 total points
ID: 16764105
hi there, just in case there is a group policy applied to the pc, you should run the resultant set of policy (RSoP) snap in from the pc and check all the options to see if there is a policy applied.

To run RSop, click on start, then run, then type   rsop.msc

The RSoP snap in should then scan the local pc for any applied policies. You will then need to go through each option in the list and make sure that everything is o.k.

Also, you could try logging on as a different user and see if this will work - if it does, then the user account has a restriction on it.

Try installing the printer locally to see if it restricts you this way. If it doesn't, then its possible that there are permissions/share issues with the shared printer driver.

Hope this helps!
LVL 13

Assisted Solution

hstiles earned 500 total points
ID: 16768570
I have experienced this problem with Windows XP clients in an NT4 domain attaching to print queues on a Windows 2000 server.

In the end I had to make domain users members of the power users group and then modify the local policy to allow power users to add or remove device drivers.

Is your environment an active Directory or still NT4 domain?

Assisted Solution

DarrenJackson earned 500 total points
ID: 16769241
The domain is w2k with primarily w2k desktops/ laptop's but we have a few XP svp 2 machines

It is this OS that is giving me grief all laptop / desktop have policies from the domain so would the idea of adding the user to the power user option not be a waste of time as the local policies are not applicable in a domain


Expert Comment

ID: 16769253
just to add i mentioned the laptop's desktop have policies applied but the xp machinee are in a OU that excludes the policy inheritence  but still log in to the domain

Assisted Solution

foochar earned 500 total points
ID: 16792078
I ran into a similar problem with XP clients in an NT 4.0 domain and the solution was to disable the policy described in the following article at microsoft: http://support.microsoft.com/?kbid=319939.  If I remember correctly I had to use gpedit.msc on the individual machines and disable the policy on the machine.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Trying to figure out group policy inheritance and which settings apply where can be a chore.  Here's a very simple summary I've written which might help.  Keep in mind, this is just a high-level conceptual overview where I try to avoid getting bogge…
Resolve DNS query failed errors for Exchange
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Screencast - Getting to Know the Pipeline
Suggested Courses

868 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question