printer problems - Please Help!!!!!

> You will need to reboot after setting the IRP value. This is network stuff
> not printing stuff so I don't even know what this irp stuff is.
>
> It sounds like you found the KB for this. You can set to the max and see it
> that gets things working then cut the value until you have a value that
> works, or increment up until you find the working value. But you will need
> to reboot after each setting change for the server service to pick up the
> change.
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Harry Hornet" <HarryHornet@discussions.microsoft.com> wrote in message
> news:07C83A5F-39D2-49A0-A015-05C287F74AD1@microsoft.com...

> >I have a strange problem.
> > All users can access a printer depending which room they log in to.
> > Example if someone logs onto a pc in the Blue Room, the can print to the
> > Blue Room's printer. Simple! This is done by using a script at logon time.
> > This has worked fine for years.
> > The other day I had mega problems with a printer and had to delete it from
> > the server and reinstall it again. Since then some PCs will not print to
> > it.
> > The situation is as follows...
> > A user logs on to PC1 and can print ok.
> > The same user logs onto a different PC and although they can see the
> > printer, they cannot print to it.
> > I have been tearing what little hair I have out. The script is working
> > because some can print. It only seems to be on some PCs.
> > I have noticed that in the event log on those that do not work, there is
> > an
> > entry for SRV error 2011 - irpstacksize is too small for the server to use
> > a
> > local device. Please increase the value of this parameter.
> > I have tried to update the registry as detailed in the knowledge base but
> > it
> > seems to make no difference. Am I looking at a red herring?
> > I just hope someone can come up with a solution!

>
>
>

> Does trhis need to be done on the server and the workstation?
>
> "Alan Morris [MSFT]" wrote:
>

>> You will need to reboot after setting the IRP value. This is network stuff
>> not printing stuff so I don't even know what this irp stuff is.
>>
>> It sounds like you found the KB for this. You can set to the max and see it
>> that gets things working then cut the value until you have a value that
>> works, or increment up until you find the working value. But you will need
>> to reboot after each setting change for the server service to pick up the
>> change.
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>>
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>
>> "Harry Hornet" <HarryHornet@discussions.microsoft.com> wrote in message
>> news:07C83A5F-39D2-49A0-A015-05C287F74AD1@microsoft.com...

>>> I have a strange problem.
>>> All users can access a printer depending which room they log in to.
>>> Example if someone logs onto a pc in the Blue Room, the can print to the
>>> Blue Room's printer. Simple! This is done by using a script at logon time.
>>> This has worked fine for years.
>>> The other day I had mega problems with a printer and had to delete it from
>>> the server and reinstall it again. Since then some PCs will not print to
>>> it.
>>> The situation is as follows...
>>> A user logs on to PC1 and can print ok.
>>> The same user logs onto a different PC and although they can see the
>>> printer, they cannot print to it.
>>> I have been tearing what little hair I have out. The script is working
>>> because some can print. It only seems to be on some PCs.
>>> I have noticed that in the event log on those that do not work, there is
>>> an
>>> entry for SRV error 2011 - irpstacksize is too small for the server to use
>>> a
>>> local device. Please increase the value of this parameter.
>>> I have tried to update the registry as detailed in the knowledge base but
>>> it
>>> seems to make no difference. Am I looking at a red herring?
>>> I just hope someone can come up with a solution!

>>
>>