I have a new Sun Fire AMD64 server running Solaris 10 12/06 and Samba
3.0.21b. I have migrated a configuration file from an older RHEL
machine running Samba 2.2.x. On this new machine, if one tries to
copy a large number of files from a Windows XP client to the server,
the copy starts and runs for a few minutes, but then stops. The
error message on the XP machine is "Cannot copy [filename]: The
specified network name is no longer available." On the Samba side, I
ran in interactive mode with debug level 3 and got this at the end of
the file:
Transaction 196173 of length 228
switch message SMBtrans2 (pid 29278) conn 0x83754b0
call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004
call_trans2qfilepathinfo kmw/_K/Kate/Travel/AZ trip1/Steph's pics/AZ
2006 w Steph & Cheryl 060.jpg (fnum = -1) level=1004
call=5 total_data=0
timeout_processing: End of file from client (client has disconnected).
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
Closing connections
push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 1
push_conn_ctx(0) : conn_ctx_stack_ndx = 0
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1
pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0
kmw closed file kmw/_K/Kate/Travel/AZ trip1/Steph's pics/AZ 2006 w
Steph & Cheryl 061.jpg (numopen=1)
error packet at smbd/notify.c(55) cmd=160 (SMBnttrans)
NT_STATUS_CANCELLED
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
iastate (129.186.19.136) closed connection to service voytaslab
Yielding connection to voytaslab
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
Yielding connection to
Server exit (normal exit)
When this happens, it appears on the server side that the machine is
backed up with disk writes.
Can someone tell me how to solve this problem?
