thr3ads.net - samba - [Samba] still can't print to samba printer from winxp [Mar 2003]

If this information is useful, please help other people find it:
Share via:

Jeff D. Hamann

2003-Mar-18 00:27 UTC

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

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 = 50000

#============================ 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

2003-Mar-18 00:35 UTC

head link

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

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 = 50000
>
> #============================ 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: jht@samba.org

Joel Hammer

2003-Mar-18 12:06 UTC

head link

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

Joel Hammer

2003-Mar-18 21:00 UTC

head link

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

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" <Joel@HammersHome.com>
> To: "Jeff D. Hamann" <jeff_hamann@hamanndonald.com>;
<samba@lists.samba.org>
> 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
> > >
> > >
> >
>

Joel Hammer

2003-Mar-19 02:52 UTC

head link

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

This looks ok.
Are you sure the error messages you submitted were actually errors
associated with your lack of print access?

Joel

Joel Hammer

2003-Mar-19 03:00 UTC

head link

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

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 = 50000
> 
> #============================ 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

Possibly Parallel Threads

Search for more apparently analagous threads

samba - Mar 2003 - still can't print to samba printer from winxp

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

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

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

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

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

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

Possibly Parallel Threads