Hello,

I was wondering if anyone might know what may be my problem with print
sharing. We have many local printers on desktop machines that are shared
to the "Everyone" account. All users who log onto Domain B or Domain C
(both
are child domains in the Windows 2000 Domain A forest) can print to the
printers. All users who log into Domain A cannot print to the printers.
The printers show up as unavailable after logging onto Domain A. The
desktop computers that the printers are connected to are Windows98se and
the computers that are trying to print to them are Windows98se machines.

Has anyone ever run into this problem? It is a bizarre one, and I haven't
had a lot of time to investigate further. I did search Microsoft.com's
support database, but did not come up with anything.

Please help,
Tom C.

Yes I have seen this problem before. What you need to do
is set up some security groups on your primary control for
the people that you want to be able to print. And then
apply the groups to the shares on the printers that will
solve that problem.

Just to let you know that when you use the 'everyone'
account this mean everyone in the domain that the share is
attach to. So people in domain c will not be able to print
to a printer share on domain b unless you give that domain
access ie create a security group or just add the users to
the printer share that you need to be able to print.

Hope this helps

Regards

Aaron
>-----Original Message-----
>Hello,
>
>I was wondering if anyone might know what may be my
problem with print
>sharing. We have many local printers on desktop machines
that are shared
>to the "Everyone" account. All users who log onto Domain
B or Domain C
>(both
>are child domains in the Windows 2000 Domain A forest)
can print to the
>printers. All users who log into Domain A cannot print
to the printers.
>The printers show up as unavailable after logging onto
Domain A. The
>desktop computers that the printers are connected to are
Windows98se and
>the computers that are trying to print to them are
Windows98se machines.
>
>Has anyone ever run into this problem? It is a bizarre
one, and I haven't
>had a lot of time to investigate further. I did search
Microsoft.com's
>support database, but did not come up with anything.
>
>Please help,
>Tom C.
>
>
>.
>