Hi I am using a BART bootable CD to access the Samba server to map a drive and run Norton ghost. This works okay when I make an image of the full hard disc on the client; the image file is written successfully to the Samba drive. However when I try to create an image of just a partition on the hard disc, I get errors from Ghost. First it says that there might not be enough space and spanning will be required. It fails by saying that it can't write to the file, but it does create a file of zero size. Eventually it closes with this error: Cannot create image file DOS error: access denied (0x0005) (662) log.smbd has the following error suggesting I should report the problem: ==> log.smbd <== [2005/06/06 09:28:30, 4] libsmb/ntlm_check.c:ntlm_password_check(373) ntlm_password_check: Checking LM password [2005/06/06 09:28:30, 4] auth/auth_sam.c:sam_account_ok(119) sam_account_ok: Checking SMB password for user cadtest [2005/06/06 09:28:30, 5] auth/auth_sam.c:logon_hours_ok(100) logon_hours_ok: user cadtest allowed to logon at this time (Mon Jun 6 09:28:30 2005 ) 2005/06/06 09:28:30, 5] auth/auth_util.c:make_server_info_sam(860) make_server_info_sam: made server info for user cadtest -> cadtest [2005/06/06 09:28:30, 3] auth/auth.c:check_ntlm_password(267) check_ntlm_password: sam authentication for user [CADTEST] succeeded [2005/06/06 09:28:30, 5] auth/auth.c:check_ntlm_password(291) check_ntlm_password: PAM Account for user [cadtest] succeeded [2005/06/06 09:28:30, 2] auth/auth.c:check_ntlm_password(300) check_ntlm_password: authentication for user [CADTEST] -> [CADTEST] -> [cadtest] succeeded [2005/06/06 09:28:30, 5] auth/auth_util.c:free_user_info(1380) attempting to free (and zero) a user_info structure ==> log.smbd <== [2005/06/06 09:31:46, 0] smbd/reply.c:reply_mknew(1306) Attempt to create file (images/PC3311C.GHO) with volid set - please report this ==> log.smbd <== [2005/06/06 09:31:46, 0] smbd/reply.c:reply_mknew(1306) Attempt to create file (images/PC3311C.GHO) with volid set - please report this Thanks for your help.
Jeremy, I see the error message still in the 3.0.20a source code. Do you want to follow up on this?
Can you send in an ethereal sniffer trace of this please ? It may be a simple fix (just removing a check) but I need to see the actual request on the wire. Thanks, Jeremy.
closing. No response.