New 2003 r2 server

[alonebfg]

I have a 2 problems at the moment I have had to do a full new install of both my domain controles and starting from scatch. This is taking its toll on me. But the two problems I have are causing me a right headach.

1. In gpo i have disabled run in start menu I know this stops people typing //servername/share but i am sure there a way round that but for the life of me I can remember.

2. Printer Issue users cannot join printer que and i dont know why have investegated with no luck can add them as admin. But user just get error "A policy is in effect on your computer which prevents you from connecting to this print queue. Please contact your system administrator" I have checked this point and print but am still no ferther on.

[GrumbleDook]

You can enter it in a browser window or type it in an Office document where it becomes a hyperlink.

The only way you can adequately block access to shares is by using share and NTFS permissions.

[alonebfg]

No its not that I didnt want it blocked sorry if i was not clear enough. Its just if you stop run connand on start menu you cant type unc in explorer also been trying all weekend to get this printer problem sorted ??

[bishopsgarthstockton]

you say people can not join printer que, never come across this problem. all i can think of is permissions.

[alonebfg]

tried that not a permissions issue authough admins can add but its to the printer que thats what confusing ?? permissions for printer que? by default it set to everyone and there are no share pomissions as far as i know just secuarty.

[JoeO]

I don't want to Hi-Jack this conversation and I will create a new post if necessary, but I'm having a similar problem.

We had all of our print shares on a windows 2003 server and nobody had problems adding the printers to their local desktops.

We created a new Windows 2003 R2 SP2 server and now end users get the deadly: ""A policy is in effect on your computer which prevents you from connecting to this printer queue. Please contact your system administrator"" error.

When you make them local administrator on their local computer sometimes it fixes the problem and sometimes it doesn't...

Any ideas?