in news:0DD61D4E-CC1D-40E0-BC9E-1AFDD15587F2@microsoft.com:

> I have a home network workgroup with two XP desktop computers
> (both running 32-bit XP/sp3) ethernet-connected to a router plus a
> wireless-connected laptop running Vista(x64).
> Both desktops have a direct-connected (USB-port) printer attached.
> All computers have admin and standard user level accounts.
> I can print to any printer from any other computer from an admin
> account. BUT I cannot print to the printer on desktop#1 from a
> standard user account on the other computers; although I *can*
> print to the printer on desktop#2 from standard user accounts on
> the other machines. I have tried in vain to find how to set up
> desktop#1 to permit standard users from the other machines to use
> its printer. (& YES, the printer is shared) 
> I have looked in all the *usual* places in network setup and
> sharing permissions to no avail. 
> What have i missed?

in news:D80B6CA1-597F-4376-953E-DA2A2262D560@microsoft.com:

>
>
> "John Wunderlich" wrote:
>
>> You've made it very difficult to guess because you don't say what
>> happens (or doesn't happen) when you _try_ to print to this
>> printer so we might determine at what point things go wrong.
>>
>> Also, it would be helpful to know if you have XP Home or XP Pro;
>> and if it is XP Pro, whether Simple File Sharing is enabled or
>> not: (Double-click any folder)->Tools->Folder Options->View Tab->
>> [Last in list].
>>
>> -- John
>>
>
> Sorry to have left out what may have been important.
> The XP machines are running XP Pro.
> and "nothing" happens when I tried to print from standard
> accounts, except the docs in the print queue show up with errors
> after a bit and sit there until cancelled.
>
> The good news is that you hit the nail on the head re: "Simple
> file sharing" I had turned it OFF years ago when I needed more
> security on that machine when I had multiple users on it before I
> had a networked workgroup and less privileged users could be moved
> off.  Had I remembered that I had done that and recalled where
> that setting was I would have re-enabled it a year ago!. 
>
> Issue solved.
> Thank you very much.
>