Help please: cannot print using lpd

I want to print files from a Linux (SuSE 10) system to an XP Home system
with an HP printer attached. XP is fully up to date with SP2 and all
subsequent updates.

First, this is what *does* work.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~
On the XP PC (192.168.x.x):
----------------------------------------
1. I installed sdilpd.exe
(http://www.bmtmicro.com/BMTCatalog/win/sdilpd.html and set up the
printer queue.

2. "netstat -a" confirmed that lpd was listening on port 515.

3. "telnet 192.168.x.x 515" confirmed that I could connect locally to
the server.


On the Linux PC:
-----------------------
1. "telnet 192.168.x.x 515" confirmed that I could connect remotely to
the server.

2. I set up a printer, and printed successfully to the XP printer.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~


Although everything worked exactly as I wanted, the snag is that sdildp
is on a 30-day trial. Looking for an alternative approach, I discovered
belatedly that XP appears to have built-in lpd support, so I uninstalled
sdilpd and then did the following:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~
On the XP PC:
--------------------
1. I set up the lpd server (Control PanelAdministrative
ToolsServices).

2. "netstat -a" confirmed that lpd was listening on port 515.

3. "telnet 192.168.x.x 515" confirmed that I could connect locally to
the server.

4. I attempted to configure a printer, setting up an LPR port on
192.168.x.x. This failed, with the long error message stating that it
could go no further.

On the Linux PC:
-----------------------
1. "telnet 192.168.x.x 515" did not connect remotely to the server, and
timed out.

2. Wireshark on the XP machine confirmed that the telnet connect request
from the Linux machine did reach the XP machine, but the server did not
respond in any way.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~

BOTTOM LINE: I am mystified as to why I cannot configure the printer on
the XP machine, and why local telnet requests to the server work on the
XP, but do not work across the LAN, even though I have already proved
there is nothing wrong with the LAN connectivity.

Ideas anyone?

--
Ian

"Ian" wrote in message
news
I want to print files from a Linux (SuSE 10) system to an XP Home system
with an HP printer attached. XP is fully up to date with SP2 and all
subsequent updates.

First, this is what *does* work.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~
On the XP PC (192.168.x.x):
----------------------------------------
1. I installed sdilpd.exe
(http://www.bmtmicro.com/BMTCatalog/win/sdilpd.html and set up the
printer queue.

2. "netstat -a" confirmed that lpd was listening on port 515.

3. "telnet 192.168.x.x 515" confirmed that I could connect locally to
the server.


On the Linux PC:
-----------------------
1. "telnet 192.168.x.x 515" confirmed that I could connect remotely to
the server.

2. I set up a printer, and printed successfully to the XP printer.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~


Although everything worked exactly as I wanted, the snag is that sdildp
is on a 30-day trial. Looking for an alternative approach, I discovered
belatedly that XP appears to have built-in lpd support, so I uninstalled
sdilpd and then did the following:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~
On the XP PC:
--------------------
1. I set up the lpd server (Control PanelAdministrative
ToolsServices).

2. "netstat -a" confirmed that lpd was listening on port 515.

3. "telnet 192.168.x.x 515" confirmed that I could connect locally to
the server.

4. I attempted to configure a printer, setting up an LPR port on
192.168.x.x. This failed, with the long error message stating that it
could go no further.

On the Linux PC:
-----------------------
1. "telnet 192.168.x.x 515" did not connect remotely to the server, and
timed out.

2. Wireshark on the XP machine confirmed that the telnet connect request
from the Linux machine did reach the XP machine, but the server did not
respond in any way.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~

BOTTOM LINE: I am mystified as to why I cannot configure the printer on
the XP machine, and why local telnet requests to the server work on the
XP, but do not work across the LAN, even though I have already proved
there is nothing wrong with the LAN connectivity.

Ideas anyone?


Maybe Samba would do what you want
(you may get better help on a Linux group)

http://www.linuxprinting.org/kpfeifl...1th-draft.html

From: philo
Date: Sat, 29 Mar 2008 Time: 08:25:40

Maybe Samba would do what you want
(you may get better help on a Linux group)

http://www.linuxprinting.org/kpfeifl...a-HOWTO-Collec
tion-3.0-PrintingChapter-11th-draft.html



Hi Philo,

Yes, Samba would probably work, but I don't really want to get into the
hassle of setting it up just for printing.

In any case, I still want to know why the server in the SDI LPD package
works, but the built-in XP lpd server appears to be listening but
doesn't hear anything.

--
Ian

"Ian" wrote in message
...
From: philo
Date: Sat, 29 Mar 2008 Time: 08:25:40

Maybe Samba would do what you want
(you may get better help on a Linux group)

http://www.linuxprinting.org/kpfeifl...a-HOWTO-Collec
tion-3.0-PrintingChapter-11th-draft.html



Hi Philo,

Yes, Samba would probably work, but I don't really want to get into the
hassle of setting it up just for printing.

In any case, I still want to know why the server in the SDI LPD package
works, but the built-in XP lpd server appears to be listening but
doesn't hear anything.



Sorry I don't know anything about SDI...
but I can tell you that it's no big deal to setup Samba
(though I have not done so any time recently)

Be sure that the Windows Firewall port 515 is open for all applications as
well as any other firewall software installed.

The application that runs the LPD Service is tcpsvcs.exe. Also on XP, LPD
service is configured for manual start. If you need this running all the
time be sure to set up the service to Automatic.




--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"philo" wrote in message
...

"Ian" wrote in message
...
From: philo
Date: Sat, 29 Mar 2008 Time: 08:25:40

Maybe Samba would do what you want
(you may get better help on a Linux group)

http://www.linuxprinting.org/kpfeifl...a-HOWTO-Collec
tion-3.0-PrintingChapter-11th-draft.html



Hi Philo,

Yes, Samba would probably work, but I don't really want to get into the
hassle of setting it up just for printing.

In any case, I still want to know why the server in the SDI LPD package
works, but the built-in XP lpd server appears to be listening but
doesn't hear anything.



Sorry I don't know anything about SDI...
but I can tell you that it's no big deal to setup Samba
(though I have not done so any time recently)

From: "Alan Morris [MSFT]"
Date: Mon, 31 Mar 2008 Time: 11:16:52

Be sure that the Windows Firewall port 515 is open for all applications as
well as any other firewall software installed.

Understood.


The application that runs the LPD Service is tcpsvcs.exe. Also on XP, LPD
service is configured for manual start. If you need this running all the
time be sure to set up the service to Automatic.

Understood. I did all that.


The facts remain that:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. I was successful in printing from the Linux machine when running the
third-party program SDILPD on port 515 on the XP machine. So there are
no firewall or LAN connectivity issues.

2. When running the tcpsvcs LPD on the XP, I could not print, even
though it was listening on 515 (and I could telnet locally to 515).

3. When attempting to connect from the Linux machine to the XP server
(using "telnet 192.168.x.x 515"), the TCP SYN request arrived at the
XP, but the server ignored it.

4. When I tried to create an LPR printer under XP, this failed, with the
error message that I had provided incorrect address and/or incorrect
printer information. I tried both the IP address of the machine
(192.168.x.x) and 127.0.0.1, and provided the name of an existing local
printer that already works. Printing a test page did not work -- the
error message said there was a printer error or the printer was busy.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Questions:

1. As the printer creation process failed, does this explain why the XP
server does not respond to SYN requests from the Linux machine?

2. Where am I going wrong in trying to create the LPR printer?

--
Ian

LPD service works fine on XP. I sounds like there is something blocking the
515 port. I'm not sure how telnet works.

If you are attempting to create an LPR Port printer on XP to the XP machine
as a loopback printer that also works but it does not make any sense to do
this.


Can you use lpr.exe from another XP machine to send a text based file to the
XP shared printer. The printer must be shared from XP in order for the LPD
service to make this available to the Unix client.

lpr -S XPmachinewithLPD -P printersharename text.txt

lpq -S -P

will query the LPD service on XP.

What version on Linux? There's a Sun compatibility registry key.

Search the microsoft knowledge base. The only way to configure the service
is by registry values.





--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"Ian" wrote in message
...
From: "Alan Morris [MSFT]"
Date: Mon, 31 Mar 2008 Time: 11:16:52

Be sure that the Windows Firewall port 515 is open for all applications as
well as any other firewall software installed.

Understood.


The application that runs the LPD Service is tcpsvcs.exe. Also on XP, LPD
service is configured for manual start. If you need this running all the
time be sure to set up the service to Automatic.

Understood. I did all that.


The facts remain that:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. I was successful in printing from the Linux machine when running the
third-party program SDILPD on port 515 on the XP machine. So there are no
firewall or LAN connectivity issues.

2. When running the tcpsvcs LPD on the XP, I could not print, even though
it was listening on 515 (and I could telnet locally to 515).

3. When attempting to connect from the Linux machine to the XP server
(using "telnet 192.168.x.x 515"), the TCP SYN request arrived at the XP,
but the server ignored it.

4. When I tried to create an LPR printer under XP, this failed, with the
error message that I had provided incorrect address and/or incorrect
printer information. I tried both the IP address of the machine
(192.168.x.x) and 127.0.0.1, and provided the name of an existing local
printer that already works. Printing a test page did not work -- the error
message said there was a printer error or the printer was busy.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Questions:

1. As the printer creation process failed, does this explain why the XP
server does not respond to SYN requests from the Linux machine?

2. Where am I going wrong in trying to create the LPR printer?

--
Ian