Re: [Samba] Printing failure through PDC

2008-03-25 Thread Rich West 
Volker Lendecke wrote:
 On Sat, Mar 22, 2008 at 04:12:26PM -0400, Rich West wrote:
   
 I recently went through a system upgrade, which resulted in an upgrade 
 of Samba to 3.0.28a.  This is for a home network, so it isn't heavily 
 taxed (only by family members), but I do use the environment as a 
 sandbox of sorts for stuff that I plan to roll in to production in the 
 office.
 

 Can you recompile Samba with -g and run it under valgrind?
 The logfile of the segfault would be very helpful.

Hrmm.. I'll have to work on that, then. :(  I'm running off of the
standard RPM...

-Rich

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

Re: [Samba] Printing failure through PDC

2008-03-25 Thread Rich West 

Rich West wrote:
I recently went through a system upgrade, which resulted in an upgrade 
of Samba to 3.0.28a.  This is for a home network, so it isn't heavily 
taxed (only by family members), but I do use the environment as a 
sandbox of sorts for stuff that I plan to roll in to production in the 
office.


I had some funky issues with authentication to start with after the 
upgrade, so I went through the (somewhat) painful steps to set up 
ldapsam.  I managed to get all of the users set up within LDAP, and 
all of the machine accounts configured within LDAP, and logging in and 
out of the domain with roaming profiles (using samba to create the 
machine accounts and user accounts turned out to be the right way to 
do it rather than to hand modify the LDAP accounts).


The only remaining issue is with regard to printing: When a Windows 
user connects to the printer (hppsc2510) and sends a test page, they 
get an error stating that the job failed to print (unable to create 
print job).  In the log.system name file, I can see:

[..snip...]
--
At this point, I'm truly unsure of what is failing.  I've made sure 
that /var/spool/samba exists and is world writeable.  I tried moving 
it out of the way and testing, and samba gave an appropriate error in 
the log file.  I tried shutting down CUPS and doing the same test, and 
samba gave an appropriate error then, too.


I can print via the command line on the samba server (a Fedora 8 box) 
as the same user who is logged in on the windows box...


Any ideas?

-Rich


Actually, I made some headway.. I found that we had an old setting for 
disable spoolss = yes in place.  Removing that allowed things to get a 
tiny bit forward.  I'm not seeing much logged, but I am getting Test 
page failed to print ... Access is denied. from the windows side.  
The Windows box successfully gets the driver as supplied by the samba 
server, so I know that part is working.  I'm just not sure what the 
Access is denied. is referring to...


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

Re: [Samba] Recovering Windows computer account string

2008-03-23 Thread Rich West 
It might be easier to remove the system from the domain and re-add it to 
the domain...


-Rich


We utilize the smbpasswd text file back end. One machine (VM machine) 
suddenly thinks its entry in the Samba PDC's smbpasswd file is no 
longer correct. Is there a way to fetch that number back out of a 
Windows 2000 workstation and paste it into the smbpasswd file to 
re-trust the workstation?


Thanks!



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

[Samba] Printing failure through PDC

2008-03-22 Thread Rich West 
I recently went through a system upgrade, which resulted in an upgrade 
of Samba to 3.0.28a.  This is for a home network, so it isn't heavily 
taxed (only by family members), but I do use the environment as a 
sandbox of sorts for stuff that I plan to roll in to production in the 
office.


I had some funky issues with authentication to start with after the 
upgrade, so I went through the (somewhat) painful steps to set up 
ldapsam.  I managed to get all of the users set up within LDAP, and all 
of the machine accounts configured within LDAP, and logging in and out 
of the domain with roaming profiles (using samba to create the machine 
accounts and user accounts turned out to be the right way to do it 
rather than to hand modify the LDAP accounts).


The only remaining issue is with regard to printing: When a Windows user 
connects to the printer (hppsc2510) and sends a test page, they get an 
error stating that the job failed to print (unable to create print 
job).  In the log.system name file, I can see:

[2008/03/22 15:03:04, 1] smbd/service.c:make_connection_snum(1033)
 cortex (192.168.56.5) connect to service windows_user initially as 
user windows_user (uid=17361, gid=17362) (pid 26541)

[2008/03/22 16:04:06, 1] smbd/service.c:make_connection_snum(1033)
 cortex (192.168.56.5) connect to service hppsc2510 initially as user 
windows_user (uid=17361, gid=17362) (pid 29537)

[2008/03/22 16:04:06, 0] lib/fault.c:fault_report(41)
 ===
[2008/03/22 16:04:06, 0] lib/fault.c:fault_report(42)
 INTERNAL ERROR: Signal 11 in pid 29537 (3.0.28a-0.fc8)
 Please read the Trouble-Shooting section of the Samba3-HOWTO
[2008/03/22 16:04:06, 0] lib/fault.c:fault_report(44)

 From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2008/03/22 16:04:06, 0] lib/fault.c:fault_report(45)
 ===
[2008/03/22 16:04:06, 0] lib/util.c:smb_panic(1655)
 PANIC (pid 29537): internal error
[2008/03/22 16:04:06, 0] lib/util.c:log_stack_trace(1759)
 BACKTRACE: 10 stack frames:
  #0 smbd(log_stack_trace+0x1c) [0x2accf59c]
  #1 smbd(smb_panic+0x43) [0x2accf683]
  #2 smbd [0x2acbd040]
  #3 /lib64/libpthread.so.0 [0x2c42f540]
  #4 smbd(reply_printopen+0x7e) [0x2ab480de]
  #5 smbd [0x2ab81274]
  #6 smbd(smbd_process+0x7b1) [0x2ab82211]
  #7 smbd(main+0xa20) [0x2ad84260]
  #8 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2d968074]
  #9 smbd [0x2ab13479]
[2008/03/22 16:04:06, 0] lib/fault.c:dump_core(181)
 dumping core in /var/log/samba/cores/smbd
[2008/03/22 16:04:06, 1] smbd/service.c:make_connection_snum(1033)
 cortex (192.168.56.5) connect to service hppsc2510 initially as user 
windows_user (uid=17361, gid=17362) (pid 29540)

[2008/03/22 16:04:06, 0] lib/fault.c:fault_report(41)
 ===
[2008/03/22 16:04:06, 0] lib/fault.c:fault_report(42)
 INTERNAL ERROR: Signal 11 in pid 29540 (3.0.28a-0.fc8)
 Please read the Trouble-Shooting section of the Samba3-HOWTO
[2008/03/22 16:04:06, 0] lib/fault.c:fault_report(44)

 From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2008/03/22 16:04:06, 0] lib/fault.c:fault_report(45)
 ===
[2008/03/22 16:04:06, 0] lib/util.c:smb_panic(1655)
 PANIC (pid 29540): internal error
[2008/03/22 16:04:06, 0] lib/util.c:log_stack_trace(1759)
 BACKTRACE: 10 stack frames:
  #0 smbd(log_stack_trace+0x1c) [0x2accf59c]
  #1 smbd(smb_panic+0x43) [0x2accf683]
  #2 smbd [0x2acbd040]
  #3 /lib64/libpthread.so.0 [0x2c42f540]
  #4 smbd(reply_printopen+0x7e) [0x2ab480de]
  #5 smbd [0x2ab81274]
  #6 smbd(smbd_process+0x7b1) [0x2ab82211]
  #7 smbd(main+0xa20) [0x2ad84260]
  #8 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2d968074]
  #9 smbd [0x2ab13479]
[2008/03/22 16:04:06, 0] lib/fault.c:dump_core(181)
 dumping core in /var/log/samba/cores/smbd
---
Unfortunately, it doesn't actually place anything in 
/var/log/samba/cores/smbd.  At least, it hasn't in the past couple of days.


I turned up the debugging to 9 and went through the same test of 
printing a test page, and I got:

[2008/03/22 14:43:25, 6] smbd/process.c:process_smb(1067)
 got message type 0x0 of len 0x23
[2008/03/22 14:43:25, 3] smbd/process.c:process_smb(1068)
 Transaction 20 of length 39
[2008/03/22 14:43:25, 5] lib/util.c:show_msg(506)
[2008/03/22 14:43:25, 5] lib/util.c:show_msg(516)
 size=35
 smb_com=0x71
 smb_rcls=0
 smb_reh=0
 smb_err=0
 smb_flg=24
 smb_flg2=51207
 smb_tid=1
 smb_pid=65279
 smb_uid=101
 smb_mid=64832
 smt_wct=0
 smb_bcc=0
[2008/03/22 14:43:25, 3] smbd/process.c:switch_message(926)
 switch message SMBtdis (pid 25593) conn 0x2aeaa4b0
[2008/03/22 14:43:25, 3] smbd/sec_ctx.c:set_sec_ctx(241)
 setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/03/22 14:43:25, 5] auth/auth_util.c:debug_nt_user_token(448)
 NT user token: (NULL)
[2008/03/22