[Samba] Trouble with Windows 2000 sp3

[Smith, Daniel A(Z07833)]

Not sure what else to try.  Maybe keepalive and socket options.

I've included a the global section of my smb.conf file, maybe there is something there that will give you a clue. HTH



[global]
        workgroup = WWWWW
        netbios name = NNNNNNNN
        security = SERVER
        encrypt passwords = Yes
        hosts equiv = /etc/hosts.equiv
        password server = PPPPPP
        username map = /appls/public/samba/lib/user.map
        password level = 8
        syslog = 0
        deadtime = 10
        keepalive = 0
        socket options = SO_KEEPALIVE
        printcap name = /appls/public/samba/lib/printcap
        dfree command = /appls/public/samba/bin/dfree.sh
        NIS homedir = Yes
        create mask = 0664
        force create mode = 0664
        printing = bsd
        level2 oplocks = No


Dan Smith
Sr. System Analyst
Pinnacle West Shared Services
"If you can't get your work done in 24 hours a day,
work nights"


-----Original Message-----
From: Joshua Pollak [mailto:jpollak at cra.com]
Sent: Tuesday, September 24, 2002 4:08 PM
To: Smith, Daniel A(Z07833); samba at lists.samba.org
Subject: Re: [Samba] Trouble with Windows 2000 sp3


This adjustment, along with the suggestion of setting the following options:

oplocks = no
level2 oplocks = no
kernel oplocks = no

Has not helped my problem. Here is a clipping of the relevant log file. The 
broken pipe errors are very very frequent.

[2002/08/21 10:02:24, 0] lib/util_sock.c:write_socket_data(546)
  write_socket_data: write failure. Error = Broken pipe
[2002/08/21 10:06:02, 0] smbd/open.c:open_directory(1044)
  open_directory: unable to create 
[2002/08/21 10:08:33, 0] lib/util_sock.c:write_socket_data(546)
  write_socket_data: write failure. Error = Broken pipe
[2002/08/21 10:13:53, 0] lib/util_sock.c:write_socket_data(546)
  write_socket_data: write failure. Error = Broken pipe

This problem only appeared after I upgraded to SP3, so I doubt this is a 
hardware error. Does anyone have any idea what could be wrong? We are using 
samba 2.2.5, and we had the same problem with 2.2.3. This only happens on one 
computer, but its the only computer we have running sp3.

-Josh

On Tuesday 24 September 2002 01:36 pm, Smith, Daniel A(Z07833) wrote:
> It sounds like your drives are getting disconnected.
>
> You can try setting
>
> deadtime=10
>
> I think what is happening is the the Windows 2000 connection is timing out
> at the same time the Samba connection does and things get confused. 
> Reducing the dead time seemed to help but not completely solve my problem
> with the connection reset by peer message.
>
> Dan Smith
> Sr. System Analyst
> Pinnacle West Shared Services
> "If you can't get your work done in 24 hours a day,
> work nights"
>
>
> -----Original Message-----
> From: Joshua Pollak [mailto:jpollak at cra.com]
> Sent: Monday, September 23, 2002 12:01 PM
> To: samba at lists.samba.org
> Subject: [Samba] Trouble with Windows 2000 sp3
>
>
> Hello,
>
> I work in a development shop where we write code for both Linux and
> Windows, and develop on both OS's on a codebase stored on a Linux drive
> with Samba shares. Ever since I 'upgraded' my Windows 2000 system to
> service pack 3, I have been having trouble compiling my code with Visual
> Studio over this Samba connection.
>
> Basically what happens is that Visual Studio reports "cannot open file" for
> various .exp, .sbr, .lib, or .dll files that it tries to write to during
> the compilation process. When I try to go into Windows Explorer and delete
> the file, I get an error message that another process is using the file. I
> can delete the file without a problem from my Linux machine, and then I can
> usually resume compilation on the Windows box, but this is very aggrivating
> as we have a large project.
>
> Usually the only way to resolve this problem is to reboot the Windows
> machine, but some of Microsofts latest critical updates seem to have made
> THAT not even work.
>
> Anyway, I have tried getting the Linux admin to disable oplocks, with this
> set of commands:
>
> [home]
> oplocks = no
> locking = Yes
> share modes = Yes
>
> But that doesn't seem to have worked. What gives? Is there anything else I
> can try?

-- 
Joshua Pollak
Software Engineer
Charles River Analytics