RE: [Samba] print$ share problem URGENT - BUG
Whoops! "extract" is really "expand".
"expand /?" at the command prompt shows the options for expanding files
with the trailing underscore. I use
expand -r *.??_
which creates new, renamed, expanded files from the compressed ones.
A word of warning: some compressed files do not have the original name
embedded within the file. This will created expanded files with the
underscore removed, not replaced with the original last character. In
these situations, one must refer to the .INF file to discover the true
name.
What would be great is if someone wrote a simple Win32 program that
parses the .INF print driver installation file, expanding the files as
necessary, getting files from the local workstation and uploading them
into the appropriate [print$] share directory, and doing the adddriver
and setdriver RPCs. That way print driver installation would be free of
the hoops imposed by drivers & show add printer wizard goofiness.
Thanks,
Peter Hurley
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 27, 2003 8:18 AM
To: [EMAIL PROTECTED]
Subject: RE: [Samba] print$ share problem URGENT - BUG
Heya, I'm looking at having to do the same thing... a couple of
manufacturer's drivers either fail to install on samba, or install
incorrectly. I'm using a W2k pro client but have no extract command.
Is this a program that comes with w2k or something you got from
somewhere else?
Btw, thanks for explaining the {2227a280-3aea...} messages. Googling
turned up lots of hits, but the only suggested solution was to delete
the key from the client's registry (which didn't seem like a good idea
to me). I didn't know that InProcServer was depended on by some driver
installations. Realizing that samba as a print-server w/ automatic
driver download has more hurdles than getting a devmode set...
Thanks for letting me know about extract,
~ Daniel
On Wednesday, March 26, 2003 5:45 PM Peter Hurley wrote:
> I do not know why your logs are showing an smb_panic(), but
> the failure
> to make a connection to {2227a280-3aea} is because the printer
> driver is attempting to open the "Printers" InProcServer on the remote
> print server.
>
> ***Snippet from logs***
> [2003/03/26 14:33:08, 0] smbd/service.c:make_connection(252)
> donglesvr (10.217.7.11) couldn't find service
> ::{2227a280-3aea-1069-a2de-08002b30309d}
> ***
>
> Since the print server is a Samba machine (that has no registry or
> capability to run InProcServers), that service doesn't exist. I had
> this happen to me when trying to add additional drivers from my W2k
> workstation to our 2.2.7a Samba server for a new HP2200
> network printer.
>
> The solution I used was to add them manually via rpcclient on
> the Samba
> server itself. It took me quite a while. Basically the process is:
> 1) expand the driver files on your local W2k workstation, via the
> "extract" command line utility.
> 2) copy the driver files up to the appropriate directory on the
> [print$] share. See section 6.2.1 of the Samba HOWTO for the
> directory
> structure.
> Basically, NT4/W2K/XP drivers go in W32X86 and 95/98/Me go into WIN40.
> 3) on the samba server, run rpcclient.
> 4) at the rpcclient prompt, use "adddriver" to install the files into
> the appropriate architecture location. The tricky part of this is
> looking at the *.INF file to determine what parameters go where in the
> adddriver command. The format is:
>
> adddriver "Architecture" "LongPrinterName:DriverFile:DataFile:
> ConfigFile:HelpFile:LanguageMonitorFile:DataType:ListOfFiles"
>
> See rpcclient() man page for list of Architectures.
> The ListOfFiles are the files not already specified in the other
> parameters.
>
> For example,
>
> adddriver "Windows NT x86" "HP LaserJet 2200 Series PCL 6:
> HPBF3222.DLL:HPBF3224.PMD:HPBF3220.DLL:HPBF3220.HLP:HPBMMON.DLL:RAW:
> HPBAFD32.DLL,HPBFTM32.DLL,HPDOMON.DLL,HPBHEALR.DLL"
>
> 5) when you have added the driver successfully, then you use the
> "setdriver" command (still at the rpcclient prompt) to associate the
> printer share with the driver.
>
> For example,
>
> setdriver "hp2200" "HP LaserJet 2200 Series PCL 6"
>
> Now automatic driver download should work.
>
> This process was so painful, eventually I'm going to look at the
> Imprints package to see if that works (there's a reference to this
> package in section 6.3 of the Samba HOWTO).
>
> Thanks,
>
> Peter Hurley
> [EMAIL PROTECTED]
>
>
> -Original Message-
> From: [EMAIL PROTE
Re: [Samba] print$ share problem URGENT - BUG
On Thu, Mar 27, 2003 at 01:14:58AM +, [EMAIL PROTECTED] wrote: > On Wed, Mar 26, 2003 at 10:33:13PM +0100, Stéphane Purnelle wrote: > > Why I have no answer for my questions ? > > > > I repeat the situation : > > RedHat 8.0 with samba 2.2.8 compiled wiwth ldapsam and acl-support > > I need the print$ share and this system dont't work. > > I explain : > > when I add a driver, the system copy the data to the share, but after > > the copy, w2k display a message "the process cannot finish". > > > > If I look in the log of machine, I found a > > > > ... > > === > > [2003/03/26 14:29:50, 0] lib/fault.c:fault_report(39) > > > > INTERNAL ERROR: Signal 11 in pid 16328 (2.2.8) > > > > Please read the file BUGS.txt in the distribution > > > > [2003/03/26 14:29:50, 0] lib/fault.c:fault_report(41) > > > > === > > Please add the following line to your smb.conf file : > > panic action = /bin/sleep 9 > > and reproduce the problem. You will find a sleep process > left on the machine. Using ps, find the parent of this > process (it will be an smbd process), then attach to > it using gdb. Type 'bt' to get a backtrace of the problem > and please mail it to the list. > > Thanks, > > Jeremy. I've been having touble getting gdb to work - ever since I upgraded to the RH 2.2.18-27.8.0 errata kernels... I wonder if all our changing uid back and forth has caused the kernel to decide we shouldn't be ptrace'ed... I'm glad jelmer added that backtrace() code... Andrew Bartlett
Re: [Samba] print$ share problem URGENT - BUG
On Wed, Mar 26, 2003 at 10:33:13PM +0100, Stéphane Purnelle wrote: > Why I have no answer for my questions ? > > I repeat the situation : > RedHat 8.0 with samba 2.2.8 compiled wiwth ldapsam and acl-support > I need the print$ share and this system dont't work. > I explain : > when I add a driver, the system copy the data to the share, but after > the copy, w2k display a message "the process cannot finish". > > If I look in the log of machine, I found a > > ... > === > [2003/03/26 14:29:50, 0] lib/fault.c:fault_report(39) > > INTERNAL ERROR: Signal 11 in pid 16328 (2.2.8) > > Please read the file BUGS.txt in the distribution > > [2003/03/26 14:29:50, 0] lib/fault.c:fault_report(41) > > === Please add the following line to your smb.conf file : panic action = /bin/sleep 9 and reproduce the problem. You will find a sleep process left on the machine. Using ps, find the parent of this process (it will be an smbd process), then attach to it using gdb. Type 'bt' to get a backtrace of the problem and please mail it to the list. Thanks, Jeremy.
RE: [Samba] print$ share problem URGENT - BUG
I do not know why your logs are showing an smb_panic(), but the failure
to make a connection to {2227a280-3aea} is because the printer
driver is attempting to open the "Printers" InProcServer on the remote
print server.
***Snippet from logs***
[2003/03/26 14:33:08, 0] smbd/service.c:make_connection(252)
donglesvr (10.217.7.11) couldn't find service
::{2227a280-3aea-1069-a2de-08002b30309d}
***
Since the print server is a Samba machine (that has no registry or
capability to run InProcServers), that service doesn't exist. I had
this happen to me when trying to add additional drivers from my W2k
workstation to our 2.2.7a Samba server for a new HP2200 network printer.
The solution I used was to add them manually via rpcclient on the Samba
server itself. It took me quite a while. Basically the process is:
1) expand the driver files on your local W2k workstation, via the
"extract" command line utility.
2) copy the driver files up to the appropriate directory on the
[print$] share. See section 6.2.1 of the Samba HOWTO for the directory
structure.
Basically, NT4/W2K/XP drivers go in W32X86 and 95/98/Me go into WIN40.
3) on the samba server, run rpcclient.
4) at the rpcclient prompt, use "adddriver" to install the files into
the appropriate architecture location. The tricky part of this is
looking at the *.INF file to determine what parameters go where in the
adddriver command. The format is:
adddriver "Architecture" "LongPrinterName:DriverFile:DataFile:
ConfigFile:HelpFile:LanguageMonitorFile:DataType:ListOfFiles"
See rpcclient() man page for list of Architectures.
The ListOfFiles are the files not already specified in the other
parameters.
For example,
adddriver "Windows NT x86" "HP LaserJet 2200 Series PCL 6:
HPBF3222.DLL:HPBF3224.PMD:HPBF3220.DLL:HPBF3220.HLP:HPBMMON.DLL:RAW:
HPBAFD32.DLL,HPBFTM32.DLL,HPDOMON.DLL,HPBHEALR.DLL"
5) when you have added the driver successfully, then you use the
"setdriver" command (still at the rpcclient prompt) to associate the
printer share with the driver.
For example,
setdriver "hp2200" "HP LaserJet 2200 Series PCL 6"
Now automatic driver download should work.
This process was so painful, eventually I'm going to look at the
Imprints package to see if that works (there's a reference to this
package in section 6.3 of the Samba HOWTO).
Thanks,
Peter Hurley
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Stéphane Purnelle
Sent: Wednesday, March 26, 2003 4:33 PM
To: [EMAIL PROTECTED]; samba US; samba-tech
Subject: Re: [Samba] print$ share problem URGENT - BUG
Why I have no answer for my questions ?
I repeat the situation :
RedHat 8.0 with samba 2.2.8 compiled wiwth ldapsam and acl-support
I need the print$ share and this system dont't work.
I explain :
when I add a driver, the system copy the data to the share, but after
the copy, w2k display a message "the process cannot finish".
If I look in the log of machine, I found a
...
===
[2003/03/26 14:29:50, 0] lib/fault.c:fault_report(39)
INTERNAL ERROR: Signal 11 in pid 16328 (2.2.8)
Please read the file BUGS.txt in the distribution
[2003/03/26 14:29:50, 0] lib/fault.c:fault_report(41)
===
[2003/03/26 14:29:50, 0] lib/util.c:smb_panic(1094)
PANIC: internal error
.
[2003/03/26 14:32:36, 1] smbd/ipc.c:api_fd_reply(292)
api_fd_reply: INVALID PIPE HANDLE: 7351
[2003/03/26 14:32:41, 1] smbd/ipc.c:api_fd_reply(292)
api_fd_reply: INVALID PIPE HANDLE: 7352
[2003/03/26 14:33:08, 0] smbd/service.c:make_connection(252)
donglesvr (10.217.7.11) couldn't find service
::{2227a280-3aea-1069-a2de-08002b30309d}
My print$ share is in a other share
//sys/samba.pub/printer
sys is a share
printer is the print$ share
How can I found the service {2227a280-3aea-1069-a2de-08002b-30309d} ?
can anybody help me.
My samba server need to be in production and fastly.
Le mer 26/03/2003 à 14:41, [EMAIL PROTECTED] a écrit :
> Hello
>
> I try to install drivers from CD to print$ share.
> I use the APW for that, but when the system have finish to copy
drivers,
> w2k says that he cannot complete the process.
>
> And the log of the machine says :
>
> [2003/03/26 11:56:41, 0] passdb/pdb_ldap.c:ldap_connect_system(316)
> ldap_connect_system: Binding to ldap server as
> "cn=manager,dc=corman,dc=be"
> [2003/03/26 14:26:53, 0] smbd/service.c:make_connection(252)
> donglesvr (10.217.7.11) couldn't find service
> ::{2227a280-3aea-1069-a2de-08002b30309d}
> [2003/03/26 14:28:04, 0] passdb/pdb_ldap.c:ldap_connect_system(316)
> ldap_connect_system: Binding to ldap ser
RE: [Samba] print$ share problem URGENT - BUG
You wrote: >>Why I have no answer for my questions ? You only sent the original posting to this list a few hours ago. If you need this kind of immediate support, where somebody gets back to you within hours (or maybe even minutes) guaranteed you might consider paying for it, see the Commercial Support section on: http://us1.samba.org/samba/support/ -Marc
Re: [Samba] print$ share problem URGENT - BUG
Why I have no answer for my questions ?
I repeat the situation :
RedHat 8.0 with samba 2.2.8 compiled wiwth ldapsam and acl-support
I need the print$ share and this system dont't work.
I explain :
when I add a driver, the system copy the data to the share, but after
the copy, w2k display a message "the process cannot finish".
If I look in the log of machine, I found a
...
===
[2003/03/26 14:29:50, 0] lib/fault.c:fault_report(39)
INTERNAL ERROR: Signal 11 in pid 16328 (2.2.8)
Please read the file BUGS.txt in the distribution
[2003/03/26 14:29:50, 0] lib/fault.c:fault_report(41)
===
[2003/03/26 14:29:50, 0] lib/util.c:smb_panic(1094)
PANIC: internal error
.
[2003/03/26 14:32:36, 1] smbd/ipc.c:api_fd_reply(292)
api_fd_reply: INVALID PIPE HANDLE: 7351
[2003/03/26 14:32:41, 1] smbd/ipc.c:api_fd_reply(292)
api_fd_reply: INVALID PIPE HANDLE: 7352
[2003/03/26 14:33:08, 0] smbd/service.c:make_connection(252)
donglesvr (10.217.7.11) couldn't find service
::{2227a280-3aea-1069-a2de-08002b30309d}
My print$ share is in a other share
//sys/samba.pub/printer
sys is a share
printer is the print$ share
How can I found the service {2227a280-3aea-1069-a2de-08002b-30309d} ?
can anybody help me.
My samba server need to be in production and fastly.
Le mer 26/03/2003 à 14:41, [EMAIL PROTECTED] a écrit :
> Hello
>
> I try to install drivers from CD to print$ share.
> I use the APW for that, but when the system have finish to copy drivers,
> w2k says that he cannot complete the process.
>
> And the log of the machine says :
>
> [2003/03/26 11:56:41, 0] passdb/pdb_ldap.c:ldap_connect_system(316)
> ldap_connect_system: Binding to ldap server as
> "cn=manager,dc=corman,dc=be"
> [2003/03/26 14:26:53, 0] smbd/service.c:make_connection(252)
> donglesvr (10.217.7.11) couldn't find service
> ::{2227a280-3aea-1069-a2de-08002b30309d}
> [2003/03/26 14:28:04, 0] passdb/pdb_ldap.c:ldap_connect_system(316)
> ldap_connect_system: Binding to ldap server as
> "cn=manager,dc=corman,dc=be"
> [2003/03/26 14:28:04, 0] passdb/pdb_ldap.c:ldap_connect_system(316)
> ldap_connect_system: Binding to ldap server as
> "cn=manager,dc=corman,dc=be"
> [2003/03/26 14:28:04, 0] passdb/pdb_ldap.c:ldap_connect_system(316)
> ldap_connect_system: Binding to ldap server as
> "cn=manager,dc=corman,dc=be"
> [2003/03/26 14:29:41, 1] smbd/service.c:make_connection(636)
> donglesvr (10.217.7.11) connect to service print$ as user root (uid=0,
> gid=0) (pid 16328)
> [2003/03/26 14:29:49, 1] smbd/service.c:make_connection(636)
> donglesvr (10.217.7.11) connect to service print$ as user root (uid=0,
> gid=0) (pid 16328)
> [2003/03/26 14:29:49, 1] smbd/service.c:close_cnum(677)
> donglesvr (10.217.7.11) closed connection to service print$
> [2003/03/26 14:29:49, 1] smbd/service.c:make_connection(636)
> donglesvr (10.217.7.11) connect to service print$ as user root (uid=0,
> gid=0) (pid 16328)
> [2003/03/26 14:29:50, 1] smbd/service.c:close_cnum(677)
> donglesvr (10.217.7.11) closed connection to service print$
> [2003/03/26 14:29:50, 0] lib/fault.c:fault_report(38)
> ===
> [2003/03/26 14:29:50, 0] lib/fault.c:fault_report(39)
> INTERNAL ERROR: Signal 11 in pid 16328 (2.2.8)
> Please read the file BUGS.txt in the distribution
> [2003/03/26 14:29:50, 0] lib/fault.c:fault_report(41)
> ===
> [2003/03/26 14:29:50, 0] lib/util.c:smb_panic(1094)
> PANIC: internal error
> [2003/03/26 14:29:50, 0] passdb/pdb_ldap.c:ldap_connect_system(316)
> ldap_connect_system: Binding to ldap server as
> "cn=manager,dc=corman,dc=be"
> [2003/03/26 14:29:50, 1] smbd/service.c:make_connection(636)
> donglesvr (10.217.7.11) connect to service print$ as user root (uid=0,
> gid=0) (pid 16602)
> [2003/03/26 14:30:18, 1] smbd/service.c:close_cnum(677)
> donglesvr (10.217.7.11) closed connection to service print$
> [2003/03/26 14:30:18, 1] smbd/service.c:make_connection(636)
> donglesvr (10.217.7.11) connect to service print$ as user root (uid=0,
> gid=0) (pid 16602)
> [2003/03/26 14:31:05, 1] smbd/service.c:make_connection(636)
> donglesvr (10.217.7.11) connect to service print$ as user root (uid=0,
> gid=0) (pid 16602)
> [2003/03/26 14:31:05, 1] smbd/service.c:close_cnum(677)
> donglesvr (10.217.7.11) closed connection to service print$
> [2003/03/26 14:31:05, 1] smbd/service.c:make_connection(636)
> donglesvr (10.217.7.11) connect to service print$ as user root (uid=0,
> gid=0) (pid 16602)
> [2003/03/26 14:31:06, 1] smbd/service.c:close_cnum(677)
> donglesvr (10.217.7.11) closed connection to service print$
> [2003/03/26 14:31:06, 0] lib/fault.c:fault_report(38)
> ===
> [2003/03/26 14:31:06, 0] lib/fault.c:fault_rep
