I am trying to use the printmig.exe tool to migrate printers from windows server to samba server. this is what I did: 1. I ran printmig.exe on the windows server. 2. Backed up the printers on the windows servers to a cab file. 3. Tried to restore the printers to the sambashare by specifying the target as //sambaShare. But I get the following error: 2006:01:25 15:35:38 Access Granted to: \\sambaShare 2006:01:25 15:35:38 Couldn't start the target spooler 2006:01:25 15:35:38 Remote Tree View Failed Do I need some specila config in smb.conf? In smb.conf I have a addprinter command. I also added [admin$] section in the smb.conf file and set enable asu support = no
The problem is more lack of documentation. The spooler service (internal to smbd) has an associated security that only allows members of BUILTIN\Administrators tro start/stop the spooler service. I recently changed smbd to add the Administrators to anyone that had the 'Domain Admins' sid in their NT token. I can send you that patch but it will only help in domain or ads mode. If you have a standalone server, then you must either be root or create a groupmapping for the Administrators SID and be a member of that group. I'll follow up the rest of this thread over email.
(In reply to comment #1) > The problem is more lack of documentation. The spooler > service (internal to smbd) has an associated security > that only allows members of BUILTIN\Administrators > tro start/stop the spooler service. I recently changed > smbd to add the Administrators to anyone that had the > 'Domain Admins' sid in their NT token. I can send you > that patch but it will only help in domain or ads mode. > > If you have a standalone server, then you must either be root > or create a groupmapping for the Administrators SID and be > a member of that group. > > I'll follow up the rest of this thread over email. > After applying the patches suggested I can migrate the print queues but not the drivers.
Hi Jerry, At debug level 4 I am seeing these errors while migrating drivers to samba server from windows server. [2006/02/21 19:48:14, 3] smbd/process.c:switch_message(900) switch message SMBntcreateX (pid 11413) conn 0x83f00f0 [2006/02/21 19:48:14, 3] smbd/sec_ctx.c:set_sec_ctx(287) setting sec ctx (70001, 70001) - sec_ctx_stack_ndx = 0 [2006/02/21 19:48:14, 4] smbd/nttrans.c:nt_open_pipe(330) nt_open_pipe: Opening pipe \system32\spool\drivers\W32X86\PSCRIPT5.DLL. [2006/02/21 19:48:14, 3] smbd/error.c:error_packet(143) error packet at smbd/nttrans.c(345) cmd=162 (SMBntcreateX) NT_STATUS_OBJECT_NAME_NOT_FOUND [2006/02/21 19:48:14, 3] smbd/process.c:process_smb(1114) Transaction 3400 of length 176 [2006/02/21 19:48:14, 3] smbd/process.c:switch_message(900) switch message SMBntcreateX (pid 11413) conn 0x83f00f0 [2006/02/21 19:48:14, 4] smbd/uid.c:change_to_user(217) change_to_user: Skipping user change - already user [2006/02/21 19:48:14, 4] smbd/nttrans.c:nt_open_pipe(330) nt_open_pipe: Opening pipe \system32\spool\drivers\W32X86\APLWBGR1.PPD. [2006/02/21 19:48:14, 3] smbd/error.c:error_packet(143) error packet at smbd/nttrans.c(345) cmd=162 (SMBntcreateX) NT_STATUS_OBJECT_NAME_NOT_FOUND [2006/02/21 19:48:14, 3] smbd/process.c:process_smb(1114) Transaction 3401 of length 170 [2006/02/21 19:48:14, 3] smbd/process.c:switch_message(900) switch message SMBntcreateX (pid 11413) conn 0x83f00f0 [2006/02/21 19:48:14, 4] smbd/uid.c:change_to_user(217) change_to_user: Skipping user change - already user [2006/02/21 19:48:14, 4] smbd/nttrans.c:nt_open_pipe(330) nt_open_pipe: Opening pipe \system32\spool\drivers\W32X86\PS5UI.DLL. [2006/02/21 19:48:14, 3] smbd/error.c:error_packet(143) error packet at smbd/nttrans.c(345) cmd=162 (SMBntcreateX) NT_STATUS_OBJECT_NAME_NOT_FOUND [2006/02/21 19:48:14, 3] smbd/process.c:process_smb(1114) Transaction 3402 of length 174 [2006/02/21 19:48:14, 3] smbd/process.c:switch_message(900) switch message SMBntcreateX (pid 11413) conn 0x83f00f0 [2006/02/21 19:48:14, 4] smbd/uid.c:change_to_user(217) change_to_user: Skipping user change - already user [2006/02/21 19:48:14, 4] smbd/nttrans.c:nt_open_pipe(330) nt_open_pipe: Opening pipe \system32\spool\drivers\W32X86\PSCRIPT.HLP. [2006/02/21 19:48:14, 3] smbd/error.c:error_packet(143) error packet at smbd/nttrans.c(345) cmd=162 (SMBntcreateX) NT_STATUS_OBJECT_NAME_NOT_FOUND [2006/02/21 19:48:14, 3] smbd/process.c:process_smb(1114) Transaction 3403 of length 174 [2006/02/21 19:48:14, 3] smbd/process.c:switch_message(900) switch message SMBntcreateX (pid 11413) conn 0x83f00f0 [2006/02/21 19:48:14, 4] smbd/uid.c:change_to_user(217) change_to_user: Skipping user change - already user [2006/02/21 19:48:14, 4] smbd/nttrans.c:nt_open_pipe(330) nt_open_pipe: Opening pipe \system32\spool\drivers\W32X86\PSCRIPT.NTF. [2006/02/21 19:48:14, 3] smbd/error.c:error_packet(143) error packet at smbd/nttrans.c(345) cmd=162 (SMBntcreateX) NT_STATUS_OBJECT_NAME_NOT_FOUND Any idea how to fix these. Thanks, Aarti. (In reply to comment #2) > (In reply to comment #1) > > The problem is more lack of documentation. The spooler > > service (internal to smbd) has an associated security > > that only allows members of BUILTIN\Administrators > > tro start/stop the spooler service. I recently changed > > smbd to add the Administrators to anyone that had the > > 'Domain Admins' sid in their NT token. I can send you > > that patch but it will only help in domain or ads mode. > > > > If you have a standalone server, then you must either be root > > or create a groupmapping for the Administrators SID and be > > a member of that group. > > > > I'll follow up the rest of this thread over email. > > > > After applying the patches suggested I can migrate the print queues but not the > drivers. >
Are the driver files actually present in the original *.cab file? This appears to be a random bug in the printmig.exe tool itself.
(In reply to comment #4) > Are the driver files actually present in the original > *.cab file? This appears to be a random bug in the > printmig.exe tool itself. > Yes the driver files are present in the cab file.
Following up on a private mail. printmig.exe expects that \\server\admin$\system32\spool\drivers and \\server\print$ point to the same path (just like Windows).