Greetings,
I have setup a Linux Samba server with guest access to the printers and
a share (/tmp). I can access the folder share from a Windows 2000
Workstation with the guest user all right.
However, when I try to access the printer I get "Access denied, unable
to connect". The samba log for this machine shows the following error:
----------
[2003/02/07 18:07:14, 0] smbd/service.c:make_connection(251)
luna (192.168.69.3) couldn't find service
::{2227a280-3aea-1069-a2de-08002b30309d}
----------
I have found that the service mentioned is the printer in the Windows
registry.
If I set log level to 3 I get the following relevant errors:
----------
[2003/02/07 18:07:14, 3] smbd/sec_ctx.c:set_sec_ctx(328)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2003/02/07 18:07:14, 3] smbd/service.c:find_service(140)
checking for home directory ::{2227a280-3aea-1069-a2de-08002b30309d}
gave (NULL)
[2003/02/07 18:07:14, 3] smbd/service.c:find_service(155)
checking whether ::{2227a280-3aea-1069-a2de-08002b30309d} is a valid
printer name...
[2003/02/07 18:07:14, 3] smbd/service.c:find_service(167)
::{2227a280-3aea-1069-a2de-08002b30309d} is not a valid printer name
[2003/02/07 18:07:14, 3] smbd/service.c:find_service(209)
find_service() failed to find service
::{2227a280-3aea-1069-a2de-08002b30309d}
[2003/02/07 18:07:14, 0] smbd/service.c:make_connection(251)
luna (192.168.69.3) couldn't find service
::{2227a280-3aea-1069-a2de-08002b30309d}
[2003/02/07 18:07:14, 3] smbd/error.c:error_packet(94)
error string = No such file or directory
[2003/02/07 18:07:14, 3] smbd/error.c:error_packet(109)
error packet at smbd/reply.c(164) cmd=117 (SMBtconX)
NT_STATUS_BAD_NETWORK_NAME
----------
However I can access the printer from a Windows 98 station and print.
This behavior has been reproduced with Mandrake 8.2(samba 2.2.3-10) and
RedHat 7.3(samba 2.2.7) with Windows 2000 Professional 2195. I have
also tried an older version of samba(2.2.2) to the same avail. I get
the same results when using USER security.
Here is my smb.conf:
----------
[global]
workgroup = GROUPE
server string = Samba Server (gaia)
security = SHARE
log file = /var/log/samba/%m.log
log level = 3
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = No
guest account = pcguest
hosts allow = 192.168.69. 127.
[printers]
comment = All Printers
path = /var/spool/samba
guest ok = Yes
printable = Yes
browseable = No
[tmp]
path = /tmp
public = yes
writable = no
printable = no
----------
Any help would be appreciated.
Etienne
Hmmm. found the solution myself. The best solution is to add the following line to the [printer] section in smb.conf: use client driver = yes This forces the Windows 2000 (and XP?) to properly treat the printer as a remote device and not locally attached. I found this on http://www2.sis.pitt.edu/~josephm/tips.html and later in the smb.conf man page... RTFM!!!! I believe that adding a [print$] section worked also. Another solution is in the way to Add the share in Windows 2000. If you add a NEW local port with name \\server\printer_share then it works like a charm. Found this solution on http://www.essenz.com/support/comp.unix.bsd.freebsd.misc/Nov/10/208529.html cheers, Etienne On Fri, 2003-02-07 at 18:11, Etienne Tourigny wrote:> Greetings, > > I have setup a Linux Samba server with guest access to the printers and > a share (/tmp). I can access the folder share from a Windows 2000 > Workstation with the guest user all right. > > However, when I try to access the printer I get "Access denied, unable > to connect". The samba log for this machine shows the following error: > > ---------- > [2003/02/07 18:07:14, 0] smbd/service.c:make_connection(251) > luna (192.168.69.3) couldn't find service > ::{2227a280-3aea-1069-a2de-08002b30309d} > ---------- > > I have found that the service mentioned is the printer in the Windows > registry. > > If I set log level to 3 I get the following relevant errors: > > ---------- > [2003/02/07 18:07:14, 3] smbd/sec_ctx.c:set_sec_ctx(328) > setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 > [2003/02/07 18:07:14, 3] smbd/service.c:find_service(140) > checking for home directory ::{2227a280-3aea-1069-a2de-08002b30309d} > gave (NULL) > [2003/02/07 18:07:14, 3] smbd/service.c:find_service(155) > checking whether ::{2227a280-3aea-1069-a2de-08002b30309d} is a valid > printer name... > [2003/02/07 18:07:14, 3] smbd/service.c:find_service(167) > ::{2227a280-3aea-1069-a2de-08002b30309d} is not a valid printer name > [2003/02/07 18:07:14, 3] smbd/service.c:find_service(209) > find_service() failed to find service > ::{2227a280-3aea-1069-a2de-08002b30309d} > [2003/02/07 18:07:14, 0] smbd/service.c:make_connection(251) > luna (192.168.69.3) couldn't find service > ::{2227a280-3aea-1069-a2de-08002b30309d} > [2003/02/07 18:07:14, 3] smbd/error.c:error_packet(94) > error string = No such file or directory > [2003/02/07 18:07:14, 3] smbd/error.c:error_packet(109) > error packet at smbd/reply.c(164) cmd=117 (SMBtconX) > NT_STATUS_BAD_NETWORK_NAME > ---------- > > However I can access the printer from a Windows 98 station and print. > This behavior has been reproduced with Mandrake 8.2(samba 2.2.3-10) and > RedHat 7.3(samba 2.2.7) with Windows 2000 Professional 2195. I have > also tried an older version of samba(2.2.2) to the same avail. I get > the same results when using USER security. > > Here is my smb.conf: > > ---------- > [global] > workgroup = GROUPE > server string = Samba Server (gaia) > security = SHARE > log file = /var/log/samba/%m.log > log level = 3 > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > dns proxy = No > guest account = pcguest > hosts allow = 192.168.69. 127. > > [printers] > comment = All Printers > path = /var/spool/samba > guest ok = Yes > printable = Yes > browseable = No > > [tmp] > path = /tmp > public = yes > writable = no > printable = no > ---------- > > > Any help would be appreciated. > > Etienne
Gerald (Jerry) Carter
2003-Feb-12 15:33 UTC
[Samba] Windows 2000 printing to public printer
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10 Feb 2003, Etienne Tourigny wrote:> Hmmm. found the solution myself. > > The best solution is to add the following line to the [printer] section > in smb.conf: > > use client driver = yes > > This forces the Windows 2000 (and XP?) to properly treat the printer as > a remote device and not locally attached. I found this on > http://www2.sis.pitt.edu/~josephm/tips.html and later in the smb.conf > man page... RTFM!!!!Nope. use client driver is a severe hack to be used **only** when you want to install the drivers locally on the client for a given printer. Generally disable spoolss is cleaner, but that is a global setting. The use client driver parameter allows drivers to be made available on the server for some printers and not others. Never enable it for a printer that will provide drivers on the server. cheers, jerry ---------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team ---------------------- http://www.samba.org GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc "You can never go home again, Oatman, but I guess you can shop there." --John Cusack - "Grosse Point Blank" (1997) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+SmlEIR7qMdg1EfYRAsePAJ4v/tARyYA2giIQmqTyDqHptuNZnwCdGM6/ kthtIDcjoRU8//MOrltAmlM=J+mV -----END PGP SIGNATURE-----