> Hello Samba Users, > > > > I am using Samba for our project needs to share folders between a Windows > Server 2003 machine and a > > RedHat Linux machine. I am facing issues with Samba shares (Samba Version > 3.5.5 for RHEL 4 x86_64). The scenario is as below ? > > > The windows machine has a couple of shared folders, one of them being * ** > C:\output* The windows shares are mounted onto corresponding mount points > in linux >and the same are exposed to the external world via samba running on the> Linux machine. > > > > Now, the Windows machine kicks off a few jobs and as a part of those jobs > it writes to the *output *shared folder. This write request is directed > via Samba as the >windows machine writes to \\<Linux IPAddress>\output. It has been observed consistently that accessing the shared folder from windows using UNC as \\<LinuxIpAddress>\output takes a very long time. Each access takes around 45 to 50 seconds ! though there are no network issues.> Any directions on how to get around this problem ? Can it controlled via > specific share level/global settings in smb.conf ? > > > > > - Supriya >
Be shure it is no firewall issue!?? Seems you have a problem resolving the ip of the linux. You can put the ip and name of the linux in the host file of your w2003 and vice versa in the host file of your linux. Or you use dns or wins to do so ----------------------------------------------- EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de Internet: www.tropenklinik.de ----------------------------------------------- -----Urspr?ngliche Nachricht----- Von: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] Im Auftrag von Supriya Kher Gesendet: Mittwoch, 12. Januar 2011 09:01 An: samba at lists.samba.org Betreff: [Samba] Samba Share Access Delay !> Hello Samba Users, > > > > I am using Samba for our project needs to share folders between a Windows > Server 2003 machine and a > > RedHat Linux machine. I am facing issues with Samba shares (Samba Version > 3.5.5 for RHEL 4 x86_64). The scenario is as below ? > > > The windows machine has a couple of shared folders, one of them being * ** > C:\output* The windows shares are mounted onto corresponding mount points > in linux >and the same are exposed to the external world via samba running on the> Linux machine. > > > > Now, the Windows machine kicks off a few jobs and as a part of those jobs > it writes to the *output *shared folder. This write request is directed > via Samba as the >windows machine writes to \\<Linux IPAddress>\output. It has been observed consistently that accessing the shared folder from windows using UNC as \\<LinuxIpAddress>\output takes a very long time. Each access takes around 45 to 50 seconds ! though there are no network issues.> Any directions on how to get around this problem ? Can it controlled via > specific share level/global settings in smb.conf ? > > > > > - Supriya >-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Supriya Kher wrote:> windows machine writes to \\<Linux IPAddress>\output. It has been > observed consistently that accessing the shared folder from windows using > UNC as \\<LinuxIpAddress>\output > takes a very long time. Each access takes around 45 to 50 seconds ! > though there are no network issues. > >> Any directions on how to get around this problem ? Can it controlled via >> specific share level/global settings in smb.conf ?--- I had something *like* this, but not quite this bad -- it was very persistent -- no matter what program I ran, my max xfer speed was about 2MB/s (read & write). Nothing I tried fixed it -- until I rebooted. Then it went mysteriously away (back to full speed of 119M/125MB read/write). I looked at the the wireshark traces for the bad-case -- the only odd thing I saw (which wouldn't explain the whole thing) was that my max window size had dropped to under 64k (normal is 1M). It hasn't repeated. It _sorta_, *looked* like something was inserting itself to look at the packets in and out and doing a really bad job of being 'transparent'. But since it hasn't re-occurred, I haven't thought much about it. In my case, it *appeared* to affect all network traffic (I kept checking the sync rate on the line, figuring it had to be syncing at 10Mb and not 1Gb, but wasn't the case). You might try a 'wireshark' trace? Try to see who is doing the 'lagging'....