[Samba] Windows XP Machines (well mostly the XP ones) hanging

[James Jeffrey]

Hello Folks,

I will personally send $50(AU) of Pizza to anyone that solves this one :)

We have a network comprising approx 30 Windows workstations all logging in
to a samba machine running as a PDC. The main exported file system is an NFS
mounted file system, but this was happening back when this was an xfs file
system as well. ACL's are enabled. We are running Samba Version 2.2.8a. The
server does not appear overloaded.

Multiple users have reported that when they are trying to access files
across the network their machine hangs for approx 20 secs then continues as
normal. This does not happen every time, but does happen quite frequently.

Our network is not displaying a significant amount of packet loss.

Below is our Samba configuration.

James.
--

[global]
netbios name = BERTHA
workgroup = TECHNOPHOBIA
veto oplock files = /*.doc/*.qbw/
kernel oplocks = no
interfaces = eth0

os level = 64
preferred master = true
domain master = yes
local master = yes
wins support = yes

log level = 2

security = user

encrypt passwords = yes

domain logons = yes
domain admin group = @pcadmin
add user script = /usr/sbin/useradd -d /dev/null -g machines -s /bin/false
-M %u

logon path = \\%N\profiles\%u

logon drive = N:
logon home = \\bertha\myhome\.profiles
logon script = %u.bat

printing = lprng

[Mothra1]
comment = Kyocera FS1000N+ Room 321
printer name = Mothra
path = /var/spool/samba/mothra
browseable = yes
public = yes
writeable = no
printable = yes
valid users = @smbusers @pcadmin

[lj5000]
comment = Main Office Laserjet
printer name = lj5000
path = /var/spool/samba/lj5000
browseable = yes
public = yes
writeable = no
printable = yes
valid users = @smbusers @pcadmin @tempusers

[mrt]
comment = Hewlett Packard CP1700
printer name = mr_t
path = /var/spool/samba/mrt
browseable = yes
public = yes
writeable = no
printable = yes
valid users = @smbusers @pcadmin

#[Stylus]
#comment = Epson Stylus Near Saul
#printer name = stylus
#path = /var/spool/samba/stylus
#public = yes
#writeable = no
#printable = yes
#browseable = yes
#use client driver = yes
#valid users = @smbusers @pcadmin

#[pdf]
#comment = PDF Printer
#printer name = pdf
#print command = /usr/local/custom/bin/pdfprinter %s %u
#path = /var/spool/samba/pdf
#public = yes
#writeable = no
#printable = yes
#browseable = yes
#valid users = @pcadmin @smbusers

[print$]
path= /home/export/print
guest ok = yes
browseable = yes
read only = yes
write list = @pcadmin root
valid users = @pcadmin @smbusers

[netlogon]
path = /home/export/netlogon
browseable = no
read only = yes
write list = @pcadmin
valid users = @pcadmin @smbusers @tempusers
create mask = 0660
directory mask = 0770
admin users = @pcadmin

[profiles]
path = /home/export/profiles
read only = no
create mask = 0600
directory mask = 0700
browseable = no
nt acl support = no
valid users = @pcadmin @smbusers @tempusers

[myhome]
path = %H/pchome
read only = no
browseable = yes
valid users = @pcadmin @smbusers
inherit acls = yes

[AllHomes]
path=/home
read only = yes
valid users = @pcadmin
write list = @pcadmin
browseable = yes
admin users = @pcadmin
inherit acls = yes

[Projects]
path=/home/export/projects
read only = no
browseable = no
valid users = @pcadmin @smbusers
admin users = @pcadmin
inherit acls = yes

[Client_Work]
path=/home/export/projects
read only = no
browseable = yes
valid users = @pcadmin @smbusers
admin users = @pcadmin
inherit acls = yes

[Sites]
path=/home/export/sites
read only = no
browseable = yes
valid users = @pcadmin @smbusers
admin users = @pcadmin
inherit acls = yes
create mask = 0660
directory mask = 0770

[Departments]
path=/home/export/departments
read only = no
browseable = yes
valid users = @pcadmin @smbusers accountant
admin users = @pcadmin
inherit acls = yes
create mask = 0660
directory mask = 0770

[Software]
path=/home/export/software
read only = yes
write list = @it
valid users = @pcadmin @smbusers
browseable = yes
admin users = @pcadmin
inherit acls = yes
create mask = 0660
directory mask = 0770

[Temporary]
path=/home/export/temporary
read only = no
valid users = @pcadmin @smbusers @tempusers
browseable = yes
admin users = @pcadmin
inherit acls = yes
create mask = 0777
directory mask = 0777

[Shared]
path=/home/export/shareddocs
read only = yes
write list = @filing @pcadmin
valid users = @pcadmin @smbusers
browseable = yes
admin users = @pcadmin
inherit acls = yes
create mask = 0660
directory mask = 0770

[CVS]
path=/home/cvs
read only = no
write list = @developers
browseable = no
admin users = @pcadmin
valid users = @pcadmin @smbusers
inherit acls = yes

[for_upload]
path = /home/export/for_upload
read only = no
valid users = @pcadmin @smbusers
browseable = yes
admin users = @pcadmin
inherit acls = yes
create mask = 0660
directory mask = 0770
force group = uploads

[archive]
path = /home/export/archive
read only = no
valid users = @pcadmin @smbusers
browseable = yes
admin users = @pcadmin
inherit acls = yes

[crypto]
path=/crypt
read only = no
valid users = @crypto
browseable = no
inherit acls = yes

--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba

[Mikevl]

Are the WinXP machines running SP1?

Mike

[James Jeffrey]

Yes they are - and I forgot to mention that the Web Filesystem service has
been disabled.

[Mal Beaton]

We have had similar problems but it was related to deadtime. IE no
network activity for a period so the connection is closed. Supposed to
seemlessly reconnect but sometimes doesnt. That could be the slowness.

We also had other problems with logins and logouts. It seemed that samba
doesnt handle win xp logouts well

We set deadtime = 120 in the smb.conf and havent had a complaint about
lost drives/slowness/bad logins for two weeks now

--
Mal

http://mbeaton.id.au:5537/
:wq!

[Mikevl]

Right I may be a little off the track here and please don't laugh as you
read on. I had a similar problem when installing a MS SBS server with XP
workstations SP1. The client really needed MS SQL server poor buggers.
Anyway XP SP1 has some significant problems all on it's own. This dosn't
show all the time on an installation and not every installation either. The
problem is described here
http://www.smallbizserver.net/Workstations/I_get_an_error_when_I_try_to_save_a_file_in_Office.aspx

hope this helps

[richard]

if your pdc network card is reporting ANY packet loss I would replace it
pronto!

[Shawn D. Kelly]

This may or may not help, but I've installed about 25 XP machines onto a W2K
network and experienced the exact same thing - slowdown and then all of the
sudden it's fine. I don't believe it's a Samba thing, but an XP thing.
Search google or your engine of choice for 'XP slow network' or something
like that and you might get luckier.

-----Original Message-----
From: samba-bounces+sdkelly=twcny....@lists.samba.org
[mailto:samba-bounces+sdkelly=twcny....@lists.samba.org] On Behalf Of
James Jeffrey
Sent: Tuesday, June 10, 2003 5:25 AM
To: sa...@lists.samba.org
Subject: [Samba] Windows XP Machines (well mostly the XP ones) hanging

[j...@dp.samba.org]

On Tue, Jun 10, 2003 at 10:24:38AM +0100, James Jeffrey wrote:
> Hello Folks,
>
> I will personally send $50(AU) of Pizza to anyone that solves this one :)
>
> We have a network comprising approx 30 Windows workstations all logging in
> to a samba machine running as a PDC. The main exported file system is an NFS
> mounted file system, but this was happening back when this was an xfs file
> system as well. ACL's are enabled. We are running Samba Version 2.2.8a. The
> server does not appear overloaded.
>
> Multiple users have reported that when they are trying to access files
> across the network their machine hangs for approx 20 secs then continues as
> normal. This does not happen every time, but does happen quite frequently.

Can you get a sniffer trace from their machine at the time this
happens ? It's probably the only way you're going to reliably
track this down.

Jeremy.

[j...@dp.samba.org]

On Tue, Jun 10, 2003 at 09:46:44PM +1200, Mikevl wrote:
> Right I may be a little off the track here and please don't laugh as you
> read on. I had a similar problem when installing a MS SBS server with XP
> workstations SP1. The client really needed MS SQL server poor buggers.
> Anyway XP SP1 has some significant problems all on it's own. This dosn't
> show all the time on an installation and not every installation either. The
> problem is described here
> http://www.smallbizserver.net/Workstations/I_get_an_error_when_I_try_to_save_a_file_in_Office.aspx

Very interesting article thanks ! I'd also
refer people to these pages if they're having
problems with MS-Office on a network drive on XP.

http://support.microsoft.com/?id=812937

"This problem occurs when the redirector flushes the contents of the file, and writes to a file handle with read-only access instead of to a file handle with write access. When the redirector received an opportunistic lock break to none, it purged the cache for the file, but did not uninitialize the cache for the file. The redirector also needed to purge and uninitialize when the set end of file occurs because the opportunistic lock break is asynchronous. Because it did not uninitialize the cache for the file, it wrote to the incorrect file handle."

and this one :

http://support.microsoft.com/?id=811492

" After you apply Windows XP Service Pack 1 (SP1), it may take approximately 35 seconds to delete files over the network. This problem occurs approximately 10 to 15 percent of the time. A network trace of the problem shows the following frames:

Client -> Server - C NT Create & X, File : \test.txt - request for OpLock\OpBatch
Client -> Server - C Delete File, File = : \test.txt
Server -> Client - R NT Create &X, FID = 0x8003 - oplock level = Batch
Server -> Client - C Lock - Break Oplock
A delay of approximately 35 seconds occurs at this time.

Server -> Client - R Delete Status_Sharing_Violation
Client -> Server - C Lock & X, FID = 0x8003 - Break OpLock
Client -> Server - C Delete File, File = : \test.txt
Server -> Client - R Delete
The first two frames are from the client. The initial frame is an "NT Create" message with a request for Oplock/OpBatch for the file. This is followed by the "Delete" request for the same file. The next frame is the server's response to the "NT Create" request with a Oplock level of "batch." The server then sends a Break OpLock message for the previous frame so that it can delete the file. The server then waits 35 seconds (until its OpLockBreakWait time-out value has expired) before the deletion does not work. The client can then release the lock and try the deletion again.
CAUSE
When the Break Oplock request is received by the client, the client cannot process the request because it is already waiting on the Delete request. The server cannot handle the Delete request until the Oplock on the file has been released. This causes a pseudo-deadlock condition that is broken after the server's OpLockBreakWait time-out value expires.
"

(Looks like not all oplock problems are the fault of Samba :-).

Jeremy.

[j...@dp.samba.org]

On Tue, Jun 10, 2003 at 07:20:47AM -0400, Shawn D. Kelly wrote:
> This may or may not help, but I've installed about 25 XP machines onto a W2K
> network and experienced the exact same thing - slowdown and then all of the
> sudden it's fine. I don't believe it's a Samba thing, but an XP thing.
> Search google or your engine of choice for 'XP slow network' or something
> like that and you might get luckier.

Indeed. It looks like WinXP SP1 has some bad bugs w.r.t. oplock
processing.

See this page for details :

http://support.microsoft.com/?id=811492

Jeremy.