Hello-

I have a sticky problem that is causing me grief. In one of our labs I this
command to connect a network printer and make it available to all users of
the computer:

rundll32 printui.dll,PrintUIEntry /ga /n\\server\%printername%

The command seems to have worked because when i connect with any user that
has admin rights the printer shows up and works just fine. However when i
log in with the normal account that would be used on the computer which is
just a normal user account the printer does NOT show up.

Also when I browse for the printer and right click on it and click connect
to connect it manually I get the following error:

"You do not have sufficient acces to your computer to connect to the
selected printer".

When I add this user to the local administrators group and log off and log
in, as I said the printer shows up and works. Then if i remove them from the
local administrators group and log off and log back on it does not and will
not even let me manually connect to it.

I am assuming that the error is why the printer is not showing up. Does
anyone have any ideas what I can do to give that user sufficient access to
the computer to connect to the printer?

Client OS is XP Pro SP2

Thanks!

I suggest posting in the microsoft.public.winodwsp.print_fax newsgroup for
printer related issues like this.

Printer drivers can be quite ideosyncratic - what make and model of printer
is this?

Is the user account a local user account or a domain user account?

--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"Ehren" <Ehren@discussions.microsoft.com> wrote in message
news:A393AF21-C8D2-40B8-B88D-0EA602A87F6A@microsoft.com...

I would have posted there but the issue involves ad and group policy and
domain users. And people in the Xp newsgroup wouldnt probably be able to
factor those things in.

I ended up figuring it out, ends up it was a long ways away from what I
thought, it ended up being an issue with the profile and not permissions at
all. I dont know exactly why but I remade the roaming profiles and then it
worked.

Thanks

"Bruce Sanderson" wrote:

Good to hear your problem is solved.

Don't be put off by the name of the newsgroup
(microsoft.public.windows.print_fax); there are some people that respond to
posts in that newsgroup that are knowledgeable about domain environments,
including one or two from the Microsoft Printing product group.

--
Bruce Sanderson MVP
http://members.shaw.ca/bsanders/
It's perfectly useless to know the right answer to the wrong question.


"Ehren" <Ehren@discussions.microsoft.com> wrote in message
news:4F1E6221-8B68-4855-9BC7-8167430BB0FD@microsoft.com...