8300 – Long delay for login with Windows 7 as Samba domain member

Bug 8300 - Long delay for login with Windows 7 as Samba domain member

Summary: Long delay for login with Windows 7 as Samba domain member

Status:	NEW

Alias:	None

Product:	Samba 3.5
Classification:	Unclassified
Component:	Domain Control (show other bugs)
Version:	3.5.4
Hardware:	All All

Importance:	P5 normal
Target Milestone:	---
Assignee:	Guenther Deschner
QA Contact:	Samba QA Contact

URL:
Keywords:

Depends on:
Blocks:

Reported:	2011-07-11 14:03 UTC by Arvid Requate
Modified:	2011-07-11 14:03 UTC (History)
CC List:	0 users

See Also:

Attachments
level 10 logs, tcpdump and smb.conf (611.51 KB, application/x-gtar) 2011-07-11 14:03 UTC, Arvid Requate	no flags	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate 2011-07-11 14:03:18 UTC

Created attachment 6678 [details]
level 10 logs, tcpdump and smb.conf

Domain users experience a slow login performance on Windows 7 clients that are joined into a samba domain (Samba version 3.5.4). The Windows 7 client was joined successfully into the domain with the Windows 7 registry settings adjusted according to http://wiki.samba.org/index.php/Windows7 (DomainCompatibilityMode = 0 and DNSNameResolutionRequired = 0).

The level 10 logs attached and the wireshark trace show a behaviour quite similar to the bugreport in the Debian bugzilla about a Windows Vista SP2 with a similar behaviour ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531344 ): There are two delays in the client-server communication. The first is a 10 second delay after the server sent a STATUS_NO_MORE_ENTRIES in resonse to a LsarEnumerateTrustedDomains operation. Shortly after that there is another 20 second delay.

The attached log and trace have been taken with an Win7 Professional joined to a samba 3.5.4 PDC on Debian Linux (2.6.32-ucs37-686-bigmem). SP1 shows the same behaviour. While the cient side registry setting "WaitForNetwork" = 0 hides the symptom from the user, it would be good to understand the cause of this behaviour.