I have an SBS2000 network and everyone/everything is
pretty good but one workstation can not print to one
network printer (our check printer, unfortunately).

I believe the problem started when I switched the print
processor to a postscript driver inadvertently; Then after
that did not work I switched it back to Winprint:NT EMF
1.008.
Now every workstation can print to that printer except
that one workstation.
Event log shows "Print Event ID 61 - Win32 error code 3003
(Oxbbb).
I have tried all I can to resolve this and I am at the end
of my short, knowledge rope.
PLEASE HELP.
Many Thanks Prior, as always.
Paul

AAAARRRGGHh - Print Problem by PaulB

PaulB
Sat Oct 25 10:53:43 CDT 2003

I take that back about the postscript print driver - it
actually appears to be something to do with AppleTalk
network. I just restarted my server after a test and it
shows, in this order in the event log:
1)"printer could not be registered because a printer of
the same name already exists on this appletalk network",
2)"the printer has been removed from this appletalk
network", 3)"the printer is now available to the appletalk
network".
I hope some can make heads-tails from this; I am still
trying.
Thanks
Paul
>-----Original Message-----
>I have an SBS2000 network and everyone/everything is
>pretty good but one workstation can not print to one
>network printer (our check printer, unfortunately).
>
>I believe the problem started when I switched the print
>processor to a postscript driver inadvertently; Then
after
>that did not work I switched it back to Winprint:NT EMF
>1.008.
>Now every workstation can print to that printer except
>that one workstation.
>Event log shows "Print Event ID 61 - Win32 error code
3003
>(Oxbbb).
>I have tried all I can to resolve this and I am at the
end
>of my short, knowledge rope.
>PLEASE HELP.
>Many Thanks Prior, as always.
>Paul
>.
>

Re: AAAARRRGGHh - Print Problem by Marina

Marina
Sat Oct 25 11:05:04 CDT 2003

What kind of a printer is it? What OS on the clients?

Marina

"PaulB" <anonymous@discussions.microsoft.com> schreef in bericht
news:097701c39b0e$579b2a60$a501280a@phx.gbl...
> I have an SBS2000 network and everyone/everything is
> pretty good but one workstation can not print to one
> network printer (our check printer, unfortunately).
>
> I believe the problem started when I switched the print
> processor to a postscript driver inadvertently; Then after
> that did not work I switched it back to Winprint:NT EMF
> 1.008.
> Now every workstation can print to that printer except
> that one workstation.
> Event log shows "Print Event ID 61 - Win32 error code 3003
> (Oxbbb).
> I have tried all I can to resolve this and I am at the end
> of my short, knowledge rope.
> PLEASE HELP.
> Many Thanks Prior, as always.
> Paul



Re: AAAARRRGGHh - Print Problem by PaulB

PaulB
Sat Oct 25 11:21:56 CDT 2003

I just got it. It was a Okidata ML590, and all network is
Win2000. It turns out that I had to enter in the IP and
port name in the registry. Apparently when I loaded the
appletalk driver, it erases the IP and port name to make
it available for its network.
Thank you for response though.
I have another prblem to get to now. I will probably be
writing in for more help a little later.
Thanks
Paul
>-----Original Message-----
>What kind of a printer is it? What OS on the clients?
>
>Marina
>
>"PaulB" <anonymous@discussions.microsoft.com> schreef in
bericht
>news:097701c39b0e$579b2a60$a501280a@phx.gbl...
>> I have an SBS2000 network and everyone/everything is
>> pretty good but one workstation can not print to one
>> network printer (our check printer, unfortunately).
>>
>> I believe the problem started when I switched the print
>> processor to a postscript driver inadvertently; Then
after
>> that did not work I switched it back to Winprint:NT EMF
>> 1.008.
>> Now every workstation can print to that printer except
>> that one workstation.
>> Event log shows "Print Event ID 61 - Win32 error code
3003
>> (Oxbbb).
>> I have tried all I can to resolve this and I am at the
end
>> of my short, knowledge rope.
>> PLEASE HELP.
>> Many Thanks Prior, as always.
>> Paul
>
>
>.
>

Re: AAAARRRGGHh - Print Problem by Rick

Rick
Sat Oct 25 14:08:52 CDT 2003

Why are you using Appletalk with an all windows 2000 network?

Rick in the Midwest

"PaulB" <anonymous@discussions.microsoft.com> wrote in message
news:045701c39b14$1bab2cc0$a001280a@phx.gbl...
> I just got it. It was a Okidata ML590, and all network is
> Win2000. It turns out that I had to enter in the IP and
> port name in the registry. Apparently when I loaded the
> appletalk driver, it erases the IP and port name to make
> it available for its network.
> Thank you for response though.
> I have another prblem to get to now. I will probably be
> writing in for more help a little later.
> Thanks
> Paul
> >-----Original Message-----
> >What kind of a printer is it? What OS on the clients?
> >
> >Marina
> >
> >"PaulB" <anonymous@discussions.microsoft.com> schreef in
> bericht
> >news:097701c39b0e$579b2a60$a501280a@phx.gbl...
> >> I have an SBS2000 network and everyone/everything is
> >> pretty good but one workstation can not print to one
> >> network printer (our check printer, unfortunately).
> >>
> >> I believe the problem started when I switched the print
> >> processor to a postscript driver inadvertently; Then
> after
> >> that did not work I switched it back to Winprint:NT EMF
> >> 1.008.
> >> Now every workstation can print to that printer except
> >> that one workstation.
> >> Event log shows "Print Event ID 61 - Win32 error code
> 3003
> >> (Oxbbb).
> >> I have tried all I can to resolve this and I am at the
> end
> >> of my short, knowledge rope.
> >> PLEASE HELP.
> >> Many Thanks Prior, as always.
> >> Paul
> >
> >
> >.
> >