0

When browsing a SAMBA file server, File Explorer takes a very long time (60+ secs) to load a share. If I view the same share on the command line with the following command, it returns the listing instantly.

dir \\server\share

This leads me to believe it's a problem with Windows and not the file server.

How can I diagnose the problem? What is File Explorer doing differently than the "dir" command?

Thanks.

0

You asked: "How can I diagnose the problem?" Here's how I would start to troubleshoot this:

If you have done these steps, could you edit your question to show the results of these steps? More detailed information in the question will lead to more detailed answers. Thank you.

  1. Do you have access to the host running Samba? What OS is on the host? I would log in to that host and look at the samba log files. The log file location should be defined in /etc/samba/smb.conf or an included configuration file.
  2. What is the IP address of server? Assuming it is 192.168.1.2, do dir \\server\share and dir \\192.168.1.2\share both take the same amount of time to load the share? Does File Explorer take the same time when using the IP and when using the hostname? If the time is faster with one or the other, that points to an issue with name resolution.
  3. Do you have another identical client to test the samba share from? Is the problem the same on the second client? Or does the problem only appear on one client? An identical problem on both clients suggests a configuration setting on the samba server needs adjustment.
  4. Do you have a linux host to use to test client access? If I have to debug the samba service, I find smbclient a useful tool.
  5. Does the problem only appear with samba and file sharing? Or does the host offer other services (http ?) that you can check by both IP and name, to see if there is a difference?
  • Thanks for the response. Most of these are the steps I've taken so far. To answer your questions. 1. Yes, host is CentOS running Samba3. Log files don't show anything out of the ordinary. 2. File Explorer takes the same time using the IP vs the hostname 3. Multiple clients are experiencing the same issue. 4. Linux clients browse quickly 5. Other services are working normally – user3113357 Oct 26 '16 at 17:35
0

Turns out the problem was being caused by a disconnected NFS connection on the Samba host. That connect was not being accessed by the shares that were not loading, but it still prevented Samba from working properly.

  • Glad to hear you found an answer. Could you mark your own answer as "accepted" so that it may be filtered out of the list of unanswered questions? Thank you. – StandardEyre Oct 26 '16 at 20:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.