[Samba] Printer on WinXP

2004-01-17 Thread Kurt Pfeifle
Thomas Bergstam thomas at acat.se
Sat Jan 3 18:10:22 GMT 2004
Hi all,

Is it possible to use a printer attached to a WinXP computer from Linux
(Suse) using only console mode, ie. no graphic mode?
Yes.

1. Make sure your WinXP-attached printer is shared.

2. Make sure you use CUPS as a printing system.

3. Make sure you know about CUPS and PPDs.

4. Know that WinXP (Prof!) is capable of using IPP as a print protocol

5. Know that Microsoft, in their unlimited wisdom decided to use as
   a printer URI this:
http://[IP-address of WinXP]:80/[printer-sharename]/.printer

6. Install the printer (assuming IP for WinXP is 11.12.13.14 and
   printer-sharename of printer is my_printer):
lpadmin -p printername -v http://11.12.13.14:80/my_printer/.printer -E -P /path/to/PPD

7. Print to your heart's limits fromt the commandline:

lp -d printername /path/to/printfile

Cheers,
Kurt
P.S:: Please bear in mind, that you may not receive anyone's attention to
  your question, if you continue to miss providing *any* details about
  your system, like XP Home or XP Prof?, Version of SuSE? etc.
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


[Samba] Printer on WinXP

2004-01-03 Thread Thomas Bergstam
Hi all,

Is it possible to use a printer attached to a WinXP computer from Linux
(Suse) using only console mode, ie. no graphic mode?




-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Printer on WinXP

2004-01-03 Thread Joe Cipale
Thomas Bergstam wrote:
 
 Hi all,
 
 Is it possible to use a printer attached to a WinXP computer from Linux
 (Suse) using only console mode, ie. no graphic mode?
 
 --
 To unsubscribe from this list go to the following URL and read the
 instructions:  http://lists.samba.org/mailman/listinfo/samba

Sure, as long as you have an entry for the printer in the /etc/printcap
file, or whatever print paradigm you are using.

Joe
-- 
#--#
#   Penguinix Consulting   #
#--#
#Software development, QA and testing. #
#Linux support and training.   #
#Don't fear the penguin! #
#--#
# Registered Linux user: #309247 http://counter.li.org #
#--#
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Printer on WinXP

2004-01-03 Thread Leonardo Boselli
Il 3 Jan 2004 alle 10:46 Joe Cipale immise in rete
 Thomas Bergstam wrote:
  Is it possible to use a printer attached to a WinXP computer from
  Linux (Suse) using only console mode, ie. no graphic mode?
 Sure, as long as you have an entry for the printer in the
 /etc/printcap file, or whatever print paradigm you are using.

XP allows also to export a printer as lpr so no need to use samba ...
Leonardo Boselli
Firenze
http://www.toscanarail.org


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Printer on WinXP

2004-01-03 Thread John H Terpstra
AOn Sat, 3 Jan 2004, Thomas Bergstam wrote:

 Hi all,

 Is it possible to use a printer attached to a WinXP computer from Linux
 (Suse) using only console mode, ie. no graphic mode?

It sure is. Configuration requirements are covered in the
Samba-HOWTO-Collection.pdf. It makes no difference whether Linux is
running X Windows or not, printing is printing.

- John T.
-- 
John H Terpstra
Email: [EMAIL PROTECTED]
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] still can't print to samba printer from winxp

2003-03-18 Thread Joel Hammer
Without thinking much about this, let me ask. How do you start smbd?
With xinetd or as a freestanding daemon?
Joel
On Mon, Mar 17, 2003 at 04:27:28PM -0800, Jeff D. Hamann wrote:
 I have upgraded samba to 2.2.7a and cannot print to my printer attached to
 my BSD machine. I can use the share dirs, etc, but cannot print. My log file
 contains:
 
 [2003/03/17 16:17:19, 0] lib/util_sock.c:open_socket_in(804)
 bind failed on port 139 socket_addr = 0.0.0.0.
 Error = Address already in use
 [2003/03/17 16:18:02, 0] smbd/service.c:make_connection(252)
 50163099sp (204.250.145.147) couldn't find service c
 [2003/03/17 16:20:46, 0] lib/util_sock.c:open_socket_in(804)
 bind failed on port 139 socket_addr = 0.0.0.0.
 Error = Address already in use
 [2003/03/17 16:22:22, 0] lib/util_sock.c:open_socket_in(804)
 bind failed on port 139 socket_addr = 0.0.0.0.
 Error = Address already in use
 
 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] still can't print to samba printer from winxp

2003-03-18 Thread Joel Hammer
Sometimes xinetd causes trouble. You may be starting it with xinetd and not
know it.
What does netstat -apn | grep 13 show?

Joel
On Tue, Mar 18, 2003 at 09:47:15AM -0800, Jeff D. Hamann wrote:
 I believe I started samba as a freestanding daemon using the
 /usr/local/etc/rc.d/samba.sh start in FreeBSD.  Let me check. Yes, that's
 the case. Is it better to use xinetd these days?
 
 I also have the following entries in my inetd.conf file:
 
 netbios-ssn stream tcp nowait root /usr/local/sbin/smbd smbd
 netbios-ns dgram udp wait root /usr/local/sbin/nmbd nmbd
 
 Jeff.
 
 
 - Original Message -
 From: Joel Hammer [EMAIL PROTECTED]
 To: Jeff D. Hamann [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Sent: Tuesday, March 18, 2003 4:06 AM
 Subject: Re: [Samba] still can't print to samba printer from winxp
 
 
  Without thinking much about this, let me ask. How do you start smbd?
  With xinetd or as a freestanding daemon?
  Joel
  On Mon, Mar 17, 2003 at 04:27:28PM -0800, Jeff D. Hamann wrote:
   I have upgraded samba to 2.2.7a and cannot print to my printer attached
 to
   my BSD machine. I can use the share dirs, etc, but cannot print. My log
 file
   contains:
  
   [2003/03/17 16:17:19, 0] lib/util_sock.c:open_socket_in(804)
   bind failed on port 139 socket_addr = 0.0.0.0.
   Error = Address already in use
   [2003/03/17 16:18:02, 0] smbd/service.c:make_connection(252)
   50163099sp (204.250.145.147) couldn't find service c
   [2003/03/17 16:20:46, 0] lib/util_sock.c:open_socket_in(804)
   bind failed on port 139 socket_addr = 0.0.0.0.
   Error = Address already in use
   [2003/03/17 16:22:22, 0] lib/util_sock.c:open_socket_in(804)
   bind failed on port 139 socket_addr = 0.0.0.0.
   Error = Address already in use
  
  
 
 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] still can't print to samba printer from winxp

2003-03-18 Thread Joel Hammer
This looks ok.
Are you sure the error messages you submitted were actually errors
associated with your lack of print access?

Joel
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] still can't print to samba printer from winxp

2003-03-18 Thread Joel Hammer
Why do you have printable in your homes share?
Which printing system are you using? 
Have you tried something simple like:
print command = echo Tried to print %s  /tmp/printjob  in your printer share.
Are the permissions on /var/spool/samba set properly? 
What type of client are you trying to print from?

Joel


On Mon, Mar 17, 2003 at 04:27:28PM -0800, Jeff D. Hamann wrote:
 I have upgraded samba to 2.2.7a and cannot print to my printer attached to
 my BSD machine. I can use the share dirs, etc, but cannot print. My log file
 contains:
 
 [2003/03/17 16:17:19, 0] lib/util_sock.c:open_socket_in(804)
 bind failed on port 139 socket_addr = 0.0.0.0.
 Error = Address already in use
 [2003/03/17 16:18:02, 0] smbd/service.c:make_connection(252)
 50163099sp (204.250.145.147) couldn't find service c
 [2003/03/17 16:20:46, 0] lib/util_sock.c:open_socket_in(804)
 bind failed on port 139 socket_addr = 0.0.0.0.
 Error = Address already in use
 [2003/03/17 16:22:22, 0] lib/util_sock.c:open_socket_in(804)
 bind failed on port 139 socket_addr = 0.0.0.0.
 Error = Address already in use
 
 
 I'm not sure what this means:
 bind failed on port 139 socket_addr = 0.0.0.0.
 
 which socket_addr? client or server?
 
 
 Here's my smb.conf file:
 
 [global]
 workgroup = skookum
 server string = Samba Server [FreeBSD 2.2.7a]
 load printers = yes
 printcap name = /etc/printcap
 log file = /var/log/log.%m
 max log size = 50
 encrypt passwords = yes
 security = user
 socket options = TCP_NODELAY
 disable spoolss = yes
 log file = /var/log/samba.log
 max log size = 5
 
 # Share Definitions ==
 [homes]
 comment = Home Directories
 browseable = no
 writeable = no
 printable = yes
 [printers]
 comment = All Printers
 path = /var/spool/samba
 browseable = yes
 guest ok = yes
 writeable = no
 printable = yes
 
 
 
 -- 
 To unsubscribe from this list go to the following URL and read the
 instructions:  http://lists.samba.org/mailman/listinfo/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] still can't print to samba printer from winxp

2003-03-17 Thread John H Terpstra
On Mon, 17 Mar 2003, Jeff D. Hamann wrote:

 I have upgraded samba to 2.2.7a and cannot print to my printer attached to
 my BSD machine. I can use the share dirs, etc, but cannot print. My log file
 contains:

 [2003/03/17 16:17:19, 0] lib/util_sock.c:open_socket_in(804)
 bind failed on port 139 socket_addr = 0.0.0.0.
 Error = Address already in use
 [2003/03/17 16:18:02, 0] smbd/service.c:make_connection(252)
 50163099sp (204.250.145.147) couldn't find service c
 [2003/03/17 16:20:46, 0] lib/util_sock.c:open_socket_in(804)
 bind failed on port 139 socket_addr = 0.0.0.0.
 Error = Address already in use
 [2003/03/17 16:22:22, 0] lib/util_sock.c:open_socket_in(804)
 bind failed on port 139 socket_addr = 0.0.0.0.
 Error = Address already in use

This means that a process is already using tcp port 139. You can use:
netstat -ap | grep 139

to find which process that may be.



 I'm not sure what this means:
 bind failed on port 139 socket_addr = 0.0.0.0.

Have you configured inetd to run smbd?


 which socket_addr? client or server?

Server.

Do you have a firewall? It may be blocking access to the loopback address
(127.0.0.1).

- John T.



 Here's my smb.conf file:

 [global]
 workgroup = skookum
 server string = Samba Server [FreeBSD 2.2.7a]
 load printers = yes
 printcap name = /etc/printcap
 log file = /var/log/log.%m
 max log size = 50
 encrypt passwords = yes
 security = user
 socket options = TCP_NODELAY
 disable spoolss = yes
 log file = /var/log/samba.log
 max log size = 5

 # Share Definitions
 ==
 [homes]
 comment = Home Directories
 browseable = no
 writeable = no
 printable = yes
 [printers]
 comment = All Printers
 path = /var/spool/samba
 browseable = yes
 guest ok = yes
 writeable = no
 printable = yes





-- 
John H Terpstra
Email: [EMAIL PROTECTED]
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba