Daniel Hedblom
2011-Dec-20 09:16 UTC
[Samba] Logging in to a Samba 3.5.6 domain from Windows 7 takes more than 2 minutes.
Hi, are about to roll out Samba to 2600 users and 1500+ machines and have a slight problem. Server: Samba 3.4.9 running on ubuntu 10.04 Client: Windows 7, 32 and 64 bit on various hardware The problem is that logging in takes time and much of it seems to be the Windows 7 client just waiting. While 2 minutes may sound pretty ok this is without any roaming profiles or GPO applied. The logs shows nothing interesting ,on Windows i see error 6005 and 6006 but thats just a standard logging when things take a long time, can be anything. On a wireshark trace nothing in perticulat comes up before the long timeouts. Anyone else who has seen this problem after applying the various remedies on this mailing list and from other places on the internet? Thankful for any input. //danielh -- With best regards, Daniel Hedblom Sysadmin
pradip mondal
2011-Dec-20 10:23 UTC
[Samba] Logging in to a Samba 3.5.6 domain from Windows 7 takes more than 2 minutes.
dear all, ? i am also face the same problem. any body give us solution to fast login in samba pdc by win7 client. ? regards Pradip Mondal 9831626957 --- On Tue, 20/12/11, Daniel Hedblom <daniel.hedblom at solleftea.se> wrote: From: Daniel Hedblom <daniel.hedblom at solleftea.se> Subject: [Samba] Logging in to a Samba 3.5.6 domain from Windows 7 takes more than 2 minutes. To: samba at lists.samba.org Date: Tuesday, 20 December, 2011, 2:46 PM Hi, are about to roll out Samba to 2600 users and 1500+ machines and have a slight problem. Server: Samba 3.4.9 running on ubuntu 10.04 Client: Windows 7, 32 and 64 bit on various hardware The problem is that logging in takes time and much of it seems to be the Windows 7 client just waiting. While 2 minutes may sound pretty ok this is without any roaming profiles or GPO applied. The logs shows nothing interesting ,on Windows i see error 6005 and 6006 but thats just a standard logging when things take a long time, can be anything. On a wireshark trace nothing in perticulat comes up before the long timeouts. Anyone else who has seen this problem after applying the various remedies on this mailing list and from other places on the internet? Thankful for any input. //danielh -- With best regards, Daniel Hedblom Sysadmin -- To unsubscribe from this list go to the following URL and read the instructions:? https://lists.samba.org/mailman/options/samba