Recently we have upgraded our server from samba-3.3.5 to 3.4.0. Everything seems normal except for a small number of clients still running Win98. From a Win98 client, invoking "net use F: \\x093\tmp" gives the error message : > Error 66: You have specified an incorrect network resource type. Your > possible choices are (1) drive letter A: through Z for a shared directory > path, or (2) port name LPT1: through LPT9 for a shared printer or modem path. However, WinXP clients do not have the problem.
Created attachment 4420 [details] smb.conf
Created attachment 4421 [details] level 10 log for win98 connection failure
Created attachment 4422 [details] level 10 log for winxp connection
Is this really the complete log file? [2009/07/15 10:46:52, 6] param/loadparm.c:6989(lp_file_list_changed) lp_file_list_changed() file /10/samba-3.4.0/lib/smb.conf -> /10/samba-3.4.0/lib/smb.conf last mod_time: Wed Jul 15 10:39:49 2009 [2009/07/15 10:46:52, 3] smbd/process.c:1251(switch_message) switch message SMBtconX (pid 7061) conn 0x0 This to me seems that the interesting part is missing. What vuid does the client send? We assigned 100. Can you please send a network trace of the failure? For those debugging purposes, please remove the "log file" parameter from your smb.conf file so that we get the whole thing. Information on how to create useful network traces can be found under http://wiki.samba.org/index.php/Capture_Packets Thanks, Volker
Created attachment 4426 [details] Fix for 3.4.0 This should fix the problem. Win9x clients do a SessionsetupX/TconX pair, and we were not setting the vuid field correctly in the req struct passed down to chain_reply() after the sessionsetupX was successful. Jeremy.
Ahhh. Thanks, Jeremy! I had not thought about that one. Volker
Thinking of a torture test for this.... :-) Volker
Created attachment 4427 [details] Git formatted patch for 3.4.1. Volker, please review and then reassign to Karolin for inclusion in 3.4.1. Thanks ! Jeremy.
*** Bug 6556 has been marked as a duplicate of this bug. ***
Comment on attachment 4427 [details] Git formatted patch for 3.4.1. Ack. Fixes it for me with the chain2 test
Also fixed the same problem on NT4 here.
Pushed, patch will be included in 3.4.1. Closing out bug report. Thanks!
*** Bug 6629 has been marked as a duplicate of this bug. ***
*** Bug 6698 has been marked as a duplicate of this bug. ***