Link to home
Start Free TrialLog in
Avatar of bankadmin
bankadminFlag for United States of America

asked on

Having problems with permissions in AD on a new printer

Installed a new network printer and users are getting an error when they try to install it. "You do not have sufficient access to your computer to access the selected printer". This printer is at another branch
I can print to it logged in as admin. I have duplicated the security settings of the printer to other printers that are located at the same location. I have run out of ideas. Please any idea would be greatly appreciated. Also notable is that we run in a citrix enviroment. I do however get the same results in a local enviroment..

Mark
ASKER CERTIFIED SOLUTION
Avatar of kanalQko
kanalQko
Flag of Slovakia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bankadmin

ASKER

Its a laser 2015. Its connected via ethernet line.
I dont follow "check permission settings at first>everyone can print"
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Ive tried that I get the same error..
So locally its hooked up to a computer or is  it a network printer?
What settings do you have on the other?  You dont have any group policies with printing do you?
Its a network printer installed on the file server and shared from there. We dont have printer policies. I have security groups for all the diffrent sites such as "location" then add the location group to the printer and give the location group rights for that printer.

Any other questions let me know
All groups arent working or just one?  There is obviously a setting the admin group has that the 'location' groups do not.
I had a hunch and I think its totally related to the citrix servers.. I'm able to get it to install when I connect to one of the citrix servers but not the other two. Sorry I was just using the genaric citrix desktop during testing instead of going to each individual server. Something is diffrent with the citrix servers
hey sorry for the misleading question it was a citrix issue not a AD problem like I thought when I wrote the question