Mac OS X 10.3 can't print to Win 2K DC print queue

[Bob C]

We have a Win 2000 DC (DC1) that is setup for DNS, DHCP,
and Print server on our network. We run a mix of PC's
and Mac's (G4's).

The output from the print queue in question first goes to
a paused print queue. The HP 5M has a 192.xxx.xxx.xxx IP
to keep it internal.

The Mac's were able to print to the DC up to a couple of
weeks ago, and then they could not print at all. DC1 is
current with all Windows Updates and security patches.

The standard Mac print setup is LPD/LPR; <DC1/DNS IP>;
<DC PrintQueueName>.

1. Printing to the pay print queue from the Mac showed
the print job starting then goes to "will retry in 30
seconds" and stays there. Inspection of the DC1 print
queue shows no print job in the queue.

2. Testing through another W2K DC (DC2) print queue to
the same printer allowed printing normally.

3. Test printing directly to the HP 5M printer IP printed
ok.

We have isolated the problem to something that has
changed on DC1. Everything checks out OK on both Mac and
DC1, nothing has visibly changed, nor has any
adminstrator made any changes to the settings.

We have spent a lot of time trying to run this problem to
ground, but still no luck.

Any help would be greatly appreciated.

Thanks,

Bob Cummings
(e-mail address removed)

 

[Alan Morris\(MSFT\)]

Do the Windows clients connect fine using the lpr.exe command? Since you
are running DHCP on this server, I recommend picking up a QFE for the LPD
Service or running the LPD service on a machine that does not run multiple
services under the tcpsvcs.exe binary.


http://support.microsoft.com/default.aspx?scid=kb;en-us;841027

--
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.

 

[Frank]

MS has always been weak in this area. I've had the same issues. Check
out http://lpd.brooksnet.com and they should be able to help you out.
The LPR/LPD commands - protocol is a Pain in the arse with MS.....

Hope they can help you,

Terry

*************************************

Do the Windows clients connect fine using the lpr.exe command? Since you
are running DHCP on this server, I recommend picking up a QFE for the LPD
Service or running the LPD service on a machine that does not run multiple
services under the tcpsvcs.exe binary.


http://support.microsoft.com/default.aspx?scid=kb;en-us;841027

--
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.

We have a Win 2000 DC (DC1) that is setup for DNS, DHCP,
and Print server on our network. We run a mix of PC's
and Mac's (G4's).

The output from the print queue in question first goes to
a paused print queue. The HP 5M has a 192.xxx.xxx.xxx IP
to keep it internal.

The Mac's were able to print to the DC up to a couple of
weeks ago, and then they could not print at all. DC1 is
current with all Windows Updates and security patches.

The standard Mac print setup is LPD/LPR; <DC1/DNS IP>;
<DC PrintQueueName>.

1. Printing to the pay print queue from the Mac showed
the print job starting then goes to "will retry in 30
seconds" and stays there. Inspection of the DC1 print
queue shows no print job in the queue.

2. Testing through another W2K DC (DC2) print queue to
the same printer allowed printing normally.

3. Test printing directly to the HP 5M printer IP printed
ok.

We have isolated the problem to something that has
changed on DC1. Everything checks out OK on both Mac and
DC1, nothing has visibly changed, nor has any
adminstrator made any changes to the settings.

We have spent a lot of time trying to run this problem to
ground, but still no luck.

Any help would be greatly appreciated.

Thanks,

Bob Cummings
(e-mail address removed)

 

[Guest]

My SysAdmin would probably not be able to justify the expenditure, since the
Mac's had no problem printing through LPR previously, and the fact that as a
test, we were able to print from another domain controllers queue to the same
printer.

My personal experience with Microsoft has been that when you turn something
off, the next update(s) will turn it back on, and/or vice-versa.

MS has always been weak in this area. I've had the same issues. Check
out http://lpd.brooksnet.com and they should be able to help you out.
The LPR/LPD commands - protocol is a Pain in the arse with MS.....

Hope they can help you,

Terry

*************************************

Do the Windows clients connect fine using the lpr.exe command? Since you
are running DHCP on this server, I recommend picking up a QFE for the LPD
Service or running the LPD service on a machine that does not run multiple
services under the tcpsvcs.exe binary.


http://support.microsoft.com/default.aspx?scid=kb;en-us;841027

--
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.

We have a Win 2000 DC (DC1) that is setup for DNS, DHCP,
and Print server on our network. We run a mix of PC's
and Mac's (G4's).

The output from the print queue in question first goes to
a paused print queue. The HP 5M has a 192.xxx.xxx.xxx IP
to keep it internal.

The Mac's were able to print to the DC up to a couple of
weeks ago, and then they could not print at all. DC1 is
current with all Windows Updates and security patches.

The standard Mac print setup is LPD/LPR; <DC1/DNS IP>;
<DC PrintQueueName>.

1. Printing to the pay print queue from the Mac showed
the print job starting then goes to "will retry in 30
seconds" and stays there. Inspection of the DC1 print
queue shows no print job in the queue.

2. Testing through another W2K DC (DC2) print queue to
the same printer allowed printing normally.

3. Test printing directly to the HP 5M printer IP printed
ok.

We have isolated the problem to something that has
changed on DC1. Everything checks out OK on both Mac and
DC1, nothing has visibly changed, nor has any
adminstrator made any changes to the settings.

We have spent a lot of time trying to run this problem to
ground, but still no luck.

Any help would be greatly appreciated.

Thanks,

Bob Cummings
(e-mail address removed)