Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2155
  • Last Modified:

Problem copying large files from windows to Samba (Redhat Linux)

When copying files to my Samba server approximately > 100 MB from windows xp/2000 machines I get an error message saying that the network path is no longer available after a minute or so of copying. I can copy files > 100 MB from the Samba server to the same machines with no problems. I can copy any number of approximately < 100 MB files to the to the same Samba server. Linux machines can send and receive files of any size and number. I have other Samba servers running that do not have these problems and I copied the smb.conf's from the to this server but the issue remained. This Linux instalation is in an iSseries guest partition using nat subnetting via virtual networking. All other systems such as FTP, SSH, telnet, HTTP are working as expected. I matched the MTU's of the virtual and the line descriptions to be 1496. My config allows guest access with security=share so there are no security issues and the file system permissions are wide open also.

My Samba log is filled with the following messages: [2004/08/26 15:31:09, 0] smbd/oplock.c:request_oplock_break(1244)
  request_oplock_break: no response received to oplock break request to pid 28509 on port 45506 for dev = 7001, inode = 4096

Thanks for your attention and if any more info is needed i will provide asap.

(system info)
Linux samba2 2.4.9-23.19.8 #1 SMP Mon Oct 14 15:01:22 CDT 2002 ppc64 unknown

Domain=[MYDOMIAN] OS=[Unix] Server=[Samba 3.0.5]

        Sharename      Type      Comment
        ---------      ----      -------
        homes          Disk      Home Directories
        everyone       Disk      Public directory
        root           Disk      Home directories
        IPC$           IPC       IPC Service (samba server 2)
        ADMIN$         IPC       IPC Service (samba server 2)

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        WORKGROUP            SAMBA2


0
drdewm
Asked:
drdewm
1 Solution
 
PaulS_IIICommented:
Do you get the "Path Too Deep" error when the copying is happening? I remember a long time ago I had a similar situation. It turned out to be my network card. It was the a 3Com card that turned out to be the problem.

It is a stretch but it may be a place to start looking
0
 
drdewmAuthor Commented:
We used different routing to avoid this issue so the root cuase was never defined. Instead of NATing the addresses we needed we went with a proxy arp method so the re-assembling of the packets was avaoided. After some sniffing/packet dissasemlby we noticed a crc error after about 16+megs and just assumed there was some ip stack wierdness and decided to move on.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now