SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'll open up Windows Explorer, and open my network drive, but it freezes and I have to wait about 10-30 seconds for it to open a folder. Then after opening that folder it takes 10-30 seconds to open that folder. Wash. Rinse. Repeat.
This is a samba server that is in a virtual drive with VirtualBox, and the network setup is kind of convoluted. I don't know if this is the problem or not.
This is the output of testparm:
Code:
# Global parameters
[global]
server string = come in poor, walk out rich
workgroup = workgroup
name resolve order = wins lmhosts hosts bcast
security = USER
wins proxy = Yes
wins support = Yes
idmap config * : backend = tdb
[annex]
path = /home/annex
read only = No
valid users = username
Note that this is not about transfer speed. Transfer speed is just fine. Whether uploading or downloading a file, the transfer speed is just fine. It's just accessing the file is the issue.
My first (totally uneducated) guess is a delay in name resolution. Have you tested the response time for WINS and/or DNS?
How would I do that? I found something from GRC and some other open source program, but they seemed geared towards internet DNS and not local.
I use hosts file on windows for name resolution, which I assume is the quickest way. It's the easiest way, which is why I chose that method. It would be best that my router would do it, but then i'm not sure my router has that functionality. (TP-Link TL-WR720N)
Your setup above indicates that your first resolver is "wins", not "lmhosts" or "hosts". If Samba is configured to double-check inbound connections, its first lookup will be through "wins", which is network-based. If there is no running WINS service, there's a time-out and the next resolver is tried.
(WINS in Samba is usually provided by nmbd, but it is optional.)
My quick-and-ignorant suggestion: change the global config section to contain
Retrospectively, I guess I should have put this thread in the ARM section, but I didn't think the problem was specific and I had thought it was going to turn out to be Windows.
I hadn't really detected a distinct pattern until this morning when I realized it was just large files that were causing problems. Since the VDI file was a large file any communication with the VirtualBox disc image would cause my computer to lock up. I tried to copy the file and got a 0x8007003B error when copying files to windows, and that's how I found the above thread.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.