Robert Rossana wrote: > I did however discover something by accident. In one of these tests I > happened to try accessing linux files from WinXP and went away from the > machine. I discovered that it was able to find them after what appeared to > be a very substantial amount of time. Testing it out under various scenarios > gives the following information. I can use files from the linux partition > but it takes a full five minutes (yes that's right five minutes) for windows > explorer to display them.
5 minutes every time you look at different files, or change directories, or just on the first connection to a share? > It just hangs there for all that time and then the > files appear. This is obviously unacceptable. And thus far totally unreproducible. All our samba servers seem to work fine, I just tested my cooker/9.0 box from a windows 2000 server, and all seems well. I tested a 9.0 out-the-box (winbind setup test on a laptop) last night, and it works fine, but in both cases I had a WINS server available (which speeds up name resolution for windows). I have a Mandrake 9.0RC2 box in production on a network that is 1 hour away, and I haven't heard any complaints. It is a domain controller for a network of about 8 machines (win9x and win2k). > Samba in the past always > would function in just a few seconds but, for whatever reason, this share, as > opposed to another share, cannot be found for all this time. Further, shut > down the machine and you ge the error message that the smb process was killed > and thus can't be shut down. > You're going to have to give us more than this. We need a log which shows the error that is causing this. Set 'log level = 3' (or uncomment it, is should be there but commented in the default smb.conf), and watch the log of the machine that is connecting (/var/log/samba/log.<client>). If you don't see anything which indicates an error, bump the log level up until you get to 10. If you don't see it at 10, something wierd is really happening, bump it to 100. You should only need to # service smb reload between changes. Of course, you should also check /var/log/syslog for any errors. Also, maybe you could mail me a sanitised version of your /etc/samba/smb.conf, and define exactly your environment (what other machines, DNS or not, WINS or not, details on client including SP level, all the network components installed etc). > At this point the only thing I can suggest is that something in the security > settings may be doing this. I use the ones set by default on install but > maybe that is where the problem lies. We did ship (unintentionally) with 2.2.6pre2 (don't ask). But, there is only one bug that has been reproducible (off-by one error in directory listing with smbclient against win9x/winme server). There will be an update, but we're still nervous about real bugs (but haven't seen any, and all bugs so far have been [mis]-configuration issues). Buchan -- |----------------Registered Linux User #182071-----------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
