I got a network print server which works fine in WinXP but could not set it up in Linux SuSE 9.1. In WinXP it uses an lpr port 9100. It has a static IP address whic I am able to ping in SuSE 9.1. Any idea?

Port 9100 is a standard hp jetdirect printing port among other things. You just need to add a printer via tcp/ip and specify that port with the proper drivers. If that's what you're asking..

Thoreau

Thanks for reply. That is exactly what I did. I tried the following sequence:
I selected Print Directly to a network printer
Then selected Direct TCP Port Printing
I entered the IP address of the print server in the field of Host name of the printer server
Port number 9100
When I do test, I get the following:
can not connect to the print server, Check if the print server is running (which is the case) or contact your administrator.
Am I following the right procedure?
Moreover, when I change the port number to 515 it tells me the print server is accessable but when I print, the status led on the print server comes on for a while and goes off and no printing.

hey linx win

are you using cups? I got my minolta magicolor laser 2300DL to work as a network printer, having downloaded the driver via www.linuxprinting.org, but I had to enter URI as 192.168.1.200:9100 where 192.168.1.200 is the IP address I manually entered into my printer. Interestingly, and I am using kde, on Printing manager it shows up in the properties tab as:

URI: socket://192.168.1.200:9100

but on the Information tab it shows as:

URI: ipp://suse90:631/printers/magicolor where suse90 is my machine name (localhost) and 'magicolor' is the printer shortname.

HTH

minrich

Thanks for reply. I am using SuSE 9.1, CUPS and HP 6P printer. I have no problem with the driver for my printer. I connected my printer directly to my Linux box and I am able to print. My problem is with the print server. I have entered the IP address of my print server 192.168.1.20 but I did not allow me to enter it as you suggested as 192.168.1.20:9100. It gave an error message. I also got the same result you got in KDE print manager:

Device: socket://192.168.1.20:9100/
and
URI: ipp://linux:631/printers/lpr1

But no printing. It seems to me that the problem with port 9100 because when I use port 515 or port 631 the status light starts blinking but no printing while for port 9100 it does not do anything at all.

I am not particularly familiar with the HP 6P, but a quick search of HP's 'support and drivers' for it suggests to me that you need the 'jetdirect' network ?card? in the printer. Is this a correct assumption? And is your printer now connected to your LAN? If so please make sure that your built-in firewall is disabled - otherwise the 9100 port will (or at least maybe) blocked. if it works ok with WinXP then it must be the port that is blocked.

Thanks alot. I disabled the firewall but no success. Any other idea.

okay

in a console type:

ncap -v 192.168.1.0/24

check for 192.168.1.20 (your printer IP) mine shows the following ports open:

Port State Service
23/tcp open telnet
80/tcp open http
427/tcp open svrloc
515/tcp open printer
631/tcp open ipp
5001/tcp open commplex-link
9100/tcp open jetdirect


Let me know what yours shows.

HTH

Thanks for reply. This is what I got:

]linux:/home/mas # ncap -v 192.168.1.20/24
bash: ncap: command not found

I repeated this command without being root and got the same results.

Does that mean that I am messing a package?

Hi linx win,

can you set yout LJ6 in standard lpr mode monitoring the port 515? The jetdirect (aka "raw") is not too standard - my LJ1150 works fine connected by lpr via an SMC access point, the setup in CUPS was a breeze.

HTH, Peter

PBSchmidt

Thanks for reply. Would you please explain how I can do that?

Hi linx win,

well, that is above my knowledge - I can rememebr, the JetDirect offers a configuration either via telnet or HTTP, so maybe you can find an option there that enables standard lpr queue. This also works under Windows, you only have to add a new port as "generic TCP/IP" and set the protocol to lpr. The JetDirect interface should show you the queue name (usually lp1 or similar).

But, as I stated, this is theory, for I do not have a jetDirect at hand to check it.

HTH, Peter

PBSchmidt
minrich
Thoreau

Thanks. I got it working on another Linux SuSE 9.1 box. I did the following:
Yast2 >>su >> hardware >> printer >> other not detected >> configure >> Print directly to network printer >> next >> Remote LPD Queue >> 192.168.1.20/24 >> lpr1 >> next
Then I followed the normal printer setup. I got it printing correctly on this box. However, when I try to do the same on the other PCs in the network it will not allow me to go to the step where I can select the printer manufacturer and type. So, when I print from those PC, It does print but I do not get the right document print.

Moreover, during my trial and error efforts I have done some thing wrong and deleted the cups server. I tried re-installing the cups rpms but no success. Any idea how I can restore cups server to its original status?

Finally, problem solved. I copied the ppd file for the printer from the PC that has it working to /etc/cups/ppd folder on the PCs where printing did not work. Now all Linux PCs on my network are enjoying printing on my print server. Thanks to all of you for support and fruitful hints.