generic blog of schmidi2

Last night I upgraded our company filesserver from debian entch to lenny. After a short test with my linux client and on my windows terminalserver, it seemed to work correctly. Well, this was quiet different the next morning.

Problem
The next day after the upgrade from debian etch to lenny, some guys were able to use all shares of the fileservers, others were not (those were a little angry).

Find cause
To debug the problem, add following two lines to your /etc/samba/smb.conf

log level = 3
log file = /tmp/samba.log

Now watch the logfile while you access the the share. This is my log:

…
[2009/05/06 18:34:50, 3] smbd/process.c:process_smb(1549)
 Transaction 328 of length 128 (0 toread)
[2009/05/06 18:34:50, 3] smbd/process.c:switch_message(1361)
 switch message SMBtrans2 (pid 13791) conn 0×96ff070
[2009/05/06 18:34:50, 3] smbd/trans2.c:call_trans2qfilepathinfo(3939)
 call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004
[2009/05/06 18:34:50, 3] smbd/trans2.c:call_trans2qfilepathinfo(3993)
 call_trans2qfilepathinfo: SMB_VFS_STAT of shell32.dll failed (No such file or directory)
[2009/05/06 18:34:50, 3] smbd/error.c:reply_unix_error(154)
 unix_error_packet: error string = No such file or directory
[2009/05/06 18:34:50, 3] smbd/error.c:error_packet_set(61)
 error packet at smbd/trans2.c(3994) cmd=50 (SMBtrans2) NT_STATUS_OBJECT_NAME_NOT_FOUND
…

== To solve ==

Now, Mr. Google said following after I searched for NT_STATUS_OBJECT_NAME_NOT_FOUND:
http://lists-archives.org/samba/30781-error-when-upgrading-to-samba-3-0-25b-nt_status_object_path_not_found.html

Well, in the last message of the thread, following can be read:
> A reboot in the Windows PCs was the solution.

Quit strange cause just one of the angry users didn’t shut down the pc over night. So I rebooted first my linux machine. Then all windows users had to reboot and some of them also had to manually delete all saved networkdrives (like k:) and restart the logon-script. The problem was vanished.

Not to forget

If the samba server was upgraded, always REBOOT the windows machines and manually DELETE and RECREATE the specific networkdrives.