I am running Centos 4 and I am trying to use a printer on a Windows domain that is connected to a Windows XP Pro computer.
If I do
smbclient //ComputerName/PrinterName password -U UserName
and then /> printmode text /> print /tmp/test.txt
the printer works.
However, if I setup the printer and check the CUPS printers.conf, it appears to be correct, but I get NT_STATUS_UNSUCCESSFUL when I print from OpenOffice or try to print from an Apple iBook.
Any suggestions on what I should check?
Todd
Todd Cary todd@aristesoftware.com wrote:
I am running Centos 4 and I am trying to use a printer on a Windows domain that is connected to a Windows XP Pro
computer.
If I do smbclient //ComputerName/PrinterName password -U UserName and then /> printmode text /> print /tmp/test.txt the printer works. However, if I setup the printer and check the CUPS printers.conf, it appears to be correct, but I get NT_STATUS_UNSUCCESSFUL when I print from OpenOffice or try to print from an Apple iBook. Any suggestions on what I should check?
I'm not answering your question directly, because to do so, I'd need to see your CUPS configuration.
That aside, have you considered setting up your Windows Server with a LPD or an IPP queue for the printer?
If you can, avoid SMB printing -- for countless reasons. God knows I do so even for Windows clients. Microsoft's own NT reliability studies show the NT spooler is the reason why NT crashes/hangs 8% of the time.
On Wed, 2005-12-28 at 17:33, Bryan J. Smith wrote:
I'm not answering your question directly, because to do so, I'd need to see your CUPS configuration.
That aside, have you considered setting up your Windows Server with a LPD or an IPP queue for the printer?
If you can, avoid SMB printing -- for countless reasons. God knows I do so even for Windows clients. Microsoft's own NT reliability studies show the NT spooler is the reason why NT crashes/hangs 8% of the time.
I second that. Many months ago I finally enabled LPD printing on the windows print server an linux to windows printing has been much simpler and less trouble ever since. SMB printing was always a problem and it required exposing a windows password.
Byron -
I got my wife a Mac (she has only been asking for one for three years): iBook G4. Well her printer is hooked up to a PC and she likes to roam around the house with the wireless connection. Can your suggestion be implemented in this environment?
Todd
Bryan J. Smith wrote:
Todd Cary todd@aristesoftware.com wrote:
I am running Centos 4 and I am trying to use a printer on a Windows domain that is connected to a Windows XP Pro
computer.
If I do smbclient //ComputerName/PrinterName password -U UserName and then /> printmode text /> print /tmp/test.txt the printer works. However, if I setup the printer and check the CUPS printers.conf, it appears to be correct, but I get NT_STATUS_UNSUCCESSFUL when I print from OpenOffice or try to print from an Apple iBook. Any suggestions on what I should check?
I'm not answering your question directly, because to do so, I'd need to see your CUPS configuration.
That aside, have you considered setting up your Windows Server with a LPD or an IPP queue for the printer?
If you can, avoid SMB printing -- for countless reasons. God knows I do so even for Windows clients. Microsoft's own NT reliability studies show the NT spooler is the reason why NT crashes/hangs 8% of the time.
Todd Cary todd@aristesoftware.com wrote:
Byron - I got my wife a Mac (she has only been asking for one for three years): iBook G4. Well her printer is hooked up to a PC and she likes to roam around the house with the
wireless
connection. Can your suggestion be implemented in this environment?
Yes. Line Printer Daemon (LPD) is a well-established, legacy standard. It uses port 515 and is governed by IETF RFC1179:
http://www.ietf.org/rfc/rfc1179.txt
The new IETF standard is the Internet Printing Protocol (IPP). It uses port 631 (both clear and SSL) and is governed by IETF RFC2910: http://www.ietf.org/rfc/rfc2910.txt
Another port to be aware of is port 9100, commonly referred to by it's vendor-centric names like a "HP JetDirect" port. The technical name is the [HP] Page Description Language datastream (PDL-datastream) port. Microsoft calls it a "TCP/IP port", and you set it up as a local port, which maps back to the IP address/port.
BSD/SysV UNIX LPD, LPR and LPRng offer LPD services.
CUPS offers IPP by default, and it can also offer LPD services. CUPS, as a client, can also use other methods including LPD, IPP, SMB, PDL-datastream, etc... CUPS also offers a replacement spooler for NT/2000/XP that radically simplifies/centralizes administration for Windows clients.
Windows Servers can offer SMB and LPD, and newer versions can offer IPP services. Windows NT/2000 clients can use SMB, LPD and PDL-datastream, with XP adding IPP. For IPP, LPD and PDL-datastream, you set it up as a "local port."
Macs can also use LPD and PDL-datastream, with newer MacOS X releases supporting IPP.
I have most ports closed on my router except the obvious (POP, SMTP, FTP, Interbase, SQL Server, MySQL and VNC). Could I have a port closed that CUPS needs? I have identical problems with Linux (RHE) and Mac Tiger.
Todd
Bryan J. Smith wrote:
Todd Cary todd@aristesoftware.com wrote:
Byron - I got my wife a Mac (she has only been asking for one for three years): iBook G4. Well her printer is hooked up to a PC and she likes to roam around the house with the
wireless
connection. Can your suggestion be implemented in this environment?
Yes. Line Printer Daemon (LPD) is a well-established, legacy standard. It uses port 515 and is governed by IETF RFC1179:
http://www.ietf.org/rfc/rfc1179.txt
The new IETF standard is the Internet Printing Protocol (IPP). It uses port 631 (both clear and SSL) and is governed by IETF RFC2910: http://www.ietf.org/rfc/rfc2910.txt
Another port to be aware of is port 9100, commonly referred to by it's vendor-centric names like a "HP JetDirect" port. The technical name is the [HP] Page Description Language datastream (PDL-datastream) port. Microsoft calls it a "TCP/IP port", and you set it up as a local port, which maps back to the IP address/port.
BSD/SysV UNIX LPD, LPR and LPRng offer LPD services.
CUPS offers IPP by default, and it can also offer LPD services. CUPS, as a client, can also use other methods including LPD, IPP, SMB, PDL-datastream, etc... CUPS also offers a replacement spooler for NT/2000/XP that radically simplifies/centralizes administration for Windows clients.
Windows Servers can offer SMB and LPD, and newer versions can offer IPP services. Windows NT/2000 clients can use SMB, LPD and PDL-datastream, with XP adding IPP. For IPP, LPD and PDL-datastream, you set it up as a "local port."
Macs can also use LPD and PDL-datastream, with newer MacOS X releases supporting IPP.
On Wed, 2005-12-28 at 21:53 -0800, Todd Cary wrote:
I have most ports closed on my router except the obvious (POP, SMTP, FTP, Interbase, SQL Server, MySQL and VNC). Could I have a port closed that CUPS needs? I have identical problems with Linux (RHE) and Mac Tiger.
Only the LPD server needs port 515 open, for IPP it's port 631. LPD is clear text. IPP can be clear text or SSL. I don't think the Windows Server IPP implementation does SSL though.
*Problem solved!
*It was the damn M$ Firewall on my wife's computer! Yes, allow Printing and Fax was checked in the Exceptions, but for some unknown reason it did not allow the printing to go through. Turned off the Firewall and the spooled pages came flying out!
Even though I know just enough to keep my Linux servers running (actually, once they are up I am able forget them until we lose power - then I need to power them back on :-) ), I know that somewhere in there is an answer. Not so with Windows.
Thank you for trying to help with this....
Todd
Bryan J. Smith wrote:
Todd Cary todd@aristesoftware.com wrote:
Byron - I got my wife a Mac (she has only been asking for one for three years): iBook G4. Well her printer is hooked up to a PC and she likes to roam around the house with the
wireless
connection. Can your suggestion be implemented in this environment?
Yes. Line Printer Daemon (LPD) is a well-established, legacy standard. It uses port 515 and is governed by IETF RFC1179:
http://www.ietf.org/rfc/rfc1179.txt
The new IETF standard is the Internet Printing Protocol (IPP). It uses port 631 (both clear and SSL) and is governed by IETF RFC2910: http://www.ietf.org/rfc/rfc2910.txt
Another port to be aware of is port 9100, commonly referred to by it's vendor-centric names like a "HP JetDirect" port. The technical name is the [HP] Page Description Language datastream (PDL-datastream) port. Microsoft calls it a "TCP/IP port", and you set it up as a local port, which maps back to the IP address/port.
BSD/SysV UNIX LPD, LPR and LPRng offer LPD services.
CUPS offers IPP by default, and it can also offer LPD services. CUPS, as a client, can also use other methods including LPD, IPP, SMB, PDL-datastream, etc... CUPS also offers a replacement spooler for NT/2000/XP that radically simplifies/centralizes administration for Windows clients.
Windows Servers can offer SMB and LPD, and newer versions can offer IPP services. Windows NT/2000 clients can use SMB, LPD and PDL-datastream, with XP adding IPP. For IPP, LPD and PDL-datastream, you set it up as a "local port."
Macs can also use LPD and PDL-datastream, with newer MacOS X releases supporting IPP.
On Thu, 2005-12-29 at 09:13 -0800, Todd Cary wrote:
Problem solved! It was the damn M$ Firewall on my wife's computer! Yes, allow Printing and Fax was checked in the Exceptions, but for some unknown reason it did not allow the printing to go through.
LPD is probably not be considered "printing" from the standpoint of MS. Not sure IPP is either -- have to check.
Turned off the Firewall and the spooled pages came flying out! Even though I know just enough to keep my Linux servers running (actually, once they are up I am able forget them until we lose power
- then I need to power them back on :-) ), I know that somewhere in
there is an answer. Not so with Windows. Thank you for trying to help with this....
Just allow 515/tcp and 515/udp through for LPD, and 631/tcp and 631/udp for IPP. This is not difficult to do at all for XPSP2's firewall.
-- Bryan
P.S. Also note, SMB changes whether you use the [not-so] encrypted RPC (port 445) or not (various ports).
Byron -
Do you where one can change the XP_SP2 firewall at the granularity you have indicated?
Also, do I need to make any changes to my D-Link Wireless Router's firewall?
Todd
Bryan J. Smith wrote:
On Thu, 2005-12-29 at 09:13 -0800, Todd Cary wrote:
Problem solved! It was the damn M$ Firewall on my wife's computer! Yes, allow Printing and Fax was checked in the Exceptions, but for some unknown reason it did not allow the printing to go through.
LPD is probably not be considered "printing" from the standpoint of MS. Not sure IPP is either -- have to check.
Turned off the Firewall and the spooled pages came flying out! Even though I know just enough to keep my Linux servers running (actually, once they are up I am able forget them until we lose power
- then I need to power them back on :-) ), I know that somewhere in
there is an answer. Not so with Windows. Thank you for trying to help with this....
Just allow 515/tcp and 515/udp through for LPD, and 631/tcp and 631/udp for IPP. This is not difficult to do at all for XPSP2's firewall.
-- Bryan
P.S. Also note, SMB changes whether you use the [not-so] encrypted RPC (port 445) or not (various ports).
On Thu, 2005-12-29 at 09:24 -0800, Todd Cary wrote:
Byron - Do you where one can change the XP_SP2 firewall at the granularity you have indicated?
A quick Google search turned up this step-by-step: http://www.windowsecurity.com/articles/Customizing-Windows-Firewall.html
Also note Microsoft KB875357, which has a lot of good info on reading the logs and other troubleshooting: http://support.microsoft.com/default.aspx?kbid=875357
Also, do I need to make any changes to my D-Link Wireless Router's firewall?
If the traffic is not traversing the wireless router's Internet connection, no.
-
Bryan J. Smith -
Scot L. Harris -
Todd Cary