Hi all.

I checked through some of the old posts, but couldn't find anything that seemed to help with my current problem. I've been using Samba for years without any issues, until recently. At this particular site, we have two Slackware machines with Samba that act as file-servers. They've been running with no hitches for several years. Recently, we upgraded one office to newer PC's, they have Windows XP SP2 on them (I skipped Vista, because it's horrible).

What happens is that I open a share on the samba server, and everything looks okay. As soon as I try clicking on a file to copy, cut, check properties, etc in the explorer window - It freezes for like 2-3 minutes. Then it finally starts moving again. Sometimes the whole computer freezes up with the need of a cold restart. I compiled the newest version of Samba and installed it on my Slackware machine, made a config from scratch and still see the same issue. I notice this happens more with large files (100 mb+) more than smaller files.

I tried checking issues with CUPS, changing from USER security to SHARE, etc. I even tried tweaking the Windows machines to omit firewalling, virus-checking. Anybody have any ideas, or a thread that already addresses this topic. I'm about to shoot these stupid machines out the window!

Thanks,

<rabber

I've been fighting the same type of problems the last couple days and got it resolved by setting the IP address on the XP machine manually.

Is your Samba using WINS?

Also make sure to remove the "msdfs proxy = " setting from your smb.conf and make sure "encrypt passwords = yes" is there

If you post your smb.conf I may be able to give you further ideas.

Otherwise, these are geared towards openSUSE, but they may help with the XP side of things:
http://www.tweakhound.com/linux/samba/page_1.htm
http://www.swerdna.net.au/linhowtolanprimer.html#nicwin

Thanks for replying -

Yeah, I'm afraid the current config is rather simple, because I'm trying to work this out before going to production. I am seeing the same problem with even the simplest config.


[global]

[Test]
path = /HDB/Bldg1

I did modify the buffer sizes as well and also turned off Large Read/Write once. I see the exact same symptom every time.

It's funny you mentioned WINS, because that's one thing I've been looking into myself. I'm going to try what you suggested, and also try a static IP. This of course will be impossible to implement for our office, but at least I could pinpoint the issue.

I just tried a static address and it didn't work. BTW, encrypted passwords is a default on my compilation of Samba, if you are wondering why it's not in global.

Hello all,

I think I figured out what's going on in my case. The new computers come with a trial version of Anti-Virus - When I uninstalled the software the samba shares updated much quicker than before. Just turning it off didn't make a difference. It seems to be connected with changes it makes to the windows explorer. FYI - This slowdown was also apparent on windows shares that had large files. This is what lead me to the conclusion that it was an application on the client.

The other problems seen with slow browsing (on other PC's) went away with the current version of Samba. Although these never froze up the client like the problem I was having with the new machines.

Here's a link for anyone that needs help on Samba issues - http://samba.org/samba/docs/man/Samb....html#id350927

Looks like applications like Anti-Virus, etc should be added to this list of slowdowns.

Hope this helps somebody else.

out of curiosity, what was the trial anti-virus program?

I am having fedora core2 system and windows xp system. How can i open the windows shared folders from fedora core2